Help required for Jupiter C+ | JPLS-8H | V135

[eduardkaufmann]

Dear community,
this is a really great development - I would love to use it, too!
Unfortunately, I was not able to make it work till now. What I did so far is:

1. Installed Mosquitto MQTT broker, Hame-Relay, hm2mqtt in HomeAssistant as add-ons.
2. HomeAssistant is running in a virtualBox on a Win11-Laptop
3. Successfully tested the MQTT broker by sending MQTT topics via Phyton script and showing the values in HA.

Now, when it comes to read the MQTT topics from Jupiter, it doesn't work. I'm able to see different entities in HA, but without any values

This is what I see right now in HA

Hame Relay configuration

inverse_forwarding: true
default_broker_id: hame-2025
log_level: debug
devices:
  - device_id: "3**************************2"
    mac: 0****************b
    type: JPLS-8H
    broker: hame-2025
    inverse_forwarding: true
username: e************@gmail.com
password: ****************
mqtt_uri: mqtt://hame******user:**************@core-mosquitto:1883

hm2mqtt configuration

pollingInterval: 5
responseTimeout: 30
enableCellData: true
enableCalibrationData: true
enableExtraBatteryData: true
allowedConsecutiveTimeouts: 3
topicPrefix: hm2mqtt
mqttProxyEnabled: false
devices:
  - deviceType: JPLS-8H
    deviceId: "3**********************************2"
MQTT_BROKER_URL: mqtt://192.168.***.**:1883
MQTT_USERNAME: hm2*****user
MQTT_PASSWORD: ***************

Hame Relay Protocol

-----------------------------------------------------------
 Add-on: Hame Relay
 Connect B2500 storage to Home Assistant while keeping mobile app functionality
-----------------------------------------------------------
 Add-on version: 1.2.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.2  (amd64 / qemux86-64)
 Home Assistant Core: 2025.9.4
 Home Assistant Supervisor: 2025.09.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
[11:55:54] INFO: Generating config file...
[11:55:55] INFO: Username found in configuration.
[11:55:55] INFO: Password found in configuration.
[11:55:55] INFO: Starting MQTT forwarder...
[09:55:55] DEBUG: Loaded url from file: certs/hame-2024-url
[09:55:55] DEBUG: Loaded ca from file: certs/ca.crt
[09:55:55] DEBUG: Loaded cert from file: certs/hame-2024.crt
[09:55:55] DEBUG: Loaded key from file: certs/hame-2024.key
[09:55:55] DEBUG: Loaded url from file: certs/hame-2025-url
[09:55:55] DEBUG: Loaded ca from file: certs/ca.crt
[09:55:55] DEBUG: Loaded cert from file: certs/hame-2025.crt
[09:55:55] DEBUG: Loaded key from file: certs/hame-2025.key
[09:55:55] DEBUG: Loaded topic_encryption_key from file: certs/hame-2025-topic-encryption-key
[09:55:55] INFO: Credentials found in config, attempting to fetch devices from API...
[09:55:55] INFO: Fetching device token for *************@gmail.com...
[09:55:55] INFO: Fetching device list...
[09:55:55] INFO: Retrieved 1 devices from API
[09:55:55] INFO: Config now contains 1 devices (1 unique)
[09:55:55] INFO: Auto-selected broker hame-2025 for device 3************************2
[09:55:55] DEBUG: Validating 1 devices...
[09:55:55] DEBUG: Found 1 devices in config file
[09:55:55] DEBUG: Validating device: 3************************2
[09:55:55] DEBUG: Using default broker ID: hame-2025
[09:55:55] DEBUG: Using broker ID: hame-2025 for device 3*******************************2
[09:55:55] DEBUG: Using topic encryption key for device 3*****************************2
[09:55:55] DEBUG: Calculated remote ID: b********************************0 for device 3**************************2
[09:55:55] DEBUG: Adding device 3***************************2 to broker hame-2025
[09:55:55] INFO: 
Configured devices: 1 total
[09:55:55] INFO: ------------------
[09:55:55] INFO: Device 1:
[09:55:55] INFO:   Name: Marstec C+
[09:55:55] INFO:   Device ID: 3****************************2
[09:55:55] INFO:   Remote ID: b***********************************0
[09:55:55] INFO:   MAC: 0**************b
[09:55:55] INFO:   Type: JPLS-8H
[09:55:55] INFO:   Version: 135
[09:55:55] INFO:   Broker: hame-2025
[09:55:55] INFO:   Inverse Forwarding: true
[09:55:55] INFO:   Use Remote Topic ID: false
[09:55:55] INFO: ------------------
[09:55:55] INFO: 
[09:55:55] DEBUG: Setting up forwarder for broker hame-2025
[09:55:55] DEBUG: [hame-2025] Subscribing to local broker topics:
hame_energy/JPLS-8H/App/0*************b/ctrl
[09:55:55] DEBUG: [hame-2025] Subscribing to remote broker topics:
marstek_energy/JPLS-8H/device/b*******************************0/ctrl
[09:55:55] INFO: Health server listening on port 8080
[09:55:55] INFO: [hame-2025] Connected to config broker
[09:55:55] INFO: [hame-2025] Subscribed to local broker topics
[09:55:56] INFO: [hame-2025] Connected to remote broker
[09:55:56] INFO: [hame-2025] Subscribed to remote broker topics
[10:04:59] DEBUG: [hame-2025] Matched device: 3***************************2
[10:04:59] DEBUG: [hame-2025] Inverse forwarding: true
[10:04:59] DEBUG: [hame-2025] Skipping device message forwarding to remote for JPLS-8H:3**********************2:0*************b: no recent App message was forwarded
[10:14:59] DEBUG: [hame-2025] Matched device: 3***************************2
[10:14:59] DEBUG: [hame-2025] Inverse forwarding: true
[10:14:59] DEBUG: [hame-2025] Skipping device message forwarding to remote for JPLS-8H:3**********************2:0*************b: no recent App message was forwarded
[10:24:59] DEBUG: [hame-2025] Matched device: 3***************************2
[10:24:59] DEBUG: [hame-2025] Inverse forwarding: true
[10:24:59] DEBUG: [hame-2025] Skipping device message forwarding to remote for JPLS-8H:3**********************2:0*************b: no recent App message was forwarded
...

