Hallo GoBieN-Be, of anderen,
Ik denk dat onderstaande aangeeft dat ik geprobeerd heb zelfredzaam te zijn, maar ik mis nog wat final-handson-tricks.
Hoe nu verder in Home Assistant om gegevens van de batterij te zien.
Om "off-topic" reacties te voorkomen s.v.p. een DM aan mij sturen; Dank je wel.
Ik heb Oracle Virtual Box geinstalleerd, vervolgens Home Assistant geinstalleerd en mijn HW P1 dongle als Device in Home Assistant gehangen.
Vervolgens MQTT in Home Assistant geinstalleerd en de tool van TomQuist (Hame Relay) om als bridge te fungeren geinstalleerd.
In de betreffende config userid/wachtwoord en deviceid/macadres ingevuld en in de log van Hame Relay
staat:
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.1 (amd64 / qemux86-64)
Home Assistant Core: 2025.8.2
Home Assistant Supervisor: 2025.08.1
-----------------------------------------------------------
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 INFO
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
[12:12:28] INFO: Generating config file...
[12:12:28] INFO: Username found in configuration.
[12:12:28] INFO: Password found in configuration.
[12:12:28] INFO: Starting MQTT forwarder...
[10:12:29] INFO: Credentials found in config, attempting to fetch devices from API...
[10:12:29] INFO: Fetching device token for xxxxxxx..
[10:12:29] INFO: Fetching device list...
[10:12:29] INFO: Retrieved 1 devices from API
[10:12:29] INFO: Config now contains 1 devices (1 unique)
[10:12:29] INFO: Auto-selected broker hame-2024 for device xxxxxxx
[10:12:29] INFO:
Configured devices: 1 total
[10:12:29] INFO: ------------------
[10:12:29] INFO: Device 1:
[10:12:29] INFO: Name: MST_ACCP_3048
[10:12:29] INFO: Device ID: xxxxx
[10:12:29] INFO: Remote ID: xxxxx
[10:12:29] INFO: MAC: xxxxx
[10:12:29] INFO: Type: HMA-1
[10:12:29] INFO: Version: 0
[10:12:29] INFO: Broker: hame-2024
[10:12:29] INFO: Inverse Forwarding: true
[10:12:29] INFO: Use Remote Topic ID: false
[10:12:29] INFO: ------------------
[10:12:29] INFO:
[10:12:30] INFO: Health server listening on port 8080
[10:12:30] INFO: [hame-2024] Connected to config broker
[10:12:30] INFO: [hame-2024] Subscribed to local broker topics
[10:12:30] INFO: [hame-2024] Connected to remote broker
[10:12:30] INFO: [hame-2024] Subscribed to remote broker topics
[10:22:48] ERROR: [hame-2024] Remote broker error
err: {
"type": "Error",
"message": "Keepalive timeout",
"stack":
Error: Keepalive timeout
at MqttClient.onKeepaliveTimeout (/app/node_modules/mqtt/build/lib/client.js:1049:28)
at Timeout._onTimeout (/app/node_modules/mqtt/build/lib/KeepaliveManager.js:67:29)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7)
}
[10:22:48] WARN: [hame-2024] Remote broker went offline
[10:22:55] INFO: [hame-2024] Connected to remote broker
NL; MT Venus E V2 (V153 BMS:V215); HW P1 (5.1903); App: V1.6.49; Comm.Mod:202409090159; 1 Fase 40A hoofdzek.; Iskra ME382-D1A52-P1 bj 2012; PV 7650 Wpiek; Inventum Ecolution ventilatiewarmtepomp; EV (Seat Mii 32kWh);