[APP][Pro][NL] Homewizard 🧙‍♂️

Zit er nog niet in, kan ik wel maken. Voor nu is het alleen flow trigger/condition cards maar niet iets wat visueel in de P1 zichtbaar is tbv aansturing van de batterij groep.

Top, dan hou ik nog even mijn logica kaartje met “Zet BatterijModus naar” Want dat werkt ook. Gebruik de waarde van de variabele dan alleen voor weergave.

en deze

Die opties gebruik ik inderdaad in mijn flow. (deel uitgesteld laden)

Het gaat mij om de weergave in welke modus de batterij staat. Dat doe ik nu dus via een variabele.

Mijn app heeft helemaal geen dashboard optie. Althans nooit naar gekeken tenzij er iets standaard vanuit Homey komt.

Dat hoeft ook niet. Je kan gewoon logica of sensor waardes gebruiken. In mijn geval gebruik ik dus een variabele “BatterijModus”

Als er net als de sensor “Batterij status” dus één sensor zou zijn voor modus. (NOM, stand-by, enz) zijn wij er al. :grinning_face:

Testje gedaan. Maar dat lijkt helaas vast te lopen.

e56375a9-a2a4-4b60-9814-796369110753

Geen idee wat je zoekt of probeert of test. Maar dit is je log. Je kan ook zelf nu in de app settings zelf kijken onder websocket tabje.

Stack Trace
Note: this log has been manually submitted by a user.
    Log ID: e56375a9-a2a4-4b60-9814-796369110753

    User Message:
    Test Batterij laad mode. Lijkt vast te lopen. 

    stdout:
    2026-01-15T19:11:28.202Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-15T19:11:28.737Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:496458a9-605e-4ae3-8090-8ef55e640c86] Plugin Battery settings: {
  use_polling: false,
  polling_interval: 10,
  url: 'https://192.168.0.105'
}
2026-01-15T19:11:28.739Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:496458a9-605e-4ae3-8090-8ef55e640c86] Restored URL from settings: https://192.168.0.105
2026-01-15T19:11:28.740Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:496458a9-605e-4ae3-8090-8ef55e640c86] 🔌 WebSocket enabled at init
2026-01-15T19:11:28.801Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:6b27b76b-8f39-490f-b374-383e7da2b3b3] Plugin Battery settings: {
  use_polling: false,
  polling_interval: 10,
  url: 'https://192.168.0.104'
}
2026-01-15T19:11:28.801Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:6b27b76b-8f39-490f-b374-383e7da2b3b3] Restored URL from settings: https://192.168.0.104
2026-01-15T19:11:28.802Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:6b27b76b-8f39-490f-b374-383e7da2b3b3] 🔌 WebSocket enabled at init
2026-01-15T19:11:28.823Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:496458a9-605e-4ae3-8090-8ef55e640c86] 🌐 Discovery: initial IP 192.168.0.105
2026-01-15T19:11:28.825Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:6b27b76b-8f39-490f-b374-383e7da2b3b3] 🌐 Discovery: initial IP 192.168.0.104
2026-01-15T19:11:28.830Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] Settings for P1 apiv2:  10
2026-01-15T19:11:28.843Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] 🌐 Discovery: initial IP set to 192.168.0.101
2026-01-15T19:11:28.850Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] 🌐 Discovery: IP unchanged (192.168.0.101) — ignoring
2026-01-15T19:11:29.699Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:496458a9-605e-4ae3-8090-8ef55e640c86] 🔐 Sending WebSocket authorization
2026-01-15T19:11:29.721Z [log] [ManagerDrivers] [Driver:plugin_battery] [Device:6b27b76b-8f39-490f-b374-383e7da2b3b3] 🔐 Sending WebSocket authorization
2026-01-15T19:11:30.028Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] 🔐 Sending WebSocket authorization
2026-01-15T19:13:52.395Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ConditionCard: Check Battery Mode
2026-01-15T19:13:52.395Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ConditionCard: Check Battery Mode
2026-01-15T19:13:52.397Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ActionCard: Set Battery to Zero Charge Only Mode
2026-01-15T19:13:52.397Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] 🔋 WS → setBatteryMode("zero_charge_only")
2026-01-15T19:13:52.398Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d]    Payload: {"type":"batteries","data":{"mode":"zero","permissions":["charge_allowed"]}}
2026-01-15T19:13:52.398Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ✅ Battery mode command sent
2026-01-15T19:13:52.402Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] Set mode to zero_charge_only via WebSocket
2026-01-15T19:14:35.713Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ConditionCard: Check Battery Mode
2026-01-15T19:14:35.713Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ConditionCard: Check Battery Mode
2026-01-15T19:16:13.041Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ConditionCard: Check Battery Mode
2026-01-15T19:16:13.325Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ConditionCard: Check Battery Mode
2026-01-15T19:16:56.626Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ActionCard: Set Battery to Zero Mode
2026-01-15T19:16:56.626Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] 🔋 WS → setBatteryMode("zero")
2026-01-15T19:16:56.626Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d]    Payload: {"type":"batteries","data":{"mode":"zero","permissions":["charge_allowed","discharge_allowed"]}}
2026-01-15T19:16:56.627Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ✅ Battery mode command sent
2026-01-15T19:16:56.630Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] Set mode to zero via WebSocket
2026-01-15T19:18:04.122Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ActionCard: Set Battery to Zero Mode
2026-01-15T19:18:04.122Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] 🔋 WS → setBatteryMode("zero")
2026-01-15T19:18:04.123Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d]    Payload: {"type":"batteries","data":{"mode":"zero","permissions":["charge_allowed","discharge_allowed"]}}
2026-01-15T19:18:04.123Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ✅ Battery mode command sent
2026-01-15T19:18:04.126Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] Set mode to zero via WebSocket
2026-01-15T19:21:02.431Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ActionCard: Set Battery to Zero Mode
2026-01-15T19:21:02.432Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] 🔋 WS → setBatteryMode("zero")
2026-01-15T19:21:02.432Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d]    Payload: {"type":"batteries","data":{"mode":"zero","permissions":["charge_allowed","discharge_allowed"]}}
2026-01-15T19:21:02.432Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] ✅ Battery mode command sent
2026-01-15T19:21:02.435Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:e41ee07f-2a0a-40c6-9d94-3faaaaf5459d] Set mode to zero via WebSocket

    stderr:
    n/a

