Please try test version.
Ah, I’m sorry. I can change it to your app. Should meter_power.daily be the usage of the current day?
Thank you @Jeroen_Tebbens, just installed the test version.
I will check tomorrow if it is still running 
Eh yes, but that one is a bit tricky as its a calculated one based on the numbers and time of reset at night time (timezone?). You can check the insights on that metric to see if it resets properly at 0:00 your time.
Also take a note I can’t track house usage as I dont have potential solar usage and / or battery(?).
Yes can be, that means your solar is generating enough to not consume any net power for 5 hours.
But it hasn’t 
The sun is barely shining today I used way more power then to solar has generated.
I restarted my Homey and it looks like it’s updating again;
Then Homey sadly lost connection somehow. Latest v3.12.3 has improvements on keeping this steady. It is pending certification, hope today else early tomorrow Athom approves this.
Sounds good! Hopefully your update will be apporoved soon. Thanks for watching with me. I’m glad restarting Homey solved it for now.
No problem, this app is getting bigger and bigger due to added features and capabilities. Last few weeks have been troublesome for me to tune it all back properly.
Hope it is now all stable again and allowing users to see the wifi / connection problems in the debug view (app settings) tabs.
It’s great that you’re putting so much time into this. I’ll keep an eye on whether that daily usage is working well now.
It looks like after a while it stops updating;
| meter_power.daily | Dag verbruik | number | 22.937 | 38 minutes ago | |||||
|---|---|---|---|---|---|---|---|---|---|
Same problem with PBTH;
| meter_kwh_this_day | kWh deze dag | number | 22.937 | 39 minutes ago | ||
|---|---|---|---|---|---|---|
Is it a Homey problem maybe?
Which device/driver is this? P1? KWh? APIv1 /apiv2?
It’s de P1 meter. Now it’s updating again. I don’t know why it stops updating sometimes.
Drop me a diagnostic please
Sure, it’s ad043404-03cc-4fd3-9bfe-a2053ad502ef
So I guess the timeout problem is key which should improve with the pending update.
Stack trace
Note: this log has been manually submitted by a user.
Log ID: ad043404-03cc-4fd3-9bfe-a2053ad502ef
User Message:
Verbruik update soms niet.
stdout:
2026-01-21T15:28:49.771Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-21T15:28:52.966Z [log] [ManagerDrivers] [Driver:energy] [Device:ccd16e39-633d-43b8-9348-26f87c1033a1] Discovered device URL: http://192.168.0.111:80/api/v1
stderr:
2026-01-21T15:29:16.197Z [err] [ManagerDrivers] [Driver:energy] [Device:ccd16e39-633d-43b8-9348-26f87c1033a1] Poll failed: Error: TIMEOUT
at Timeout._onTimeout (/app/drivers/energy/device.js:28:16)
at listOnTimeout (node:internal/timers:588:17)
at process.processTimers (node:internal/timers:523:7)
2026-01-21T15:29:17.023Z [err] [ManagerDrivers] [Driver:watermeter] [Device:f985a5cf-4d71-4282-a9b8-61ef3ae96428] Polling failed: Error: TIMEOUT
at Timeout._onTimeout (/app/drivers/watermeter/device.js:15:16)
at listOnTimeout (node:internal/timers:588:17)
at process.processTimers (node:internal/timers:523:7)
I guess so. But it’s not only with your app. Data is updated 35 minutes ago. If I check PowerByTheHour it’s the same. That data is also updated 35 minutes ago.
PowerByTheHour updates when the value it is linked to updates. So yeah those are aligned/linked to each other and hence you see both 35min. Lets wait till latest version is deployed and running at your end and take it from there.
We’ll do that! Thanks so far.
1 Like
