Struggeling with my Jupiter C+ setup

[mbaiti]

Hey guys,

As mentioned here, I‘m struggeling with my Jupiter C+ setup on V135. I‘ve setup a docker-compose stack with b2500-meter as smartmeter, hame-relay in mode 2 and hm2mqtt.

services:
  hm2mqtt:
    container_name: hm2mqtt
    image: ghcr.io/tomquist/hm2mqtt:latest
    restart: unless-stopped
    environment:
      - MQTT_BROKER_URL=mqtt://ip:1883
      - MQTT_USERNAME=hamerelay
      - MQTT_PASSWORD=xyz
      - POLL_CELL_DATA=true
      - POLL_EXTRA_BATTERY_DATA=true
      - POLL_CALIBRATION_DATA=true
      - DEVICE_0=HMA-1:mac
  hame-relay:
    image: ghcr.io/tomquist/hame-relay:latest
    container_name: hame-relay
    restart: unless-stopped
    volumes:
      - /path/to/config:/app/config
    environment:
      - LOG_LEVEL=warn
  smartmeter:
    container_name: smartmeter
    image: ghcr.io/tomquist/b2500-meter:latest
    network_mode: host
    restart: unless-stopped
    volumes:
      - /path/to/config.ini:/app/config.ini

And the hame-relay config:

{
  "broker_url": "mqtt://hamerelay:xyz@ip:1883",
  "inverse_forwarding": true,
  "default_broker_id": "hame-2024",
  "username": "name@domain.com",
  "password": "password",
  "devices": [
    { "device_id": "id", "mac": "mac", "type": "HMA-1", "version": 0 }
  ]
}

After retrieving the id and mac and edit the config, it seems, everything worked fine, the entities showed up within the mqtt Integration in Home Assistant but they become unavailable. The hm2mqtt container log start throwing:

hm2mqtt     | [13:39:23] WARN: No response received from mac within timeout period
hm2mqtt     | [13:40:23] WARN: No response received from mac within timeout period
hm2mqtt     | [13:41:23] WARN: No response received from mac within timeout period
hm2mqtt     | [13:42:23] WARN: No response received from mac within timeout period

Andy ideas? Thank you

[tomquist]

Can you try removing the device from your Hame Relay config so it automatically retrieves aöl the information from your credentials.

[mbaiti]

After removing i got some more errors, but in auto-retrival i‘ve seen some other Settings, so i‘ve updated the config:

{ "device_id": "deviceid", "mac": "mac", "type": "JPLS-8H", "version": 135 }

Now it works like a charm! Thank you @tomquist
If there is an opportunity, I will gladly give you a beer in Stuttgart. Cheers

[mbaiti]

@tomquist another question: some of the sensors are still "unavailable" after several hours. e.g.

Does it take some time or do I have enable additional settings in hm2mqtt?

[tomquist]

These sensors shouldn’t exist for the Jupiter. Likely they have been added when you set the wrong device type. Try deleting the entire device via Settings -> Devices -> Select the device -> Delete the device (If I remember correctly you can do this via the 3 dots, I can't check atm).

Then restart hm2mqtt to recreate the device.

[mbaiti]

Worked as you mentioned! Thanks!

I've read somewhere to use the following sensors for the energy dashboard: Daily PV Charging for solar panels and Daily Battery Charging and Discharging for Home battery storage. These sensors are not available with the Jupiter?

[tomquist]

The Jupiter has "Daily/Monthly Charging Capacity", and "Daily/Monthly Discharge Capacity" you can use instead.

[mbaiti]

Worked for the Battery, but I cannot find a sensor for the solar panels?

[mbaiti]

Just for all they are looking for:
I had to create two new sensors to use it in the energy dashboard:

1. Sum PV1-4 Sensors in a combined helper sensor
2. Add a integral sensor (Riemann-Sum) to create a kWh-sensor

The second sensor can be used in the energy dashboard