Nach Update auf AstraMeter erkennt der Marstek Venus E3 keinen SmartMeter

[arturwins]

Hallo zusammen,

Ich habe am Sonntag bei mir sowohl den Marstek Venus E3 auf die aktuelle Firmware geupdatet als auch den B2500 meter auf AstraMeter 2.0.1 hochgezogen (aktuell auf 2.0.2) leider funktioniert seitdem mein Setup nicht mehr. Vorher lief meine Nulleinspeisung problemlos.
Ich nutze wie unten beschrieben HA auf einem Rasp PI4, die aktuelle Leistung bekomme ich vorzeichenbehaftet als Gesamtleistung über alle drei Phasen über Mqtt von meinem ESP32 (sensor.Gesamtleistung). Jetzt habe ich nach über 2 Tagen rumprobieren keine Idee mehr.
Aktuell nutze ich über die config.ini den Smartmeter_Test_skip, da er sonst bereits hier gescheitert ist. Mein Verständnis nach erhält AstraMeter über 192.168.178.186:22222 eine Anfrage von meinem Marstek -> antwortet hier rauf jedoch nicht -> No powermeter found for client 192.168.178.186
Jemand eine Idee was ich falsch konfiguriert habe???

Firmware des Marstek Venus E3 is die V148

-----------------------------------------------------------
 Add-on: AstraMeter
 "Replicates a Smart Meter device for Marstek energy storage systems (formerly B2500 Meter) while allowing integration with various smart meters."
-----------------------------------------------------------
 Add-on version: 2.0.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 17.3  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2026.5.3
 Home Assistant Supervisor: 2026.05.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
Log level is set to DEBUG
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[15:13:02] INFO: Using custom config file: config.ini
[15:13:02] WARNING: App UI Marstek settings are ignored when custom_config is used; values from custom config file take precedence
[GENERAL]
DEVICE_TYPE= shellypro3em,shellyproem50
SKIP_POWERMETER_TEST = True
THROTTLE_INTERVAL = 2
CURRENT_POWER_ENTITY = sensor.Gesamtleistung
[15:13:04] INFO: Waiting for Home Assistant to be ready...
[15:13:04] DEBUG: Checking Home Assistant readiness (attempt 1/60)...
[15:13:04] INFO: Home Assistant is ready! Proceeding with AstraMeter startup...
[15:13:04] INFO: Starting AstraMeter with log level: debug
2026-05-20 15:13:07 INFO:astrameter:started astrameter application
2026-05-20 15:13:07 INFO:astrameter:Git commit: 0b5a7b9e0f399daaab6e0310bdb35e4abfd2eca6
2026-05-20 15:13:07 INFO:astrameter:Device Types: ['shellypro3em_old', 'shellyproem50', 'shellypro3em_new']
2026-05-20 15:13:07 INFO:astrameter:Device IDs: ['shellypro3em-ec4609c439c1', 'shellyproem50-ec4609c439c2', 'shellypro3em-ec4609c439c1']
2026-05-20 15:13:07 INFO:astrameter:Skip Test: True
2026-05-20 15:13:07 DEBUG:asyncio:Using selector: EpollSelector
2026-05-20 15:13:07 INFO:astrameter:Starting web server...
2026-05-20 15:13:07 INFO:astrameter:Web server started on 0.0.0.0:52500
2026-05-20 15:13:07 INFO:astrameter:Web server started successfully
2026-05-20 15:13:07 DEBUG:astrameter:Starting device: shellypro3em_old
2026-05-20 15:13:07 DEBUG:astrameter:Shelly Pro 3EM Settings:
2026-05-20 15:13:07 DEBUG:astrameter:Device ID: shellypro3em-ec4609c439c1
2026-05-20 15:13:07 DEBUG:astrameter:Starting device: shellyproem50
2026-05-20 15:13:07 DEBUG:astrameter:Shelly Pro EM 50 Settings:
2026-05-20 15:13:07 DEBUG:astrameter:Device ID: shellyproem50-ec4609c439c2
2026-05-20 15:13:07 DEBUG:astrameter:Starting device: shellypro3em_new
2026-05-20 15:13:07 DEBUG:astrameter:Shelly Pro 3EM Settings:
2026-05-20 15:13:07 DEBUG:astrameter:Device ID: shellypro3em-ec4609c439c1
2026-05-20 15:13:07 INFO:astrameter:Shelly emulator listening on UDP port 1010...
2026-05-20 15:13:07 INFO:astrameter:Shelly emulator listening on UDP port 2223...
2026-05-20 15:13:07 INFO:astrameter:Shelly emulator listening on UDP port 2220...
2026-05-20 15:13:08 INFO:astrameter:Battery detected on Shelly UDP port 2223: 192.168.178.186
2026-05-20 15:13:08 DEBUG:astrameter:Received UDP message: {"id":0,"method":"EM1.GetStatus","params":{"id":0}}
2026-05-20 15:13:08 DEBUG:astrameter:From: 192.168.178.186:22222
2026-05-20 15:13:08 DEBUG:astrameter:Parsed request: {
  "id": 0,
  "method": "EM1.GetStatus",
  "params": {
    "id": 0
  }
}
2026-05-20 15:13:08 WARNING:astrameter:No powermeter found for client 192.168.178.186
2026-05-20 15:13:08 DEBUG:astrameter:Received UDP message: {"id":0,"method":"EM1.GetStatus","params":{"id":0}}
2026-05-20 15:13:08 DEBUG:astrameter:From: 192.168.178.186:22222
2026-05-20 15:13:08 DEBUG:astrameter:Parsed request: {
  "id": 0,
  "method": "EM1.GetStatus",
  "params": {
    "id": 0
  }
}
2026-05-20 15:13:08 WARNING:astrameter:No powermeter found for client 192.168.178.186
2026-05-20 15:13:09 DEBUG:astrameter:Received UDP message: {"id":0,"method":"EM1.GetStatus","params":{"id":0}}
2026-05-20 15:13:09 DEBUG:astrameter:From: 192.168.178.186:22222

