Probleme mit hame-relay und hm2mqtt (B2500)

[JWRu]

Ich bin ein Neueinsteiger - habe seit kurzer Zeit einen Marstek B2500 (HMJ-2 - V166.6).
Der Speicher läuft mit der Cloud, die darin vorhandene Kopplung (beta) mit dem EcoTracker funktioniert recht gut.
Ich würde den Speicher gerne in der Cloud lassen und die Daten des B2500 parallel per MQTT an mein Automatisierungssystem (FHEM) senden.
Dafür habe ich hame-relay und hm2mqtt als Docker-Container per Portainer auf meinem Synology-NAS installiert. Ich habe wie empfohlen die Daten mit einer zweite Mailadresse geteilt, die ich in der Konfiguration von hame-relay nutze.
Hier ist die Konfiguration von hame-relay (< und > wird zur Anonymisierung benutzt):

 {
  "broker_url": "mqtt://<MQTT-user>:<MQTT-password>@<MQTT-Broker-URL>:1883",
  "username": "<Mail-Adresse2>",
  "password": "<Password Mail2>",
  "inverse_forwarding": false,
  "default_broker_id": "hame-2024",
  "inverse_forwarding_device_ids": "<24-stellige Device-ID>",
  "devices": [
    { 
      "device_id": "<24-stellige Device-ID>", 
      "mac": "<BT-MAC-Adresse>", 
      "type": "HMJ-2", 
      "version": 116,
      "inverse_forwarding": true,
      "broker_id": "hame-2025"
    }
  ]
}

hame-relay startet einwandfrei (Status "healthy"):

[2026-05-03 15:18:57] INFO: Fetching devices from Hame API...
[2026-05-03 15:18:57] INFO: Fetching device token for <Mail-Adresse2>...
[2026-05-03 15:18:58] INFO: Fetching device list...
[2026-05-03 15:18:58] INFO: Successfully fetched 1 devices from Hame API
[2026-05-03 15:18:58] INFO: Successfully retrieved 1 devices from API
[2026-05-03 15:18:58] INFO: Selective inverse forwarding enabled for device IDs: <24-stellige Device-ID>
[2026-05-03 15:18:58] INFO: Auto-selected broker hame-2025 for device <24-stellige Device-ID>
[2026-05-03 15:18:58] INFO: 
Configured devices: 1 total
[2026-05-03 15:18:58] INFO: ------------------
[2026-05-03 15:18:58] INFO: Device 1:
[2026-05-03 15:18:58] INFO:   Name: HM_B2500_385a
[2026-05-03 15:18:58] INFO:   Device ID: <24-stellige Device-ID>
[2026-05-03 15:18:58] INFO:   Remote ID: <32-stellige Remote-ID>
[2026-05-03 15:18:58] INFO:   MAC: <BT-MAC-Adresse>
[2026-05-03 15:18:58] INFO:   Type: HMJ-2
[2026-05-03 15:18:58] INFO:   Version: 116
[2026-05-03 15:18:58] INFO:   Broker: hame-2025
[2026-05-03 15:18:58] INFO:   Inverse Forwarding: true
[2026-05-03 15:18:58] INFO:   Use Remote Topic ID: false
[2026-05-03 15:18:58] INFO: ------------------
[2026-05-03 15:18:58] INFO: 
[2026-05-03 15:18:58] INFO: Health server listening on port 8080
[2026-05-03 15:18:58] INFO: [hame-2025] Connected to config broker
[2026-05-03 15:18:58] INFO: [hame-2025] Subscribed to local broker topics
[2026-05-03 15:18:58] INFO: [hame-2025] Connected to remote broker
[2026-05-03 15:18:58] INFO: [hame-2025] Subscribed to remote broker topics

Nach dem Start tauchem im Log von hame-relay keine Meldungen mehr auf.

hm2mqtt habe ich mit der folgenden Docker-Compose-Datei installiert:

version: '3.7'

