Hame Relay / Jupiter C+ stopped updating after reboot

[sventiffe]

I have a strange issue. After a reboot of HA yesterday the updates for my Jupiter C+ stopped working. I am not aware if anything else changed. The Jupiter C+ is on v131.

Hame Relay 1.2.0 configured as:

default_broker_id: hame-2024
log_level: info
devices:
  - device_id: "..."
    mac: ...
    type: JPLS-8H
    version: 0
username: ...
password: ...

The relay seems to work:

[06:57:10] INFO: [hame-2024] Forwarded message from remote to local: hame_energy/JPLS-8H/device/.../ctrl -> hame_energy/JPLS-8H/device/.../ctrl

These messages about forwarding in either direction update once every two minutes.

hm2mqtt 1.5.0 configured as:

responseTimeout: 55
enableCellData: false
enableCalibrationData: false
enableExtraBatteryData: false
allowedConsecutiveTimeouts: 3
topicPrefix: hm2mqtt
mqttProxyEnabled: false
devices:
  - deviceType: JPLS-8H
    deviceId: ...
debug: true

The log says:

[08:59:32] INFO: Starting hm2mqtt...
[06:59:32] INFO: Starting hm2mqtt application...
[06:59:32] INFO: Environment: production
[06:59:32] INFO: MQTT Proxy: disabled
[06:59:32] INFO: Registering device: JPLS-8H:... from DEVICE_0=JPLS-8H:...
[06:59:32] INFO: Found 1 device(s)
[06:59:32] INFO: - Device: JPLS-8H:...
[06:59:32] INFO: Initializing topics for device: JPLS-8H:...
[06:59:32] INFO: Connecting to MQTT broker at mqtt://addons:wohNg8veishah4yohchongiyeer5oodate8ohngethi8Loh3IS7Foht3boo8iedu@core-mosquitto:1883 with client ID hm2mqtt-ha-addon
[06:59:32] INFO: MQTT Proxy is disabled (set MQTT_PROXY_ENABLED=true to enable)
[06:59:33] INFO: Connected to MQTT broker
[07:00:28] WARN: No response received from ... within timeout period

Interestingly, when I scroll back in the protocol, it only consists of the no response received messages even those days where the data got reliably and constantly updated:

[20:21:10] WARN: No response received from ... within timeout period
[20:22:10] WARN: No response received from ... within timeout period
[20:23:10] WARN: No response received from ... within timeout period
[20:24:10] WARN: No response received from ... within timeout period

Any idea how to investigate what stopped working?

[sventiffe]

I've installed the MQTT Explorer Add On to investigate the messages that are being received. It looks like the messages from the device are being received correctly through the Relay:

{
   "deviceType":"JPLS-8H",
   "deviceId":"...",
   "timestamp":"2025-09-18T09:53:34.382Z",
   "values":{
      "ele_d":"74",
      "ele_m":"2995",
      "ele_y":"2996",
      "pv1_p":"132",
      "pv1_s":"1",
      "pv2_p":"135",
      "pv2_s":"1",
      "pv3_p":"126",
      "pv3_s":"1",
      "pv4_p":"127",
      "pv4_s":"1",
      "grd_o":"198",
      "grd_t":"1",
      "gct_s":"0",
      "cel_s":"1",
      "cel_p":"81",
      "cel_c":"16",
      "err_t":"0",
      "wor_m":"2",
      "tim_0":"0|0|23|59|127|200|1",
      "tim_1":"18|30|23|59|127|150|0",
      "tim_2":"0|0|7|0|127|150|0",
      "tim_3":"0|0|0|0|255|0|0",
      "tim_4":"0|0|0|0|255|0|0",
      "cts_m":"0",
      "grd_d":"40",
      "grd_m":"3051",
      "dev_n":"131",
      "dev_i":"107",
      "dev_m":"207",
      "dev_b":"30",
      "dev_t":"111",
      "wif_s":"69",
      "ala_c":"0",
      "ful_d":"0",
      "ssid":"...",
      "stop_s":"10",
      "htt_p":"0",
      "ct_t":"0",
      "phase_t":"0",
      "dchrg":"1",
      "seq_s":"0",
      "total_b":"2",
      "online_b":"3"
   },
   "dailyChargingCapacity":0.74,
   "monthlyChargingCapacity":29.95,
   "yearlyChargingCapacity":29.96,
   "pv1Power":132,
   "pv2Power":135,
   "pv3Power":126,
   "pv4Power":127,
   "dailyDischargeCapacity":0.4,
   "monthlyDischargeCapacity":30.51,
   "combinedPower":198,
   "workingStatus":1,
   "ctStatus":0,
   "batteryWorkingStatus":"charging",
   "batteryEnergy":0.81,
   "batterySoc":16,
   "errorCode":0,
   "workingMode":"manual",
   "autoSwitchWorkingMode":0,
   "httpServerType":0,
   "wifiSignalStrength":-69,
   "ctType":0,
   "phaseType":0,
   "rechargeMode":1,
   "deviceVersion":131,
   "wifiName":"...",
   "surplusFeedInEnabled":false,
   "alarmCode":0,
   "timePeriods":[
      {
         "startTime":"0:00",
         "endTime":"23:59",
         "enabled":true,
         "power":200,
         "weekday":"0123456"
      },
      {
         "startTime":"18:30",
         "endTime":"23:59",
         "enabled":false,
         "power":150,
         "weekday":"0123456"
      },
      {
         "startTime":"0:00",
         "endTime":"7:00",
         "enabled":false,
         "power":150,
         "weekday":"0123456"
      },
      {
         "startTime":"0:00",
         "endTime":"0:00",
         "enabled":false,
         "power":0,
         "weekday":"0123456"
      },
      {
         "startTime":"0:00",
         "endTime":"0:00",
         "enabled":false,
         "power":0,
         "weekday":"0123456"
      }
   ]
}

[sventiffe]

After an unrelated update to v137 and installing the preview release of Hame Relay mentioned in tomquist/hame-relay#74 (comment) it started receiving updates again.

I do not know why it stopped working on v131 without any changes on my end BUT: the Jupiter C+ stopped charging its battery (solar power dropped to 0w independently from daylight/sun) around the same time when the integration stopped working. After some back and forth with the Marstek support and error code 0480 on the device (which shows up when the battery falls below 10% or so) the support asked me to update to v137. This did not fix the issue of 0w solar power but after a ten-seconds-power-press-reset reboot the device started operating normal again.

With v137 the integration also did not work, but given the new release mentioned above (and the discussions on that bug) it required an update of the add on. And here we go again. I wonder if my initial issue would have been resolved by resetting the device. In case I encounter a 0w-issue again, I will try that one.

I guess this discussion can be called "resolved"