HMJ-2 stopped responding after HAOS reboot - no telemetry, app offline

[joebac25]

Device Model

B2500D

Firmware Version

116

Installation Method

Home Assistant

Issue Description

HMJ-2 stopped responding - App offline, no telemetry, no BLE response

Hello,

I'm experiencing a communication problem with my Marstek / HAME HMJ-2 and would appreciate any help.

Environment

• Home Assistant OS 18.1
• Home Assistant Core 2026.7.2
• hm2mqtt Add-on 1.8.1
• Mosquitto Broker (Home Assistant Add-on)
• Device: HMJ-2
• Device ID: 18cedf985a05
• Firmware reported by MQTT Discovery: 116.6

Timeline

The system had been working correctly for several weeks.

After a Home Assistant OS update followed by a reboot (around 2026-07-04) the HMJ-2 became unreachable.

Since then:

• Marstek App reports the battery offline.
• hm2mqtt no longer receives any response.
• Home Assistant entities became unavailable.
• No telemetry is published anymore.

hm2mqtt configuration

pollingInterval: 10
responseTimeout: 45
enableCellData: false
enableCalibrationData: false
enableExtraBatteryData: false
allowedConsecutiveTimeouts: 8
topicPrefix: hm2mqtt
mqttProxyEnabled: false
log_level: info

devices:

• deviceType: HMJ-2
  deviceId: 18cedf985a05

hm2mqtt log

hm2mqtt starts correctly and connects successfully to the MQTT broker.

Afterwards it continuously reports:

WARN: No response received from 18cedf985a05 within timeout period

No successful communication ever occurs.

MQTT

MQTT Discovery works correctly.

All Home Assistant discovery topics are published correctly.

However, the topic

hm2mqtt/HMJ-2/device/18cedf985a05/data

never publishes any payload.

Only availability topics are published.

Network

The HMJ-2 is still reachable on the local network.

Ping to 192.168.25.63 works reliably.

HTTP and HTTPS connections are refused (which I assume is expected because the device has no web interface).

Bluetooth

The device is visible during BLE scanning.

However:

• bluetoothctl detects the device.
• bluetoothctl cannot establish a connection.
• hm2mqtt also never receives any BLE response.

Current behaviour

The inverter still produces PV power during daytime.

However:

• the Marstek App reports the battery offline.
• Home Assistant receives no battery telemetry.
• the battery appears to no longer discharge during the night (house imports power from the grid instead).

What I already checked

• MQTT broker is working correctly.
• hm2mqtt starts normally.
• MQTT Discovery works correctly.
• MQTT topics are created.
• No payload is ever published on hm2mqtt/HMJ-2/device/18cedf985a05/data.
• The battery is still reachable via ICMP ping.
• The Marstek App also cannot communicate with the battery.

Questions

1. Is this a known issue with firmware 116.6?

2. Can the HMJ-2 enter a state where:

   • BLE no longer responds
   • the app reports the battery offline
   • hm2mqtt receives only timeouts
   • but the inverter still continues normal daytime PV operation?

3. Is there any recovery procedure besides physically power cycling the unit?

4. Could the communication stack (BLE / WiFi / local MQTT) become stuck after a reboot?

I can provide complete hm2mqtt logs, MQTT traces and Home Assistant diagnostics if needed.

Thank you very much.

hm2mqtt Configuration

hm2mqtt Logs

Hame Relay Configuration

Hame Relay Logs