services:
  hm2mqtt:
    container_name: hm2mqtt
    image: ghcr.io/tomquist/hm2mqtt:latest
    restart: unless-stopped
    environment:
      - MQTT_BROKER_URL=mqtt://<MQTT-Broker-URL>:1883
      - MQTT_USERNAME=<MQTT-user>
      - MQTT_PASSWORD=<MQTT-password>
      - POLL_CELL_DATA=true
      - POLL_EXTRA_BATTERY_DATA=true
      - POLL_CALIBRATION_DATA=true
      - DEVICE_0=HMJ-2:<BT-MAC-Adresse>

hm2mqtt startet auch einwandfrei mit dem folgenden Log:

[15:40:08] INFO: Starting hm2mqtt application...
[15:40:08] INFO: Environment: production
[15:40:08] INFO: MQTT Proxy: disabled
[15:40:08] INFO: Registering device: HMJ-2:<BT-MAC-Adresse> from DEVICE_0=HMJ-2:<BT-MAC-Adresse>
[15:40:08] INFO: Found 1 device(s)
[15:40:08] INFO: - Device: HMJ-2:<BT-MAC-Adresse>
[15:40:08] INFO: Initializing topics for device: HMJ-2:<BT-MAC-Adresse>
[15:40:08] INFO: Connecting to MQTT broker at mqtt://<MQTT-Broker-URL>:1883 with client ID hm2mqtt-6b7632
[15:40:09] INFO: MQTT Proxy is disabled (set MQTT_PROXY_ENABLED=true to enable)
[15:40:09] INFO: Connected to MQTT broker
[15:40:24] WARN: No response received from <BT-MAC-Adresse> within timeout period
[15:41:24] WARN: No response received from <BT-MAC-Adresse> within timeout period
[15:42:24] WARN: No response received from <BT-MAC-Adresse> within timeout period

hm2mqtt verbindet sich beim Start erfolgreich mit meinem MQTT-Broker und legt topics an.
Anschließend gibt es aber im Minutentakt die Fehlermeldungen "No response..."

Nach dem Start von hm2mqtt tauchen auch im Log von hame-relay wieder Meldungen auf:

[2026-05-03 15:40:30] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/<BT-MAC-Adresse>/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl
[2026-05-03 15:40:30] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/<BT-MAC-Adresse>/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl
[2026-05-03 15:40:30] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/<BT-MAC-Adresse>/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl
[2026-05-03 15:40:30] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/<BT-MAC-Adresse>/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl
[2026-05-03 15:41:09] INFO: [hame-2025] Devices configured with inverse_forwarding get rate limited. Rate limiting message with code cd=1 for device HMJ-2:<24-stellige Device-ID>:<BT-MAC-Adresse>. Please wait for 21329ms before sending another message. Use inverse_forwarding=false to avoid rate limiting.
[2026-05-03 15:41:09] INFO: [hame-2025] Devices configured with inverse_forwarding get rate limited. Rate limiting message with code cd=16 for device HMJ-2:<24-stellige Device-ID>:<BT-MAC-Adresse>. Please wait for 21241ms before sending another message. Use inverse_forwarding=false to avoid rate limiting.
[2026-05-03 15:41:09] INFO: [hame-2025] Devices configured with inverse_forwarding get rate limited. Rate limiting message with code cd=13 for device HMJ-2:<24-stellige Device-ID>:<BT-MAC-Adresse>. Please wait for 21133ms before sending another message. Use inverse_forwarding=false to avoid rate limiting.
[2026-05-03 15:41:09] INFO: [hame-2025] Devices configured with inverse_forwarding get rate limited. Rate limiting message with code cd=21 for device HMJ-2:<24-stellige Device-ID>:<BT-MAC-Adresse>. Please wait for 21006ms before sending another message. Use inverse_forwarding=false to avoid rate limiting.
[2026-05-03 15:42:09] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/18cedf98385a/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl
[2026-05-03 15:42:09] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/18cedf98385a/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl
[2026-05-03 15:42:09] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/18cedf98385a/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl
[2026-05-03 15:42:09] INFO: [hame-2025] Forwarded message from local to remote: hame_energy/HMJ-2/App/18cedf98385a/ctrl -> marstek_energy/HMJ-2/App/<32-stellige Remote-ID>/ctrl

Jetzt bin ich leider am Ende meiner Kenntnisse angekommen und hoffe, dass mir jemand aus der Community weiterhelfen kann.