[tomquist]

Die Antwort steht im log:

WARNING: App UI Marstek settings are ignored when custom_config is used; values from custom config file take precedence

und dann später:

2026-05-20 15:13:08 WARNING:astrameter:No powermeter found for client 192.168.178.186

D.h. du benutzt eine custom Config, d.h. du hast in der Home Assistant config page das Feld "Custom Config" ausgefüllt. Deine Config Datei enhält diese Invalide Konfiguration:

[GENERAL]
DEVICE_TYPE= shellypro3em,shellyproem50
SKIP_POWERMETER_TEST = True
THROTTLE_INTERVAL = 2
CURRENT_POWER_ENTITY = sensor.Gesamtleistung

Konkret ist dort kein Powermeter angegeben. Schaue dir entweder die Readme nochmal genau an wie eine custom config aufbaut oder leere das Feld "Custom Config" und trage in der Home Assistant config deinen Sensor sensor.Gesamtleistung ein.

[arturwins]

Danke für deine Antwort!
Das mit der config.ini habe ich testhalber ausprobiert, eigentlich benötige ich die config.ini nicht, ich wollte nur den powermeter test überspringen, da ich sonst an der Stelle nicht weiter gekommen bin. Ohne der config.ini bekomme ich folgende Ausgabe im Protokoll, vielleicht kannst du mir hier weiter helfen?

-----------------------------------------------------------
 Add-on: AstraMeter
 "Replicates a Smart Meter device for Marstek energy storage systems (formerly B2500 Meter) while allowing integration with various smart meters."