Beste Jeroen,

Ook met de laatste versie 3.11.2 blijft de Battery Group Average SoC op 0% staan, terwijl die nu 5% is.

Probeer test versie v3.11.4

  • Bugfix: P1 (apiv2) polling mode - Charge mode fixes
  • Extra log info on Group Battery State of Charge

Helaas geen verbetering, blijft op 0% SoC staan.

Ok stuur mij diagnose rapport want ik heb logging toegevoegd dan kan ik zien wat de code doet.
Wat lastig is hier, ik heb zelf maar 1 batterij. In jou geval 2 stuks en dan is het een berekening op basis van 2 registraties intern in een groep die ik gemaakt heb.

Diagnose rapport gestuurd. Code 3fbd8dc2-1338-4995-9307-516ad5ec0e29

Ok dit moet opgelost zijn in nieuwe test versie v3.11.5 (nu in store)

Helaas, Jeroen, maar niet opgelost. Blijft op 0% staan.

Stuur nog eens diagnostic

Diagnose rapport gestuurd, code: 998cb3e3-5f3e-4fd1-bdb9-4fc6334b97b2

Je batterijen zijn echt niet leeg?
soc_pct beide 0 anders gaat er daar iets fout.

Nu test versie v3.11.6 maar blijf het vreemd vinden

2026-01-16T14:09:01.250Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:63e5153f-d6a2-4475-b950-25dcaaea21c8] :magnifying_glass_tilted_left: pluginBatteryGroup = {
“5c2faf33f7e0”: {
“id”: “5c2faf33f7e0”,
“capacity_kwh”: 2.8,
“cycles”: 145,
“power_w”: 0,
“soc_pct”: 0,
“updated_at”: 1767197719566
},
“5c2faf33f688”: {
“id”: “5c2faf33f688”,
“capacity_kwh”: 2.8,
“cycles”: 172,
“power_w”: 0,
“soc_pct”: 0,
“updated_at”: 1767197719218
}
}

Nee de batterijen zijn/waren niet leeg. Niet heel vol, maar toch 10% SoC vanmiddag. Nu inmiddels wel bijna. 1 heeft 1% en de andere 4% SoC. Het HW displey geeft nu 2% aan. Ze zijn al een uurtje aan het ontladen en zullen nu snel leeg zijn. Dus morgen maar weer verder kijken, lijkt mij.