```Additional information:
The battery still responds to ICMP ping on its local IP address.
The Marstek App also reports the battery offline.
MQTT discovery works correctly.
No payload is ever published on hm2mqtt/HMJ-2/device/<id>/data.
The inverter still produces PV power during daytime.
The battery no longer appears to discharge during the night.
bluetoothctl can discover the device but cannot establish a connection.

[github-actions[bot]]

Thanks for the report — I can take a look, but I’ll need logs to debug this.

Please add:

1. hm2mqtt logs (DEBUG)

   • Home Assistant → Settings → Add-ons → hm2mqtt
   • In the add-on configuration, set:
     • log_level: debug
     • debug: true
   • Restart the add-on
   • Then paste the relevant log excerpt here (around the time the problem happens)

2. Hame Relay logs (DEBUG)

   • In the Hame Relay add-on, enable debug logging (log level debug) and restart
   • Paste the relevant log excerpt here

Important: please redact/replace any IDs (deviceId/MAC, tokens, MQTT credentials, etc.) before posting.

[joebac25]

here are the logs: Hame Relay

[2026-07-11 04:23:19] INFO:
Configured devices: 2 total
[2026-07-11 04:23:19] INFO: ------------------
[2026-07-11 04:23:19] INFO: Device 1:
[2026-07-11 04:23:19] INFO:   Name: AstraMeter CT002
[2026-07-11 04:23:19] INFO:   Device ID: 02b250c3de3b
[2026-07-11 04:23:19] INFO:   Remote ID: 628891ddb42c0f09969d3bb3XXXXXXXX
[2026-07-11 04:23:19] INFO:   MAC: 02b250c3de3b
[2026-07-11 04:23:19] INFO:   Type: HME-4
[2026-07-11 04:23:19] INFO:   Version: 121
[2026-07-11 04:23:19] INFO:   Broker: hame-2025
[2026-07-11 04:23:19] INFO:   Inverse Forwarding: false
[2026-07-11 04:23:19] INFO:   Use Remote Topic ID: false
[2026-07-11 04:23:19] INFO: ------------------
[2026-07-11 04:23:19] INFO: Device 2:
[2026-07-11 04:23:19] INFO:   Name: HM_B2500_5a05
[2026-07-11 04:23:19] INFO:   Device ID: 360111505357363937034f57
[2026-07-11 04:23:19] INFO:   Remote ID: a0E0w000S0nVW0Q0XXXXXXXX
[2026-07-11 04:23:19] INFO:   MAC: 18cedf985a05
[2026-07-11 04:23:19] INFO:   Type: HMJ-2
[2026-07-11 04:23:19] INFO:   Version: 116
[2026-07-11 04:23:19] INFO:   Broker: hame-2025
[2026-07-11 04:23:19] INFO:   Inverse Forwarding: false
[2026-07-11 04:23:19] INFO:   Use Remote Topic ID: false
[2026-07-11 04:23:19] INFO: ------------------
[2026-07-11 04:23:19] INFO:
[2026-07-11 04:23:19] INFO: Health server listening on port 8080
[2026-07-11 04:23:20] INFO: [hame-2025] Connected to config broker
[2026-07-11 04:23:20] INFO: [hame-2025] Subscribed to local broker topics
[2026-07-11 04:23:20] INFO: [hame-2025] Connected to remote broker
[2026-07-11 04:23:20] INFO: [hame-2025] Subscribed to remote broker topics
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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Hame Relay
Connect B2500 storage to Home Assistant while keeping mobile app functionality

Add-on version: 1.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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 INFO
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
[06:29:25] INFO: Generating config file...
[06:29:26] INFO: Username and password found in configuration.
[06:29:26] INFO: Configuration file generated successfully.
[06:29:26] INFO: Starting MQTT forwarder...
[2026-07-11 04:29:27] INFO: Fetching devices from Hame API...
[2026-07-11 04:29:27] INFO: Fetching device token for mail@jochenbackhaus.de...
[2026-07-11 04:29:28] INFO: Fetching device list...
[2026-07-11 04:29:28] INFO: Successfully fetched 2 devices from Hame API
[2026-07-11 04:29:28] INFO: Successfully retrieved 2 devices from API
[2026-07-11 04:29:28] INFO: Auto-selected broker hame-2025 for device 02b250c3de3b
[2026-07-11 04:29:28] INFO: Auto-selected broker hame-2025 for device 360111505357363937034f57
[2026-07-11 04:29:28] INFO: Device 02b250c3de3b (HME-4): AstraMeter synthetic MAC — inverse forwarding disabled
[2026-07-11 04:29:28] INFO:
Configured devices: 2 total
[2026-07-11 04:29:28] INFO: ------------------
[2026-07-11 04:29:28] INFO: Device 1:
[2026-07-11 04:29:28] INFO:   Name: AstraMeter CT002
[2026-07-11 04:29:28] INFO:   Device ID: 02b250c3de3b
[2026-07-11 04:29:28] INFO:   Remote ID: 628891ddb42c0f09969d3bb3XXXXXXXX
[2026-07-11 04:29:28] INFO:   MAC: 02b250c3de3b
[2026-07-11 04:29:28] INFO:   Type: HME-4
[2026-07-11 04:29:28] INFO:   Version: 121
[2026-07-11 04:29:28] INFO:   Broker: hame-2025
[2026-07-11 04:29:28] INFO:   Inverse Forwarding: false
[2026-07-11 04:29:28] INFO:   Use Remote Topic ID: false
[2026-07-11 04:29:28] INFO: ------------------
[2026-07-11 04:29:28] INFO: Device 2:
[2026-07-11 04:29:28] INFO:   Name: HM_B2500_5a05
[2026-07-11 04:29:28] INFO:   Device ID: 360111505357363937034f57
[2026-07-11 04:29:28] INFO:   Remote ID: a0E0w000S0nVW0Q0XXXXXXXX
[2026-07-11 04:29:28] INFO:   MAC: 18cedf985a05
[2026-07-11 04:29:28] INFO:   Type: HMJ-2
[2026-07-11 04:29:28] INFO:   Version: 116
[2026-07-11 04:29:28] INFO:   Broker: hame-2025
[2026-07-11 04:29:28] INFO:   Inverse Forwarding: false
[2026-07-11 04:29:28] INFO:   Use Remote Topic ID: false
[2026-07-11 04:29:28] INFO: ------------------
[2026-07-11 04:29:28] INFO:
[2026-07-11 04:29:28] INFO: Health server listening on port 8080
[2026-07-11 04:29:29] INFO: [hame-2025] Connected to config broker
[2026-07-11 04:29:29] INFO: [hame-2025] Subscribed to local broker topics
[2026-07-11 04:29:29] INFO: [hame-2025] Connected to remote broker
[2026-07-11 04:29:29] INFO: [hame-2025] Subscribed to remote broker topics
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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Hame Relay
Connect B2500 storage to Home Assistant while keeping mobile app functionality

Add-on version: 1.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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 INFO
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
[06:35:11] INFO: Generating config file...
[06:35:12] INFO: Username and password found in configuration.
[06:35:12] INFO: Configuration file generated successfully.
[06:35:12] INFO: Starting MQTT forwarder...
[2026-07-11 04:35:14] INFO: Fetching devices from Hame API...
[2026-07-11 04:35:14] INFO: Fetching device token for mail@jochenbackhaus.de...
[2026-07-11 04:35:14] INFO: Fetching device list...
[2026-07-11 04:35:14] INFO: Successfully fetched 2 devices from Hame API
[2026-07-11 04:35:14] INFO: Successfully retrieved 2 devices from API
[2026-07-11 04:35:14] INFO: Auto-selected broker hame-2025 for device 02b250c3de3b
[2026-07-11 04:35:14] INFO: Auto-selected broker hame-2025 for device 360111505357363937034f57
[2026-07-11 04:35:14] INFO: Device 02b250c3de3b (HME-4): AstraMeter synthetic MAC — inverse forwarding disabled
[2026-07-11 04:35:14] INFO:
Configured devices: 2 total
[2026-07-11 04:35:14] INFO: ------------------
[2026-07-11 04:35:14] INFO: Device 1:
[2026-07-11 04:35:14] INFO:   Name: AstraMeter CT002
[2026-07-11 04:35:14] INFO:   Device ID: 02b250c3de3b
[2026-07-11 04:35:14] INFO:   Remote ID: 628891ddb42c0f09969d3bb3XXXXXXXX
[2026-07-11 04:35:14] INFO:   MAC: 02b250c3de3b
[2026-07-11 04:35:14] INFO:   Type: HME-4
[2026-07-11 04:35:14] INFO:   Version: 121
[2026-07-11 04:35:14] INFO:   Broker: hame-2025
[2026-07-11 04:35:14] INFO:   Inverse Forwarding: false
[2026-07-11 04:35:14] INFO:   Use Remote Topic ID: false
[2026-07-11 04:35:14] INFO: ------------------
[2026-07-11 04:35:14] INFO: Device 2:
[2026-07-11 04:35:14] INFO:   Name: HM_B2500_5a05
[2026-07-11 04:35:14] INFO:   Device ID: 360111505357363937034f57
[2026-07-11 04:35:14] INFO:   Remote ID: a0E0w000S0nVW0Q0XXXXXXXX
[2026-07-11 04:35:14] INFO:   MAC: 18cedf985a05
[2026-07-11 04:35:14] INFO:   Type: HMJ-2
[2026-07-11 04:35:14] INFO:   Version: 116
[2026-07-11 04:35:14] INFO:   Broker: hame-2025
[2026-07-11 04:35:14] INFO:   Inverse Forwarding: false
[2026-07-11 04:35:14] INFO:   Use Remote Topic ID: false
[2026-07-11 04:35:14] INFO: ------------------
[2026-07-11 04:35:14] INFO:
[2026-07-11 04:35:15] INFO: Health server listening on port 8080
[2026-07-11 04:35:15] INFO: [hame-2025] Connected to remote broker
[2026-07-11 04:35:15] INFO: [hame-2025] Subscribed to remote broker topics
[2026-07-11 04:35:15] INFO: [hame-2025] Connected to config broker
[2026-07-11 04:35:15] INFO: [hame-2025] Subscribed to local broker topics
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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Hame Relay
Connect B2500 storage to Home Assistant while keeping mobile app functionality

Add-on version: 1.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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 INFO
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
[08:46:53] INFO: Generating config file...
[08:46:54] INFO: Username and password found in configuration.
[08:46:54] INFO: Configuration file generated successfully.
[08:46:54] INFO: Starting MQTT forwarder...
[2026-07-11 06:46:55] INFO: Fetching devices from Hame API...
[2026-07-11 06:46:55] INFO: Fetching device token for mail@jochenbackhaus.de...
[2026-07-11 06:46:55] INFO: Fetching device list...
[2026-07-11 06:46:56] INFO: Successfully fetched 2 devices from Hame API
[2026-07-11 06:46:56] INFO: Successfully retrieved 2 devices from API
[2026-07-11 06:46:56] INFO: Auto-selected broker hame-2025 for device 02b250c3de3b
[2026-07-11 06:46:56] INFO: Auto-selected broker hame-2025 for device 360111505357363937034f57
[2026-07-11 06:46:56] INFO: Device 02b250c3de3b (HME-4): AstraMeter synthetic MAC — inverse forwarding disabled
[2026-07-11 06:46:56] INFO:
Configured devices: 2 total
[2026-07-11 06:46:56] INFO: ------------------
[2026-07-11 06:46:56] INFO: Device 1:
[2026-07-11 06:46:56] INFO:   Name: AstraMeter CT002
[2026-07-11 06:46:56] INFO:   Device ID: 02b250c3de3b
[2026-07-11 06:46:56] INFO:   Remote ID: 628891ddb42c0f09969d3bb3XXXXXXXX
[2026-07-11 06:46:56] INFO:   MAC: 02b250c3de3b
[2026-07-11 06:46:56] INFO:   Type: HME-4
[2026-07-11 06:46:56] INFO:   Version: 121
[2026-07-11 06:46:56] INFO:   Broker: hame-2025
[2026-07-11 06:46:56] INFO:   Inverse Forwarding: false
[2026-07-11 06:46:56] INFO:   Use Remote Topic ID: false
[2026-07-11 06:46:56] INFO: ------------------
[2026-07-11 06:46:56] INFO: Device 2:
[2026-07-11 06:46:56] INFO:   Name: HM_B2500_5a05
[2026-07-11 06:46:56] INFO:   Device ID: 360111505357363937034f57
[2026-07-11 06:46:56] INFO:   Remote ID: a0E0w000S0nVW0Q0XXXXXXXX
[2026-07-11 06:46:56] INFO:   MAC: 18cedf985a05
[2026-07-11 06:46:56] INFO:   Type: HMJ-2
[2026-07-11 06:46:56] INFO:   Version: 116
[2026-07-11 06:46:56] INFO:   Broker: hame-2025
[2026-07-11 06:46:56] INFO:   Inverse Forwarding: false
[2026-07-11 06:46:56] INFO:   Use Remote Topic ID: false
[2026-07-11 06:46:56] INFO: ------------------
[2026-07-11 06:46:56] INFO:
[2026-07-11 06:46:56] INFO: Health server listening on port 8080
[2026-07-11 06:46:56] INFO: [hame-2025] Connected to remote broker
[2026-07-11 06:46:56] INFO: [hame-2025] Subscribed to remote broker topics
[2026-07-11 06:46:56] INFO: [hame-2025] Connected to config broker
[2026-07-11 06:46:56] INFO: [hame-2025] Subscribed to local broker topics
[2026-07-11 06:49:56] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:50:00] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:50:00] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:50:01] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:50:02] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:50:33] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:50:34] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:50:36] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:51:13] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:51:13] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
[2026-07-11 06:51:15] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl -> hame_energy/HME-4/App/02b250c3de3b/ctrl
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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Hame Relay
Connect B2500 storage to Home Assistant while keeping mobile app functionality

Add-on version: 1.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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
[09:01:48] DEBUG: Requested API resource: http://supervisor/services/mqtt
[09:01:48] DEBUG: Request method: GET
[09:01:48] DEBUG: Request data: {}
[09:01:48] DEBUG: API HTTP Response code: 200
[09:01:48] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi","addon":"core_mosquitto"}}
[09:01:49] INFO: Generating config file...
[09:01:49] INFO: Username and password found in configuration.
[09:01:50] INFO: Configuration file generated successfully.
[09:01:50] INFO: Starting MQTT forwarder...
[2026-07-11 07:01:51] DEBUG: Loaded url from file: certs/hame-2024-url
[2026-07-11 07:01:51] DEBUG: Loaded ca from file: certs/ca.crt
[2026-07-11 07:01:51] DEBUG: Loaded cert from file: certs/hame-2024.crt
[2026-07-11 07:01:51] DEBUG: Loaded key from file: certs/hame-2024.key
[2026-07-11 07:01:51] DEBUG: Loaded url from file: certs/hame-2025-url
[2026-07-11 07:01:51] DEBUG: Loaded ca from file: certs/ca.crt
[2026-07-11 07:01:51] DEBUG: Loaded cert from file: certs/hame-2025.crt
[2026-07-11 07:01:51] DEBUG: Loaded key from file: certs/hame-2025.key
[2026-07-11 07:01:51] DEBUG: Loaded topic_encryption_key from file: certs/hame-2025-topic-encryption-key
[2026-07-11 07:01:51] INFO: Fetching devices from Hame API...
[2026-07-11 07:01:51] INFO: Fetching device token for mail@jochenbackhaus.de...
[2026-07-11 07:01:51] INFO: Fetching device list...
[2026-07-11 07:01:52] INFO: Fetch device list failed with non-retryable error: Unexpected API response from device list: 8 - token无效. Not retrying.
[2026-07-11 07:01:52] INFO: Fetch devices from Hame API failed with non-retryable error: Unexpected API response from device list: 8 - token无效. Not retrying.
[2026-07-11 07:01:52] ERROR: Failed to fetch devices from Hame API
err: {
"type": "Error",
"message": "Unexpected API response from device list: 8 - token无效",
"stack":
Error: Unexpected API response from device list: 8 - token无效
at file:///app/dist/hame_api.js:128:23
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async withRetry (file:///app/dist/hame_api.js:48:28)
at async withRetry.maxRetries (file:///app/dist/hame_api.js:136:26)
at async withRetry (file:///app/dist/hame_api.js:48:28)
at async start (file:///app/dist/main.js:118:35)
}
[2026-07-11 07:01:52] ERROR: Failed to start MQTT forwarder
err: {
"type": "Error",
"message": "Unable to fetch device information from Hame API: Unexpected API response from device list: 8 - token无效",
"stack":
Error: Unable to fetch device information from Hame API: Unexpected API response from device list: 8 - token无效
at start (file:///app/dist/main.js:142:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
}
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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Hame Relay
Connect B2500 storage to Home Assistant while keeping mobile app functionality

Add-on version: 1.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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
[09:02:00] DEBUG: Requested API resource: http://supervisor/services/mqtt
[09:02:00] DEBUG: Request method: GET
[09:02:00] DEBUG: Request data: {}
[09:02:00] DEBUG: API HTTP Response code: 200
[09:02:00] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi","addon":"core_mosquitto"}}
[09:02:01] INFO: Generating config file...
[09:02:02] INFO: Username and password found in configuration.
[09:02:02] INFO: Configuration file generated successfully.
[09:02:02] INFO: Starting MQTT forwarder...
[2026-07-11 07:02:03] DEBUG: Loaded url from file: certs/hame-2024-url
[2026-07-11 07:02:03] DEBUG: Loaded ca from file: certs/ca.crt
[2026-07-11 07:02:03] DEBUG: Loaded cert from file: certs/hame-2024.crt
[2026-07-11 07:02:03] DEBUG: Loaded key from file: certs/hame-2024.key
[2026-07-11 07:02:03] DEBUG: Loaded url from file: certs/hame-2025-url
[2026-07-11 07:02:03] DEBUG: Loaded ca from file: certs/ca.crt
[2026-07-11 07:02:03] DEBUG: Loaded cert from file: certs/hame-2025.crt
[2026-07-11 07:02:03] DEBUG: Loaded key from file: certs/hame-2025.key
[2026-07-11 07:02:03] DEBUG: Loaded topic_encryption_key from file: certs/hame-2025-topic-encryption-key
[2026-07-11 07:02:03] INFO: Fetching devices from Hame API...
[2026-07-11 07:02:03] INFO: Fetching device token for mail@jochenbackhaus.de...
[2026-07-11 07:02:04] INFO: Fetching device list...
[2026-07-11 07:02:04] INFO: Fetch device list failed with non-retryable error: Unexpected API response from device list: 8 - token无效. Not retrying.
[2026-07-11 07:02:04] INFO: Fetch devices from Hame API failed with non-retryable error: Unexpected API response from device list: 8 - token无效. Not retrying.
[2026-07-11 07:02:04] ERROR: Failed to fetch devices from Hame API
err: {
"type": "Error",
"message": "Unexpected API response from device list: 8 - token无效",
"stack":
Error: Unexpected API response from device list: 8 - token无效
at file:///app/dist/hame_api.js:128:23
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async withRetry (file:///app/dist/hame_api.js:48:28)
at async withRetry.maxRetries (file:///app/dist/hame_api.js:136:26)
at async withRetry (file:///app/dist/hame_api.js:48:28)
at async start (file:///app/dist/main.js:118:35)
}
[2026-07-11 07:02:04] ERROR: Failed to start MQTT forwarder
err: {
"type": "Error",
"message": "Unable to fetch device information from Hame API: Unexpected API response from device list: 8 - token无效",
"stack":
Error: Unable to fetch device information from Hame API: Unexpected API response from device list: 8 - token无效
at start (file:///app/dist/main.js:142:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
}
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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: Hame Relay
Connect B2500 storage to Home Assistant while keeping mobile app functionality

Add-on version: 1.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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
[09:02:12] DEBUG: Requested API resource: http://supervisor/services/mqtt
[09:02:12] DEBUG: Request method: GET
[09:02:12] DEBUG: Request data: {}
[09:02:12] DEBUG: API HTTP Response code: 200
[09:02:12] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi","addon":"core_mosquitto"}}
[09:02:13] INFO: Generating config file...
[09:02:14] INFO: Username and password found in configuration.
[09:02:14] INFO: Configuration file generated successfully.
[09:02:14] INFO: Starting MQTT forwarder...
[2026-07-11 07:02:15] DEBUG: Loaded url from file: certs/hame-2024-url
[2026-07-11 07:02:15] DEBUG: Loaded ca from file: certs/ca.crt
[2026-07-11 07:02:15] DEBUG: Loaded cert from file: certs/hame-2024.crt
[2026-07-11 07:02:15] DEBUG: Loaded key from file: certs/hame-2024.key
[2026-07-11 07:02:15] DEBUG: Loaded url from file: certs/hame-2025-url
[2026-07-11 07:02:15] DEBUG: Loaded ca from file: certs/ca.crt
[2026-07-11 07:02:15] DEBUG: Loaded cert from file: certs/hame-2025.crt
[2026-07-11 07:02:15] DEBUG: Loaded key from file: certs/hame-2025.key
[2026-07-11 07:02:15] DEBUG: Loaded topic_encryption_key from file: certs/hame-2025-topic-encryption-key
[2026-07-11 07:02:15] INFO: Fetching devices from Hame API...
[2026-07-11 07:02:15] INFO: Fetching device token for mail@jochenbackhaus.de...
[2026-07-11 07:02:16] INFO: Fetching device list...
[2026-07-11 07:02:16] INFO: Successfully fetched 2 devices from Hame API
[2026-07-11 07:02:16] INFO: Successfully retrieved 2 devices from API
[2026-07-11 07:02:16] DEBUG: Device 02b250c3de3b (HME-4): inverse_forwarding = true (automatic)
[2026-07-11 07:02:16] DEBUG: Device 360111505357363937034f57 (HMJ-2): inverse_forwarding = false (selective)
[2026-07-11 07:02:16] INFO: Auto-selected broker hame-2025 for device 02b250c3de3b
[2026-07-11 07:02:16] INFO: Auto-selected broker hame-2025 for device 360111505357363937034f57
[2026-07-11 07:02:16] DEBUG: Validating 2 devices...
[2026-07-11 07:02:16] DEBUG: Found 2 devices in config file
[2026-07-11 07:02:16] DEBUG: Validating device: 02b250c3de3b
[2026-07-11 07:02:16] DEBUG: Validating device: 360111505357363937034f57
[2026-07-11 07:02:16] INFO: Device 02b250c3de3b (HME-4): AstraMeter synthetic MAC — inverse forwarding disabled
[2026-07-11 07:02:16] DEBUG: Using broker ID: hame-2025 for device 02b250c3de3b
[2026-07-11 07:02:16] DEBUG: AstraMeter synthetic MAC: remote_id from topic encryption for device 02b250c3de3b
[2026-07-11 07:02:16] DEBUG: Adding device 02b250c3de3b to broker hame-2025
[2026-07-11 07:02:16] DEBUG: Using broker ID: hame-2025 for device 360111505357363937034f57
[2026-07-11 07:02:16] DEBUG: Device 360111505357363937034f57 supports CommonHelper.cq method, using salt-based calculation
[2026-07-11 07:02:16] DEBUG: Calculated remote ID using CommonHelper.cq: a0E0w000S0nVW0Q0XXXXXXXX for device 360111505357363937034f57
[2026-07-11 07:02:16] DEBUG: Adding device 360111505357363937034f57 to broker hame-2025
[2026-07-11 07:02:16] INFO:
Configured devices: 2 total
[2026-07-11 07:02:16] INFO: ------------------
[2026-07-11 07:02:16] INFO: Device 1:
[2026-07-11 07:02:16] INFO:   Name: AstraMeter CT002
[2026-07-11 07:02:16] INFO:   Device ID: 02b250c3de3b
[2026-07-11 07:02:16] INFO:   Remote ID: 628891ddb42c0f09969d3bb3XXXXXXXX
[2026-07-11 07:02:16] INFO:   MAC: 02b250c3de3b
[2026-07-11 07:02:16] INFO:   Type: HME-4
[2026-07-11 07:02:16] INFO:   Version: 121
[2026-07-11 07:02:16] INFO:   Broker: hame-2025
[2026-07-11 07:02:16] INFO:   Inverse Forwarding: false
[2026-07-11 07:02:16] INFO:   Use Remote Topic ID: false
[2026-07-11 07:02:16] INFO: ------------------
[2026-07-11 07:02:16] INFO: Device 2:
[2026-07-11 07:02:16] INFO:   Name: HM_B2500_5a05
[2026-07-11 07:02:16] INFO:   Device ID: 360111505357363937034f57
[2026-07-11 07:02:16] INFO:   Remote ID: a0E0w000S0nVW0Q0XXXXXXXX
[2026-07-11 07:02:16] INFO:   MAC: 18cedf985a05
[2026-07-11 07:02:16] INFO:   Type: HMJ-2
[2026-07-11 07:02:16] INFO:   Version: 116
[2026-07-11 07:02:16] INFO:   Broker: hame-2025
[2026-07-11 07:02:16] INFO:   Inverse Forwarding: false
[2026-07-11 07:02:16] INFO:   Use Remote Topic ID: false
[2026-07-11 07:02:16] INFO: ------------------
[2026-07-11 07:02:16] INFO:
[2026-07-11 07:02:16] DEBUG: Setting up forwarder for broker hame-2025
[2026-07-11 07:02:16] DEBUG: [hame-2025] Subscribing to local broker topics:
hame_energy/HME-4/device/02b250c3de3b/ctrl
hame_energy/HMJ-2/device/18cedf985a05/ctrl
[2026-07-11 07:02:16] DEBUG: [hame-2025] Subscribing to remote broker topics:
marstek_energy/HME-4/App/628891ddb42c0f09969d3bb3XXXXXXXX/ctrl
marstek_energy/HMJ-2/App/a0E0w000S0nVW0Q0XXXXXXXX/ctrl
[2026-07-11 07:02:16] INFO: Health server listening on port 8080
[2026-07-11 07:02:16] INFO: [hame-2025] Connected to config broker
[2026-07-11 07:02:16] INFO: [hame-2025] Subscribed to local broker topics
[2026-07-11 07:02:17] INFO: [hame-2025] Connected to remote broker
[2026-07-11 07:02:17] INFO: [hame-2025] Subscribed to remote broker topics
 Live #/#/  You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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 INFO
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
[08:47:03] INFO: Using Home Assistant's internal MQTT broker
[08:47:04] INFO: MQTT Broker URL: mqtt://addons:Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi@core-mosquitto:1883
[08:47:06] INFO: MQTT allowed consecutive timeouts: 8
[08:47:06] INFO: MQTT proxy enabled: false
[08:47:06] INFO: MQTT polling interval: 10 seconds
[08:47:06] INFO: MQTT response timeout: 45 seconds
[08:47:06] INFO: MQTT topic prefix: hm2mqtt
[08:47:06] INFO: MQTT autodiscovery topic prefix: homeassistant
[08:47:06] INFO: Configuring devices...
[08:47:06] INFO: Found 1 devices in configuration
[08:47:07] INFO: Configured device 1: HMJ-2:18cedf985a05
[08:47:07] INFO: Total configured devices: 1
DEVICE_0=HMJ-2:18cedf985a05
[08:47:07] INFO: Starting hm2mqtt...
(node:301) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
◇ injected env (0) from .env // tip: ⌘ custom filepath { path: '/custom/path/.env' }
[06:47:08] INFO: Starting hm2mqtt application...
[06:47:08] INFO: Build commit: 7cce49f8a356ccf011868f8d1d7e1aeef3385ff2
[06:47:08] INFO: Environment: production
[06:47:08] INFO: MQTT Proxy: disabled
[06:47:08] INFO: Registering device: HMJ-2:18cedf985a05 from DEVICE_0=HMJ-2:18cedf985a05
[06:47:08] INFO: Found 1 device(s)
[06:47:08] INFO: - Device: HMJ-2:18cedf985a05
[06:47:08] INFO: Initializing topics for device: HMJ-2:18cedf985a05
[06:47:08] INFO: Connecting to MQTT broker at mqtt://addons:Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi@core-mosquitto:1883 with client ID hm2mqtt-ha-addon
[06:47:08] INFO: MQTT Proxy is disabled (set MQTT_PROXY_ENABLED=true to enable)
[06:47:08] INFO: Connected to MQTT broker
[06:47:53] WARN: No response received from 18cedf985a05 within timeout period
[06:48:43] WARN: No response received from 18cedf985a05 within timeout period
[06:49:33] WARN: No response received from 18cedf985a05 within timeout period
[06:50:23] WARN: No response received from 18cedf985a05 within timeout period
[06:51:14] WARN: No response received from 18cedf985a05 within timeout period
[06:52:04] WARN: No response received from 18cedf985a05 within timeout period
[06:52:54] WARN: No response received from 18cedf985a05 within timeout period
[06:53:44] WARN: No response received from 18cedf985a05 within timeout period
[06:54:34] WARN: No response received from 18cedf985a05 within timeout period
[06:55:24] WARN: No response received from 18cedf985a05 within timeout period
[06:56:14] WARN: No response received from 18cedf985a05 within timeout period
[06:57:04] WARN: No response received from 18cedf985a05 within timeout period
[06:57:54] WARN: No response received from 18cedf985a05 within timeout period
[06:58:44] WARN: No response received from 18cedf985a05 within timeout period
[06:59:34] WARN: No response received from 18cedf985a05 within timeout period
[07:00:24] WARN: No response received from 18cedf985a05 within timeout period
[07:01:14] WARN: No response received from 18cedf985a05 within timeout period
[07:02:04] WARN: No response received from 18cedf985a05 within timeout period
[07:02:54] WARN: No response received from 18cedf985a05 within timeout period
[07:03:44] WARN: No response received from 18cedf985a05 within timeout period
[07:04:34] WARN: No response received from 18cedf985a05 within timeout period
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
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

Add-on: hm2mqtt
Connect Hame energy storage devices to Home Assistant via MQTT

Add-on version: 1.8.1
You are running the latest version of this add-on.
System: Home Assistant OS 18.1  (amd64 / generic-x86-64)
Home Assistant Core: 2026.7.2
Home Assistant Supervisor: 2026.06.2

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
[09:05:03] INFO: Using Home Assistant's internal MQTT broker
[09:05:03] DEBUG: Requested API resource: http://supervisor/services/mqtt
[09:05:03] DEBUG: Request method: GET
[09:05:03] DEBUG: Request data: {}
[09:05:03] DEBUG: API HTTP Response code: 200
[09:05:03] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi","addon":"core_mosquitto"}}
[09:05:03] INFO: MQTT Broker URL: mqtt://addons:Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi@core-mosquitto:1883
[09:05:05] INFO: MQTT allowed consecutive timeouts: 8
[09:05:05] INFO: MQTT proxy enabled: false
[09:05:05] INFO: MQTT polling interval: 10 seconds
[09:05:05] INFO: MQTT response timeout: 45 seconds
[09:05:05] INFO: MQTT topic prefix: hm2mqtt
[09:05:05] INFO: MQTT autodiscovery topic prefix: homeassistant
[09:05:05] INFO: Configuring devices...
[09:05:05] INFO: Found 1 devices in configuration
[09:05:06] INFO: Configured device 1: HMJ-2:18cedf985a05
[09:05:06] INFO: Total configured devices: 1
[09:05:06] DEBUG: Device environment variables:
DEVICE_0=HMJ-2:18cedf985a05
[09:05:06] INFO: Starting hm2mqtt...
(node:313) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use node --trace-warnings ... to show where the warning was created)
◇ injected env (0) from .env // tip: ⌘ enable debugging { debug: true }
[07:05:07] INFO: Starting hm2mqtt application...
[07:05:07] INFO: Build commit: 7cce49f8a356ccf011868f8d1d7e1aeef3385ff2
[07:05:07] INFO: Environment: production
[07:05:07] INFO: MQTT Proxy: disabled
[07:05:07] DEBUG: Full configuration:
[07:05:07] DEBUG: Device environment variables:
[07:05:07] DEBUG: DEVICE_0=HMJ-2:18cedf985a05
[07:05:07] INFO: Registering device: HMJ-2:18cedf985a05 from DEVICE_0=HMJ-2:18cedf985a05
[07:05:07] DEBUG: {
"brokerUrl": "mqtt://addons:Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi@core-mosquitto:1883",
"clientId": "hm2mqtt-ha-addon",
"password": "",
"topicPrefix": "hm2mqtt",
"autodiscoveryTopicPrefix": "homeassistant",
"devices": [
{
"deviceType": "HMJ-2",
"deviceId": "18cedf985a05"
}
],
"responseTimeout": 45000,
"allowedConsecutiveTimeouts": 8
}
[07:05:07] DEBUG: Parsing device configurations...
[07:05:07] DEBUG: Device environment variables:
[07:05:07] DEBUG: DEVICE_0=HMJ-2:18cedf985a05
[07:05:07] INFO: Registering device: HMJ-2:18cedf985a05 from DEVICE_0=HMJ-2:18cedf985a05
[07:05:07] INFO: Found 1 device(s)
[07:05:07] INFO: - Device: HMJ-2:18cedf985a05
[07:05:07] DEBUG: Creating MQTT configuration...
[07:05:07] DEBUG: MQTT Broker: mqtt://addons:Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi@core-mosquitto:1883
[07:05:07] DEBUG: MQTT Client ID: hm2mqtt-ha-addon
[07:05:07] DEBUG: Full MQTT config: {
"brokerUrl": "mqtt://addons:Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi@core-mosquitto:1883",
"clientId": "hm2mqtt-ha-addon",
"password": "",
"topicPrefix": "hm2mqtt",
"autodiscoveryTopicPrefix": "homeassistant",
"devices": [
{
"deviceType": "HMJ-2",
"deviceId": "18cedf985a05"
}
],
"responseTimeout": 45000,
"allowedConsecutiveTimeouts": 8
}
[07:05:07] INFO: Initializing topics for device: HMJ-2:18cedf985a05
[07:05:07] DEBUG: Topics for HMJ-2:18cedf985a05: { deviceTopicOld: 'hame_energy/HMJ-2/device/18cedf985a05/ctrl', deviceTopicNew: 'marstek_energy/HMJ-2/device/0640fe86be81468898da590935d13ded/ctrl', deviceControlTopicOld: 'hame_energy/HMJ-2/App/18cedf985a05/ctrl', deviceControlTopicNew: 'marstek_energy/HMJ-2/App/0640fe86be81468898da590935d13ded/ctrl', publishTopic: 'hm2mqtt/HMJ-2/device/18cedf985a05', controlSubscriptionTopic: 'hm2mqtt/HMJ-2/control/18cedf985a05', availabilityTopic: 'hm2mqtt/HMJ-2/availability/18cedf985a05' }
[07:05:07] INFO: Connecting to MQTT broker at mqtt://addons:Beow7ia6iesaepo3ju5leop2ohdaimah7queengooM5ahqueid0ohXi5fuu5eifi@core-mosquitto:1883 with client ID hm2mqtt-ha-addon
[07:05:07] DEBUG: MQTT username: not provided
[07:05:07] DEBUG: MQTT password: not provided
[07:05:07] INFO: MQTT Proxy is disabled (set MQTT_PROXY_ENABLED=true to enable)
[07:05:07] DEBUG: Application initialized successfully
[07:05:07] INFO: Connected to MQTT broker
[07:05:08] DEBUG: Setting up periodic polling every 10 seconds
[07:05:08] DEBUG: Published to hame_energy/HMJ-2/App/18cedf985a05/ctrl: cd=1
[07:05:08] DEBUG: Published to marstek_energy/HMJ-2/App/0640fe86be81468898da590935d13ded/ctrl: cd=1
[07:05:08] DEBUG: Published to hm2mqtt/availability: online
[07:05:08] DEBUG: Subscribed to topic: hame_energy/HMJ-2/device/18cedf985a05/ctrl
[07:05:08] DEBUG: Subscribed to topic: marstek_energy/HMJ-2/device/0640fe86be81468898da590935d13ded/ctrl
[07:05:08] DEBUG: Subscribed to topic: hm2mqtt/HMJ-2/control/18cedf985a05/discharge-depth,hm2mqtt/HMJ-2/control/18cedf985a05/restart,hm2mqtt/HMJ-2/control/18cedf985a05/refresh,hm2mqtt/HMJ-2/control/18cedf985a05/factory-reset,hm2mqtt/HMJ-2/control/18cedf985a05/use-flash-commands,hm2mqtt/HMJ-2/control/18cedf985a05/charging-mode,hm2mqtt/HMJ-2/control/18cedf985a05/adaptive-mode,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/1/enabled,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/1/start-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/1/end-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/1/output-value,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/2/enabled,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/2/start-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/2/end-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/2/output-value,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/3/enabled,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/3/start-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/3/end-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/3/output-value,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/4/enabled,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/4/start-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/4/end-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/4/output-value,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/5/enabled,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/5/start-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/5/end-time,hm2mqtt/HMJ-2/control/18cedf985a05/time-period/5/output-value,hm2mqtt/HMJ-2/control/18cedf985a05/connected-phase,hm2mqtt/HMJ-2/control/18cedf985a05/time-zone,hm2mqtt/HMJ-2/control/18cedf985a05/sync-time,hm2mqtt/HMJ-2/control/18cedf985a05/surplus-feed-in,hm2mqtt/HMJ-2/control/18cedf985a05/meter-mac,hm2mqtt/HMJ-2/control/18cedf985a05/meter-type
[07:05:08] DEBUG: Published to hm2mqtt/HMJ-2/availability/18cedf985a05: offline
[07:05:18] DEBUG: Published to hame_energy/HMJ-2/App/18cedf985a05/ctrl: cd=1
[07:05:18] DEBUG: Published to marstek_energy/HMJ-2/App/0640fe86be81468898da590935d13ded/ctrl: cd=1
[07:05:28] DEBUG: Published to hame_energy/HMJ-2/App/18cedf985a05/ctrl: cd=1
[07:05:28] DEBUG: Published to marstek_energy/HMJ-2/App/0640fe86be81468898da590935d13ded/ctrl: cd=1
[07:05:38] DEBUG: Published to hame_energy/HMJ-2/App/18cedf985a05/ctrl: cd=1
[07:05:38] DEBUG: Published to marstek_energy/HMJ-2/App/0640fe86be81468898da590935d13ded/ctrl: cd=1

[tomquist]

The device doesn't seem to respond. Try restarting the device either via the App using BLE or by pressing the physical button for 10s.

[thowiegit]

Hint:
If restarting the B2500 via Button does not help and you try to do this while the Sun is still shining, disconnect the PV-Panels from the B2500 before doing the restart via the button, else a power off is not a full power off and thus it will not a full restart ;-)

[joebac25]

Hi, thanks for help, i found it, problem was the wifi, i switch the channel from 11 to 1 and it runs, so easyli, omg!