-----------------------------------------------------------
 Add-on version: 2.0.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 17.3  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2026.5.3
 Home Assistant Supervisor: 2026.05.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to DEBUG
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[16:39:11] DEBUG: Requested API resource: http://supervisor/addons/self/info
[16:39:11] DEBUG: Request method: GET
[16:39:11] DEBUG: Request data: {}
[16:39:11] DEBUG: API HTTP Response code: 200
[16:39:11] DEBUG: API Response: {"result":"ok","data":{"name":"AstraMeter","slug":"11e5258b_b2500_meter","hostname":"11e5258b-b2500-meter","dns":["11e5258b-b2500-meter.local.hass.io"],"description":"\"Replicates a Smart Meter device for Marstek energy storage systems (formerly B2500 Meter) while allowing integration with various smart meters.\"","long_description":null,"advanced":false,"stage":"stable","repository":"11e5258b","version_latest":"2.0.2","protected":true,"rating":4,"boot_config":"auto","boot":"auto","options":{"power_input_alias":"sensor.Gesamtleistung","power_output_alias":"","device_types":"shellyproem50","throttle_interval":2.0,"wait_for_next_message":true,"marstek_auto_register_ct_device":false,"marstek_mailbox":"","marstek_password":"","min_efficient_power":0,"efficiency_rotation_interval":900,"log_level":"debug","power_offset":"10"},"schema":[{"name":"power_input_alias","required":true,"type":"string"},{"name":"power_output_alias","optional":true,"type":"string"},{"name":"device_types","required":true,"type":"string"},{"name":"throttle_interval","lengthMin":0.0,"required":true,"type":"float"},{"name":"wait_for_next_message","required":true,"type":"boolean"},{"name":"ct_mac","optional":true,"type":"string"},{"name":"marstek_auto_register_ct_device","optional":true,"type":"boolean"},{"name":"marstek_mailbox","optional":true,"type":"string"},{"name":"marstek_password","optional":true,"type":"string","format":"password"},{"name":"min_efficient_power","lengthMin":0.0,"optional":true,"type":"integer"},{"name":"efficiency_rotation_interval","lengthMin":1.0,"optional":true,"type":"integer"},{"name":"log_level","required":true,"type":"select","options":["critical","error","warning","info","debug"]},{"name":"power_offset","optional":true,"type":"string"},{"name":"power_multiplier","optional":true,"type":"string"},{"name":"dedupe_time_window","lengthMin":0.0,"optional":true,"type":"float"},{"name":"smooth_target_alpha","lengthMin":0.0,"lengthMax":1.0,"optional":true,"type":"float"},{"name":"max_smooth_step","lengthMin":0.0,"optional":true,"type":"float"},{"name":"deadband","lengthMin":0.0,"optional":true,"type":"float"},{"name":"custom_config","optional":true,"type":"string"},{"name":"mqtt_uri","optional":true,"type":"string"}],"arch":["amd64","aarch64"],"machine":[],"homeassistant":null,"url":"https://github.com/tomquist/astrameter","detached":false,"available":true,"build":false,"network":{"12345/udp":12345,"1010/udp":1010,"2220/udp":2220,"2222/udp":2222,"2223/udp":2223},"network_description":null,"host_network":true,"host_pid":false,"host_ipc":false,"host_uts":false,"host_dbus":false,"privileged":[],"full_access":false,"apparmor":"default","icon":false,"logo":false,"changelog":true,"documentation":false,"stdin":false,"hassio_api":true,"hassio_role":"homeassistant","auth_api":false,"homeassistant_api":true,"gpio":false,"usb":false,"uart":false,"kernel_modules":false,"devicetree":false,"udev":false,"docker_api":false,"video":false,"audio":false,"startup":"application","services":["mqtt:want"],"discovery":[],"translations":{"en":{"configuration":{"power_input_alias":{"name":"Power Input Entity ID","description":"The entity ID of the sensor(s) that provide the current power input. For multi-phase setups, enter multiple entity IDs separated by commas (e.g., 'sensor.phase1_in,sensor.phase2_in,sensor.phase3_in')."},"power_output_alias":{"name":"Power Output Entity ID","description":"The entity ID of the sensor(s) that provide the current power output. For multi-phase setups, enter multiple entity IDs separated by commas (e.g., 'sensor.phase1_out,sensor.phase2_out,sensor.phase3_out'). If you only have one sensor for both input and output, leave this empty."},"device_types":{"name":"Emulated Devices","description":"Comma-separated list of devices to emulate (ct002, ct003, shellypro3em, shellyemg3, shellyproem50, shellypro3em_old, shellypro3em_new). Use ct002 or ct003 for multiple storage devices; use a Shelly type otherwise. The device type shellypro3em_old uses port 1010 (used up until B2500 firmware version 224). The device type shellypro3em_new uses the new port 2220 (used for B2500 firmware >=226). If you use shellypro3em, it will use shellypro3em_old and shellypro3em_new simultaneously for backwards compatibility."},"ct_mac":{"name":"CT MAC Override","description":"Optional MAC address of the emulated CT device (the CT MAC addressed in incoming requests). Leave empty to respond regardless of addressed CT MAC and mirror that addressed CT MAC in the response. If set, only requests addressed to this CT MAC are answered."},"throttle_interval":{"name":"Throttling Interval","description":"Minimum time interval (in seconds) between power meter readings. When set to 0, throttling is disabled for maximum performance. For slower data sources or to prevent control instability, set to 1-3 seconds. Supports decimal values (e.g., 1.5 for 1.5 seconds). Increase this value if you're seeing oscillations or instability with slow data sources."},"wait_for_next_message":{"name":"Wait For Fresh Home Assistant Reading","description":"When enabled (default), the app waits briefly (up to 2 seconds) for Home Assistant to push a fresh value before responding to the battery, keeping control loops on the freshest data. Disable this if your source sensor (e.g. a P1 smart meter) updates slower than 2 seconds — turning it off avoids the needless wait and always serves the last-known value immediately."},"log_level":{"name":"Log Level","description":"Controls the verbosity of log messages. Select 'critical' for only critical errors, 'error' for error messages and above, 'warning' for warnings and above, 'info' for informational messages and above (recommended), or 'debug' for detailed debugging information. Use 'debug' for troubleshooting connection or configuration issues."},"custom_config":{"name":"Custom Config","description":"Optional. Name of a custom config.ini file to use instead of the UI configuration. The file must be placed in the app's configuration directory."},"mqtt_uri":{"name":"Custom MQTT URI","description":"Optional. MQTT broker URI for MQTT Insights, e.g. mqtt://user:pass@broker.example.com:1883 (or mqtts:// for TLS). When set, this overrides Home Assistant's internal MQTT broker. Leave empty to use the Mosquitto add-on automatically."},"min_efficient_power":{"name":"Min Efficient Power","description":"Minimum watts each active battery should handle. At low demand, excess batteries are idled so the remaining ones stay above this threshold and operate more efficiently. Set to 0 to disable (default). Example: 2 batteries, 200 W demand, threshold 150 — one battery gets 200 W, the other idles. Only applies to CT002/CT003 device types."},"efficiency_rotation_interval":{"name":"Efficiency Rotation Interval","description":"Seconds between rotating which battery has priority when Min Efficient Power is active (default 900). Ensures fair wear across batteries by periodically swapping which batteries are active and which are idled. Minimum value is 1. Only applies to CT002/CT003 device types."},"marstek_auto_register_ct_device":{"name":"Auto-register Managed CT Device (Marstek)","description":"If enabled, the app signs in to your Marstek account at startup and ensures one managed fake CT device exists for each emulated CT type (ct002 -> HME-4, ct003 -> HME-3). Existing matching devices are reused to avoid duplicates."},"marstek_mailbox":{"name":"Marstek Account Email","description":"Email address used to sign in to your Marstek account for managed CT device registration."},"marstek_password":{"name":"Marstek Account Password","description":"Password used to sign in to your Marstek account for managed CT device registration."},"power_offset":{"name":"Power Offset","description":"Optional. Added to each power value after the multiplier is applied. Single value (e.g. -50) or a comma-separated list (one per phase, e.g. -50,-30,-40). Leave empty to disable."},"power_multiplier":{"name":"Power Multiplier","description":"Optional. Scales each power value (formula: value * POWER_MULTIPLIER + POWER_OFFSET). Single value (e.g. 1.05) or a comma-separated list (one per phase, e.g. 1.05,1.02,1.03). Use -1 to flip polarity. Leave empty to disable."},"dedupe_time_window":{"name":"Deduplication Time Window","description":"Optional. Seconds during which repeat requests from the same battery are ignored. Applies to both CT002/CT003 (keyed by consumer id) and Shelly (keyed by battery IP) emulators. Set to 0 or leave empty to disable."},"smooth_target_alpha":{"name":"Smoothing Alpha (EMA)","description":"Optional. Exponential moving-average factor in (0, 1] applied to power readings from Home Assistant. Smaller values smooth more heavily (e.g. 0.1 = heavy smoothing, 0.5 = light). Leave empty to disable."},"max_smooth_step":{"name":"Max Smoothing Step","description":"Optional. Caps the maximum watt change per cycle when smoothing is active. Use together with Smoothing Alpha to bound per-step jumps (e.g. 200). Leave empty or 0 for unlimited."},"deadband":{"name":"Deadband (W)","description":"Optional. Readings with absolute value below this threshold are reported as 0 W to stop battery micro-cycling near zero demand (e.g. 5). Leave empty or 0 to disable."}}}},"ingress":false,"signed":false,"state":"started","webui":null,"ingress_entry":null,"ingress_url":null,"ingress_port":null,"ingress_panel":null,"audio_input":null,"audio_output":null,"auto_update":false,"ip_address":"172.30.32.1","version":"2.0.2","update_available":false,"watchdog":false,"devices":[],"system_managed":false,"system_managed_config_entry":null}}
[16:39:11] INFO: Resolved add-on slug for HA discovery: 11e5258b_b2500_meter
[16:39:11] INFO: Using Home Assistant's internal MQTT broker
[16:39:11] DEBUG: Requested API resource: http://supervisor/services/mqtt
[16:39:11] DEBUG: Request method: GET
[16:39:11] DEBUG: Request data: {}
[16:39:11] DEBUG: API HTTP Response code: 200
[16:39:11] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"theughei0eangai1oowaimoo4aichae2ohXaiphohwon0eib5aebahchaivoogei","addon":"core_mosquitto"}}
[GENERAL]
DEVICE_TYPE=shellyproem50
THROTTLE_INTERVAL=2.0
ENABLE_WEB_SERVER=true
[CT002]
CT_MAC=
MIN_EFFICIENT_POWER=0
EFFICIENCY_ROTATION_INTERVAL=900
[HOMEASSISTANT]
IP=supervisor
PORT=80
API_PATH_PREFIX=/core
ACCESSTOKEN = REDACTED
WAIT_FOR_NEXT_MESSAGE=true
POWER_CALCULATE=False
CURRENT_POWER_ENTITY=sensor.Gesamtleistung
POWER_OFFSET=10
[MQTT_INSIGHTS]
BROKER=core-mosquitto
PORT=1883
USERNAME=addons
PASSWORD = REDACTED
TLS=false
HA_DISCOVERY=True
ADDON_SLUG=11e5258b_b2500_meter
[16:39:12] INFO: Waiting for Home Assistant to be ready...
[16:39:12] DEBUG: Checking Home Assistant readiness (attempt 1/60)...
[16:39:12] INFO: Home Assistant is ready! Proceeding with AstraMeter startup...
[16:39:12] INFO: Starting AstraMeter with log level: debug
2026-05-20 16:39:15 INFO:astrameter:started astrameter application
2026-05-20 16:39:15 INFO:astrameter:Git commit: 0b5a7b9e0f399daaab6e0310bdb35e4abfd2eca6
2026-05-20 16:39:15 INFO:astrameter:Device Types: ['shellyproem50']
2026-05-20 16:39:15 INFO:astrameter:Device IDs: ['shellyproem50-ec4609c439c1']
2026-05-20 16:39:15 INFO:astrameter:Skip Test: False
2026-05-20 16:39:15 DEBUG:asyncio:Using selector: EpollSelector
2026-05-20 16:39:15 INFO:astrameter:Starting web server...
2026-05-20 16:39:15 INFO:astrameter:Web server started on 0.0.0.0:52500
2026-05-20 16:39:15 INFO:astrameter:Web server started successfully
2026-05-20 16:39:15 INFO:astrameter:Applying power transform (multiplier=[1.0], offset=[10.0]) to HOMEASSISTANT
2026-05-20 16:39:15 INFO:astrameter:Applying global throttling (2.0s) to HOMEASSISTANT
2026-05-20 16:39:15 DEBUG:astrameter:Testing powermeter configuration... (attempt 1/4)
2026-05-20 16:39:15 INFO:astrameter:Home Assistant WebSocket connected to supervisor
2026-05-20 16:39:15 DEBUG:astrameter:Home Assistant: auth required, sending token
2026-05-20 16:39:15 INFO:astrameter:Home Assistant: authenticated
2026-05-20 16:39:45 DEBUG:astrameter:Error on attempt 1: Timeout waiting for Home Assistant state
2026-05-20 16:39:45 INFO:astrameter:Retrying powermeter test in 5 seconds...
2026-05-20 16:39:50 DEBUG:astrameter:Testing powermeter configuration... (attempt 2/4)
2026-05-20 16:40:20 DEBUG:astrameter:Error on attempt 2: Timeout waiting for Home Assistant state
2026-05-20 16:40:20 INFO:astrameter:Retrying powermeter test in 5 seconds...
2026-05-20 16:40:25 DEBUG:astrameter:Testing powermeter configuration... (attempt 3/4)
2026-05-20 16:40:55 DEBUG:astrameter:Error on attempt 3: Timeout waiting for Home Assistant state
2026-05-20 16:40:55 INFO:astrameter:Retrying powermeter test in 5 seconds...
2026-05-20 16:41:00 DEBUG:astrameter:Testing powermeter configuration... (attempt 4/4)
2026-05-20 16:41:30 DEBUG:astrameter:Error on attempt 4: Timeout waiting for Home Assistant state
2026-05-20 16:41:30 INFO:astrameter:Stopping web server...
2026-05-20 16:41:30 INFO:astrameter:Web server stopped
2026-05-20 16:41:30 ERROR:astrameter:Failed to test powermeter after 4 attempts: Timeout waiting for Home Assistant state
Traceback (most recent call last):
  File "/app/.venv/lib/python3.12/site-packages/astrameter/main.py", line 91, in test_powermeter
    await powermeter.wait_for_message(timeout=30)
  File "/app/.venv/lib/python3.12/site-packages/astrameter/powermeter/wrappers/base.py", line 17, in wait_for_message
    await self.wrapped_powermeter.wait_for_message(timeout)
  File "/app/.venv/lib/python3.12/site-packages/astrameter/powermeter/wrappers/base.py", line 17, in wait_for_message
    await self.wrapped_powermeter.wait_for_message(timeout)
  File "/app/.venv/lib/python3.12/site-packages/astrameter/powermeter/homeassistant.py", line 278, in wait_for_message
    raise TimeoutError("Timeout waiting for Home Assistant state") from None
