Before you submit
Battery / device models
Marstek Jupiter Plus
Version
1.4.3
Deployment
Home Assistant add-on
B2500 MQTT configuration
Not applicable — I don't have a B2500
Are you using hm2mqtt?
Yes
What's happening?
Marstek Jupiter C Plus (JPLS-8H), firmware V231.
Hame Relay forwards App messages local→remote reliably every 60s with no errors.
No message is ever received in the opposite direction: there is not a single
"Forwarded message from remote to local" line in the log, over ~40 minutes of
continuous operation. hm2mqtt therefore reports "No response received from
24215edb1697 within timeout period" on every polling cycle.
Expected: device messages on
marstek_energy/JPLS-8H/device//ctrl to be forwarded to the local
broker so hm2mqtt can create entities. No entities are created.
The device is confirmed online and talking to the Marstek cloud:
- established TLS connection from the battery to the cloud on port 8883
(verified on the router's connection table, hundreds of packets)
- WiFi signal -70 dBm, stable, no disconnects
- the Marstek mobile app shows live data throughout
Local MQTT (Mosquitto) is confirmed working; hm2mqtt publishes to both
hame_energy/ and marstek_energy/ prefixes and Hame Relay picks up the
hame_energy one correctly.
Suspicion: the salt-based CommonHelper.cq remote ID calculation may not match
firmware V231, so the subscription topic does not correspond to what the
device actually publishes on.
Steps to reproduce: configure Hame Relay + hm2mqtt for a JPLS-8H on FW V231
with Hame account credentials; observe outbound forwarding but no inbound.
Configuration
log_level: debug
inverse_forwarding: false
# username / password / mqtt_uri removed
Logs
Device 360111505659323435094847 (JPLS-8H): inverse_forwarding = true (automatic)
Auto-selected broker hame-2025 for device 360111505659323435094847
Device 360111505659323435094847 supports CommonHelper.cq method, using salt-based calculation
Calculated remote ID using CommonHelper.cq: 00C0i05V3Va0vVQ0s0fVw0TV for device 360111505659323435094847
Device 1:
Name: MST_JPLS_1697
Device ID: 360111505659323435094847
Remote ID: 00C0i05V3Va0vVQ0s0fVw0TV
MAC: 24215edb1697
Type: JPLS-8H
Version: 231
Broker: hame-2025
Inverse Forwarding: true
Use Remote Topic ID: false
[hame-2025] Subscribing to local broker topics:
hame_energy/JPLS-8H/App/24215edb1697/ctrl
[hame-2025] Subscribing to remote broker topics:
marstek_energy/JPLS-8H/device/00C0i05V3Va0vVQ0s0fVw0TV/ctrl
[hame-2025] Connected to config broker
[hame-2025] Subscribed to local broker topics
[hame-2025] Connected to remote broker
[hame-2025] Subscribed to remote broker topics
[hame-2025] Matched device: 360111505659323435094847
[hame-2025] Inverse forwarding: true
[hame-2025] Target prefix: marstek_energy/
[hame-2025] Target identifier: 00C0i05V3Va0vVQ0s0fVw0TV
[hame-2025] New topic: marstek_energy/JPLS-8H/App/00C0i05V3Va0vVQ0s0fVw0TV/ctrl
[hame-2025] From: local
[hame-2025] To: remote
[hame-2025] Forwarded message from local to remote: hame_energy/JPLS-8H/App/24215edb1697/ctrl -> marstek_energy/JPLS-8H/App/00C0i05V3Va0vVQ0s0fVw0TV/ctrl
(repeats every 60s -- never any remote -> local)
--- hm2mqtt 1.8.1 ---
Published to hame_energy/JPLS-8H/App/24215edb1697/ctrl: cd=1
Published to marstek_energy/JPLS-8H/App/24215edb1697/ctrl: cd=1
Subscribed to topic: hame_energy/JPLS-8H/device/24215edb1697/ctrl
Subscribed to topic: marstek_energy/JPLS-8H/device/24215edb1697/ctrl
WARN: No response received from 24215edb1697 within timeout period
(every cycle, continuously)
Before you submit
Battery / device models
Marstek Jupiter Plus
Version
1.4.3
Deployment
Home Assistant add-on
B2500 MQTT configuration
Not applicable — I don't have a B2500
Are you using hm2mqtt?
Yes
What's happening?
Marstek Jupiter C Plus (JPLS-8H), firmware V231.
Hame Relay forwards App messages local→remote reliably every 60s with no errors.
No message is ever received in the opposite direction: there is not a single
"Forwarded message from remote to local" line in the log, over ~40 minutes of
continuous operation. hm2mqtt therefore reports "No response received from
24215edb1697 within timeout period" on every polling cycle.
Expected: device messages on
marstek_energy/JPLS-8H/device//ctrl to be forwarded to the local
broker so hm2mqtt can create entities. No entities are created.
The device is confirmed online and talking to the Marstek cloud:
(verified on the router's connection table, hundreds of packets)
Local MQTT (Mosquitto) is confirmed working; hm2mqtt publishes to both
hame_energy/ and marstek_energy/ prefixes and Hame Relay picks up the
hame_energy one correctly.
Suspicion: the salt-based CommonHelper.cq remote ID calculation may not match
firmware V231, so the subscription topic does not correspond to what the
device actually publishes on.
Steps to reproduce: configure Hame Relay + hm2mqtt for a JPLS-8H on FW V231
with Hame account credentials; observe outbound forwarding but no inbound.
Configuration
Logs