I suspected something like that. My flow should the way it is writen with the change if the card “fail” do a retry every 15 min until the x hour limit have passed in my case the trigger is price highest 2 hour amount between 18-22 so it moves around in that timeframe with 15 min pricing. The limitation lock variable prevent it from dual run if already executed once with success. There is situation where i dont want it to run (future prod prediction check and so on). The morning reset flow have a diff design solution.
Was considering setting up ems and put logging triggers to check the behavior if it is something for me
Makes sense, thanks for laying it out — that’s exactly the case the 1.2.18 fix is meant to support: if the target-SoC write fails, the card no longer runs the battery to the old target silently, so your “retry every 15 min until the window passes” actually has a reliable failure to react to. The lock variable + morning reset pattern is a clean way to do the once-per-day guard.
One thing I’d love to understand: how do you fetch the prices today? I’m looking at adding price-aware charging/discharging to the EMS (solar first, then fill in the cheapest hours toward a deadline), and I want to feed it a price forecast the same way people already have their data.
Concretely:
Which app/source do you use for the spot prices (Tibber, Nordpool, “Power by the Hour”, something else)?
Is it 15-min or hourly resolution?
How does it expose the prices in Homey — a capability you read, or do you build the “highest 2 hours in 18–22” selection yourself in a flow (Logic / better logic), or does the price app already give you a “this is a peak/cheap hour” trigger?
And yes — setting up the EMS device with the trigger logging is a good way to watch it without it touching anything; that’s exactly what that view is for.
Im actualy using homey energi solution with RC changes in the experimental version and cards and variables. I used to use tibbers and prior also used Heating controller app but the built in system homey put in is realy good and even better now with the coming stuff. It is doing hour calc on 15 min changes. I swiched out recently the solcast app to homeys new functions for solar prediction wich is realy useful sinsi it is way more accurate sins i have a west/east system and solcast aint very good on that. Been using homeys new system for it for 2 weeks now and it is realy nice.
Just a different kind of email. I wanted to send a huge thank you for the app and the support you provide, Andi. It’s great having a home that you can control yourself, with a little help from others. You can’t get anywhere on your own, so a big thank you.
Good evening,
My battery status shows “not available,” and my Huawei inverter is reporting 0W, whereas the other inverter is working fine. It is 6:30 PM and the sun is still out. What could be causing this?
2026-08-20 21:53:10 [modbus] batch 32070/4 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:10 [modbus] read 32070/1 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] read 32071/1 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] read 32072/2 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] batch 32074/16 (5 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:10 [modbus] read 32074/2 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] read 32076/2 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] read 32080/2 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] batch 32087/3 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:10 [modbus] read 32087/1 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] read 32089/1 failed: no connection to modbus server
2026-08-20 21:53:10 [modbus] batch 32106/10 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:11 [modbus] read 32106/2 failed: no connection to modbus server
2026-08-20 21:53:11 [modbus] read 32114/2 failed: no connection to modbus server
2026-08-20 21:53:11 [modbus] batch 37200/2 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:11 [modbus] read 37200/1 failed: no connection to modbus server
2026-08-20 21:53:11 [modbus] read 37201/1 failed: no connection to modbus server
2026-08-20 21:53:13 [modbus] batch 37046/4 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:13 [modbus] read 37046/2 failed: no connection to modbus server
2026-08-20 21:53:13 [modbus] read 37048/2 failed: no connection to modbus server
2026-08-20 21:53:13 [modbus] batch 37760/54 (8 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:13 [modbus] read 37760/1 failed: no connection to modbus server
2026-08-20 21:53:13 [modbus] read 37762/1 failed: no connection to modbus server
2026-08-20 21:53:13 [modbus] batch 37765/17 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:13 [modbus] read 37765/2 failed: no connection to modbus server
2026-08-20 21:53:13 [modbus] read 37780/2 failed: no connection to modbus server
2026-08-20 21:53:13 [modbus] batch 37782/32 (4 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:14 [modbus] read 37782/2 failed: no connection to modbus server
2026-08-20 21:53:14 [modbus] read 37784/2 failed: no connection to modbus server
2026-08-20 21:53:14 [modbus] batch 37786/28 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:14 [modbus] read 37786/2 failed: no connection to modbus server
2026-08-20 21:53:14 [modbus] read 37799/15 failed: no connection to modbus server
2026-08-20 21:53:14 [modbus] read 37814/15 failed: no connection to modbus server
2026-08-20 21:53:16 [modbus] batch 37100/38 (13 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:16 [modbus] read 37100/1 failed: no connection to modbus server
2026-08-20 21:53:16 [modbus] read 37101/2 failed: no connection to modbus server
2026-08-20 21:53:16 [modbus] batch 37103/4 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:16 [modbus] read 37103/2 failed: no connection to modbus server
2026-08-20 21:53:16 [modbus] read 37105/2 failed: no connection to modbus server
2026-08-20 21:53:16 [modbus] batch 37107/6 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:16 [modbus] read 37107/2 failed: no connection to modbus server
2026-08-20 21:53:16 [modbus] read 37109/2 failed: no connection to modbus server
2026-08-20 21:53:17 [modbus] read 37111/2 failed: no connection to modbus server
2026-08-20 21:53:17 [modbus] batch 37113/25 (6 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:17 [modbus] read 37113/2 failed: no connection to modbus server
2026-08-20 21:53:17 [modbus] read 37119/2 failed: no connection to modbus server
2026-08-20 21:53:17 [modbus] read 37121/2 failed: no connection to modbus server
2026-08-20 21:53:17 [modbus] batch 37132/6 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:17 [modbus] read 37132/2 failed: no connection to modbus server
2026-08-20 21:53:17 [modbus] read 37134/2 failed: no connection to modbus server
2026-08-20 21:53:17 [modbus] read 37136/2 failed: no connection to modbus server
2026-08-20 21:53:19 [modbus] batch 40125/3 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:19 [modbus] read 40125/1 failed: no connection to modbus server
2026-08-20 21:53:19 [modbus] read 40126/2 failed: no connection to modbus server
2026-08-20 21:53:19 [modbus] batch 42054/2 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:19 [modbus] read 42054/1 failed: no connection to modbus server
2026-08-20 21:53:19 [modbus] read 42055/1 failed: no connection to modbus server
2026-08-20 21:53:20 [modbus] batch 47415/4 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:53:20 [modbus] read 47415/1 failed: no connection to modbus server
2026-08-20 21:53:20 [modbus] read 47416/2 failed: no connection to modbus server
2026-08-20 21:53:20 [modbus] read 47418/1 failed: no connection to modbus server
2026-08-20 21:53:21 [log] [ManagerDrivers] [Driver:sun2000_modbus] [Device:fc928dd9-2ea1-438a-a619-9dacbee9f104] Poll OK: PV=0W (+14 polls since last line)
2026-08-20 21:54:09 [modbus] batch 32016/2 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:54:09 [modbus] batch 32064/10 (6 registers) failed: no connection to modbus server — splitting
2026-08-20 21:54:10 [modbus] batch 32070/2 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:54:10 [modbus] batch 32074/8 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:54:13 [modbus] batch 37760/3 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:54:16 [modbus] batch 37100/7 (4 registers) failed: no connection to modbus server — splitting
2026-08-20 21:54:17 [modbus] batch 37113/8 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:09 [modbus] read 30000/15 failed: no connection to modbus server
2026-08-20 21:55:09 [modbus] batch 30050/25 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:09 [modbus] read 30050/15 failed: no connection to modbus server
2026-08-20 21:55:09 [modbus] read 30073/2 failed: no connection to modbus server
2026-08-20 21:55:09 [modbus] batch 32016/4 (4 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:09 [modbus] read 32016/1 failed: no connection to modbus server
2026-08-20 21:55:09 [modbus] read 32017/1 failed: no connection to modbus server
2026-08-20 21:55:09 [modbus] batch 32018/2 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:09 [modbus] read 32018/1 failed: no connection to modbus server
2026-08-20 21:55:09 [modbus] read 32019/1 failed: no connection to modbus server
2026-08-20 21:55:09 [modbus] batch 32064/26 (11 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:10 [modbus] read 32064/2 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] read 32066/1 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] read 32069/1 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] batch 32070/4 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:10 [modbus] read 32070/1 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] read 32071/1 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] read 32072/2 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] batch 32074/16 (5 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:10 [modbus] read 32074/2 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] read 32076/2 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] read 32080/2 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] batch 32087/3 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:10 [modbus] read 32087/1 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] read 32089/1 failed: no connection to modbus server
2026-08-20 21:55:10 [modbus] batch 32106/10 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:11 [modbus] read 32106/2 failed: no connection to modbus server
2026-08-20 21:55:11 [modbus] read 32114/2 failed: no connection to modbus server
2026-08-20 21:55:11 [modbus] batch 37200/2 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:11 [modbus] read 37200/1 failed: no connection to modbus server
2026-08-20 21:55:11 [modbus] read 37201/1 failed: no connection to modbus server
2026-08-20 21:55:13 [modbus] batch 37046/4 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:13 [modbus] read 37046/2 failed: no connection to modbus server
2026-08-20 21:55:13 [modbus] read 37048/2 failed: no connection to modbus server
2026-08-20 21:55:13 [modbus] batch 37760/22 (4 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:13 [modbus] read 37760/1 failed: no connection to modbus server
2026-08-20 21:55:13 [modbus] read 37762/1 failed: no connection to modbus server
2026-08-20 21:55:13 [modbus] batch 37765/17 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:13 [modbus] read 37765/2 failed: no connection to modbus server
2026-08-20 21:55:13 [modbus] read 37780/2 failed: no connection to modbus server
2026-08-20 21:55:13 [modbus] batch 37782/32 (4 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:14 [modbus] read 37782/2 failed: no connection to modbus server
2026-08-20 21:55:14 [modbus] read 37784/2 failed: no connection to modbus server
2026-08-20 21:55:14 [modbus] batch 37786/28 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:14 [modbus] read 37786/2 failed: no connection to modbus server
2026-08-20 21:55:14 [modbus] read 37799/15 failed: no connection to modbus server
2026-08-20 21:55:14 [modbus] read 37814/15 failed: no connection to modbus server
2026-08-20 21:55:16 [modbus] batch 37100/13 (7 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:16 [modbus] read 37100/1 failed: no connection to modbus server
2026-08-20 21:55:16 [modbus] read 37101/2 failed: no connection to modbus server
2026-08-20 21:55:16 [modbus] batch 37103/4 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:16 [modbus] read 37103/2 failed: no connection to modbus server
2026-08-20 21:55:16 [modbus] read 37105/2 failed: no connection to modbus server
2026-08-20 21:55:16 [modbus] batch 37107/6 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:16 [modbus] read 37107/2 failed: no connection to modbus server
2026-08-20 21:55:16 [modbus] read 37109/2 failed: no connection to modbus server
2026-08-20 21:55:17 [modbus] read 37111/2 failed: no connection to modbus server
2026-08-20 21:55:17 [modbus] batch 37113/10 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:17 [modbus] read 37113/2 failed: no connection to modbus server
2026-08-20 21:55:17 [modbus] read 37119/2 failed: no connection to modbus server
2026-08-20 21:55:17 [modbus] read 37121/2 failed: no connection to modbus server
2026-08-20 21:55:17 [modbus] batch 37132/6 (3 registers) failed: no connection to modbus server — splitting
2026-08-20 21:55:17 [modbus] read 37132/2 failed: no connection to modbus server
2026-08-20 21:55:17 [modbus] read 37134/2 failed: no connection to modbus server
2026-08-20 21:55:17 [modbus] read 37136/2 failed: no connection to modbus server
2026-08-20 21:56:09 [modbus] read 30000/15 failed: no connection to modbus server
2026-08-20 21:56:09 [modbus] batch 30050/25 (2 registers) failed: no connection to modbus server — splitting
2026-08-20 21:56:09 [modbus] read 30050/15 failed: no connection to modbus server
2026-08-20 21:56:09 [modbus] read 30073/2 failed: no connection to modbus server
2026-08-20 21:56:09 [modbus] batch 32016/4 (4 registers) failed: no connection to modbus server — splitting
2026-08-20 21:56:09 [modbus] read 32016/1 failed: no connection to modbus server
Since no other users are experiencing this issue, it’s likely something specific to your system.
Could you please reboot the inverter, and the sDongle as well if available?