TimeoutError: Timeout waiting for Home Assistant state
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/app/.venv/lib/python3.12/site-packages/astrameter/main.py", line 737, in main
    asyncio.run(
  File "/usr/lib/python3.12/asyncio/runners.py", line 195, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/asyncio/base_events.py", line 691, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.12/site-packages/astrameter/main.py", line 464, in async_main
    await test_powermeter(powermeter, client_filter)
  File "/app/.venv/lib/python3.12/site-packages/astrameter/main.py", line 109, in test_powermeter
    raise RuntimeError(
RuntimeError: Failed to test powermeter after 4 attempts: Timeout waiting for Home Assistant state
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[arturwins]

Ich habe mein Setup wieder zum Laufen bekommen, jedoch funktioniert es bei mir nur wenn ich SKIP_POWERMETER_TEST = True setze. Dies ist nur bei Verwendung der Config.ini möglich, daher habe ich meine Config.ini nochmal überarbeitet und korrigiert. Nutze ich die Standardeinstellung läuft der Powermeter-Test immer in den Timeout und die App wird gestoppt. Mit der B2500 1.0.8 hat alles mit den selben Einstellungen ohne Probleme funktioniert.

Folgend meine Config.ini

[GENERAL]
DEVICE_TYPE= shellyproem50
SKIP_POWERMETER_TEST = True
THROTTLE_INTERVAL = 2

[MQTT]
BROKER = 192.168.178.105
PORT = 1883
TOPIC = Zaehler/Gesamtleistung

Hast du eine Idee warum der Powermeter-Test bei mir immer in den Timeout läuft?
Nochmal danke für die für den Support und die AstraMeter-App!!!!