hm2mqtt protocol

-----------------------------------------------------------
 Add-on: hm2mqtt
 Connect Hame energy storage devices to Home Assistant via MQTT
-----------------------------------------------------------
 Add-on version: 1.5.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.2  (amd64 / qemux86-64)
 Home Assistant Core: 2025.9.4
 Home Assistant Supervisor: 2025.09.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
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
[11:38:23] DEBUG: Debug logging enabled by default
[11:38:23] INFO: Using Home Assistant's internal MQTT broker
[11:38:23] DEBUG: Requested API resource: http://supervisor/services/mqtt
[11:38:23] DEBUG: Request method: GET
[11:38:23] DEBUG: Request data: {}
[11:38:23] DEBUG: API HTTP Response code: 200
[11:38:23] DEBUG: API Response: {"result":"ok","data":{"host":"core-mosquitto","port":1883,"ssl":false,"protocol":"3.1.1","username":"addons","password":"C********************************************************i","addon":"core_mosquitto"}}
[11:38:23] INFO: MQTT Broker URL: mqtt://addons:C*********************************************************i@core-mosquitto:1883
[11:38:24] INFO: MQTT allowed consecutive timeouts: 3
[11:38:24] INFO: MQTT proxy enabled: false
[11:38:24] INFO: MQTT polling interval: 5 seconds
[11:38:24] INFO: MQTT response timeout: 30 seconds
[11:38:24] INFO: MQTT topic prefix: hm2mqtt
[11:38:24] INFO: Configuring devices...
[11:38:24] INFO: Found 1 devices in configuration
[11:38:24] INFO: Configured device 1: JPLS-8H:3****************************2
[11:38:24] INFO: Total configured devices: 1
[11:38:24] DEBUG: Device environment variables:
DEVICE_0=JPLS-8H:3***************************2
[11:38:24] INFO: Starting hm2mqtt...
[09:38:25] INFO: Starting hm2mqtt application...
[09:38:25] INFO: Environment: production
[09:38:25] INFO: MQTT Proxy: disabled
[09:38:25] INFO: Registering device: JPLS-8H:3************************2 from DEVICE_0=JPLS-8H:3****************************2
[09:38:25] INFO: Found 1 device(s)
[09:38:25] INFO: - Device: JPLS-8H:3***************************2
[09:38:25] INFO: Initializing topics for device: JPLS-8H:3*************************2
[09:38:25] INFO: Connecting to MQTT broker at mqtt://addons:C*****************************************************i@core-mosquitto:1883 with client ID hm2mqtt-ha-addon
[09:38:25] INFO: MQTT Proxy is disabled (set MQTT_PROXY_ENABLED=true to enable)
[09:38:25] INFO: Connected to MQTT broker
[09:38:55] WARN: No response received from 3*****************************2 within timeout period
[09:39:26] WARN: No response received from 3*****************************2 within timeout period
[09:39:56] WARN: No response received from 3*****************************2 within timeout period
[09:40:26] WARN: No response received from 3*****************************2 within timeout period
...

I went through several topics and discussion on github and tried out different configurations, but still didn't manage to make it work.
I would really appreciate any advice. Many thanks in advance!

[sventiffe]

I see that you are running 135 on the device. I know that for 137, you will need to install the developer preview release of Hame Relay to receive MQQT updates from the Cloud (and to write back). Not sure if the official release works with 135 (it worked for me with 131 though). See my comment here #178 (reply in thread)

[eduardkaufmann]

Thanks @sventiffe.
Today I installed the new version of Hame-Relay what you proposed.
I think, I got a tiny improvement: When I refresh the Jupiter status in the mobile app, some new lines appear in the hame-releay log:

[18:05:19] DEBUG: [hame-2025] Matched device: 3*************************2
[18:05:19] DEBUG: [hame-2025] Inverse forwarding: false
[18:05:19] DEBUG: [hame-2025] Target prefix: hame_energy/
[18:05:19] DEBUG: [hame-2025] Target identifier: 0*************b
[18:05:19] DEBUG: [hame-2025] New topic: hame_energy/JPLS-8H/App/0********************b/ctrl
[18:05:19] DEBUG: [hame-2025] From: remote
[18:05:19] DEBUG: [hame-2025] To: local
[18:05:19] INFO: [hame-2025] Forwarded message from remote to local: marstek_energy/JPLS-8H/App/b************************************0/ctrl -> hame_energy/JPLS-8H/App/0**************b/ctrl 

unfortunately, hm2mgtt produces continuously the same log:

[18:14:37] WARN: No response received from 3**********************2 within timeout period

I also tried to browse mqtt topics with mqtt-explorer. There, I also see the value ctrl = cd = 1... Sometimes it changes from 1 to 14...
And, the hm2mgtt shows an "offline" value:

Somehow I have the feeling that hm2mqtt does not run properly in my setup...

[tomquist]

Looks like hame relay is working correctly but you configured hm2mqtt wrong. Make sure to set the device id to the Mac of the device (the one shown in the hame relay logs) and also ensure you set the correct device type (JPLS-8H).

[sventiffe]

Fwiw, my logs are full of No response received from messages but the values update in both directions