Cannot connect to B2500; hm2mqtt still necessary?

[halorx]

Question

I can no longer reach the power storage devices. BLE tool is only showing one of the devices remaining. before at least both have shown up but i only was able to connect one device. Ironically it was the other device and not the one that is remaining, if i remember correctly(but im not 100% sure) and i cannot connect to it, it says:

22:33:39 - Requesting Bluetooth device...
22:33:39 - Using device name prefix: "HM_"
22:33:53 - Selected device: HM_B2500_6631 (gKgzrxCnOQE6YeFqlwhfWQ==)
22:33:53 - Connecting to GATT server...
22:33:58 - Getting primary service (0000ff00-0000-1000-8000-00805f9b34fb)...
22:34:03 - Error: GATT Server is disconnected. Cannot retrieve services. (Re)connect first with device.gatt.connect.
22:34:03 - Connection error: GATT Server is disconnected. Cannot retrieve services. (Re)connect first with device.gatt.connect.
22:34:03 - Scanning error: GATT Server is disconnected. Cannot retrieve services. (Re)connect first with device.gatt.connect.

Im able to ping the devices over network, they also show up as wlan0 and wlan0--8 devices in the devices list of the router. One device is showing up/down 48,0 Mbit/s 48,0 Mbit/s and the other one 0 bit/s 0 bit/s its really weird.

Also it was very weird that for some amount of time one of the storage devices showed firmware 229.5, the other one 229 and now both of them are showing 229.

Is the hm2mqtt bridge still necessary? Should it be possible to connect the storage devices to the mosquitto broker directly for at least to try some of the publish commands from the marstek mqtt documentation from the marstek app?

Does someone know what this behaviour or error messages mean? Is it possible that the storage devices are deeply discharged? The App is showing 23% for the _6631 device wen im clicking into it in the app but in the overview it shows 0%. This is the device that is reachable but not able to connect to, the other device shows up permanently offline in the overview(HM_B2500_6b5a) and when i click into it it shows 20% charged. But it doesnt seem like so to me. Seems that it is an warranty case to me.

Device Model (optional)

B2500 HMA

Firmware Version (optional)

229

hm2mqtt Configuration

GNU nano 8.4                                                                                    docker-compose.yml
services:
  homeassistant:
    image: ghcr.io/home-assistant/home-assistant:stable
    container_name: homeassistant
    restart: unless-stopped
    network_mode: host
    cap_add:
      - NET_ADMIN
      - NET_RAW
    volumes:
      - ./homeassistant:/config
      - /etc/localtime:/etc/localtime:ro
    environment:
      - TZ=Europe/Berlin

  mosquitto:
    image: eclipse-mosquitto:latest
    container_name: mosquitto
    restart: unless-stopped
    network_mode: host
    volumes:
      - ./mosquitto/config:/mosquitto/config
      - ./mosquitto/data:/mosquitto/data
      - ./mosquitto/log:/mosquitto/log

  hm2mqtt:
    container_name: hm2mqtt
    image: ghcr.io/tomquist/hm2mqtt:latest
    restart: unless-stopped
    network_mode: host
    ports:
      - "1890:1890"  # Expose proxy port for B2500 devices
    environment:
      - MQTT_BROKER_URL=mqtt://127.0.0.1:1883
      - MQTT_USERNAME=foo
      - MQTT_PASSWORD=bazzz
      - MQTT_PROXY_ENABLED=true
      - MQTT_PROXY_PORT=1890
      - POLL_CELL_DATA=true
      - POLL_EXTRA_BATTERY_DATA=true
      - POLL_CALIBRATION_DATA=true
      - DEVICE_0=HMA-1:7ce712af6b5a
      - DEVICE_1=HMA-1:7ce712af6631

hm2mqtt Logs

pi@raspberry:~/smarthome-docker $ docker compose logs -f
homeassistant  | s6-rc: info: service s6rc-oneshot-runner: starting
homeassistant  | s6-rc: info: service s6rc-oneshot-runner successfully started
homeassistant  | s6-rc: info: service fix-attrs: starting
homeassistant  | s6-rc: info: service fix-attrs successfully started
homeassistant  | s6-rc: info: service legacy-cont-init: starting
homeassistant  | s6-rc: info: service legacy-cont-init successfully started
homeassistant  | s6-rc: info: service legacy-services: starting
homeassistant  | services-up: info: copying legacy longrun home-assistant (no readiness notification)
homeassistant  | s6-rc: info: service legacy-services successfully started
hm2mqtt        | [20:19:39] INFO: Starting hm2mqtt application...
hm2mqtt        | [20:19:39] INFO: Environment: production
hm2mqtt        | [20:19:39] INFO: MQTT Proxy: enabled on port 1890
hm2mqtt        | [20:19:39] INFO: Registering device: HMA-1:7ce712af6b5a from DEVICE_0=HMA-1:7ce712af6b5a
hm2mqtt        | [20:19:39] INFO: Registering device: HMA-1:7ce712af6631 from DEVICE_1=HMA-1:7ce712af6631
hm2mqtt        | [20:19:39] INFO: Found 2 device(s)
hm2mqtt        | [20:19:39] INFO: - Device: HMA-1:7ce712af6b5a
hm2mqtt        | [20:19:39] INFO: - Device: HMA-1:7ce712af6631
hm2mqtt        | [20:19:39] INFO: Initializing topics for device: HMA-1:7ce712af6b5a
hm2mqtt        | [20:19:39] INFO: Initializing topics for device: HMA-1:7ce712af6631
hm2mqtt        | [20:19:39] INFO: Connecting to MQTT broker at mqtt://127.0.0.1:1883 with client ID hm2mqtt-11c01a
hm2mqtt        | [20:19:40] INFO: MQTT Proxy connecting to main broker at mqtt://127.0.0.1:1883 with client ID hm2mqtt-11c01a-proxy
hm2mqtt        | [20:19:40] INFO: MQTT Proxy server started on port 1890
hm2mqtt        | [20:19:40] INFO: MQTT Proxy started successfully on port 1890
hm2mqtt        | [20:19:40] INFO: Connected to MQTT broker
hm2mqtt        | [20:19:41] INFO: MQTT Proxy connected to main broker
hm2mqtt        | [20:19:56] WARN: No response received from 7ce712af6b5a within timeout period
hm2mqtt        | [20:19:56] WARN: No response received from 7ce712af6631 within timeout period
hm2mqtt        | [20:20:56] WARN: No response received from 7ce712af6b5a within timeout period
hm2mqtt        | [20:20:56] WARN: No response received from 7ce712af6631 within timeout period
hm2mqtt        | [20:21:56] WARN: No response received from 7ce712af6b5a within timeout period
hm2mqtt        | [20:21:56] WARN: No response received from 7ce712af6631 within timeout period
hm2mqtt        | [20:23:56] WARN: No response received from 7ce712af6b5a within timeout period
hm2mqtt        | [20:23:56] WARN: No response received from 7ce712af6631 within timeout period
hm2mqtt        | [20:25:56] WARN: No response received from 7ce712af6b5a within timeout period
hm2mqtt        | [20:25:56] WARN: No response received from 7ce712af6631 within timeout period
hm2mqtt        | [20:26:56] WARN: No response received from 7ce712af6b5a within timeout period

Hame Relay Configuration

Hame Relay Logs