No, I wasn’t. No problems until early this morning. I’m aware that you receive unsolicited reports, so I’ll patiently await your request.
Ah ok, sorry wrong assumption here as those reports were about crashes too and without a name. What I noticed on late crashes on my apo is about websocket restarts which I hope have resolved during Christmas break. Just try latest test and if you still have crashes let me know I will help you.
Thank you for your quick help. With the test version, no more crashes for the last 25 minutes. I sent you a small token of appreciation. 
1 Like
You shouldn’t have, but very kind of you 
Dear Jeroen,
Thanks for the nice app, I have a 1 phase kwh meter that I use for P1. This is because fortunately I don’t have a smart meter. However, I don’t get to see the standby consumption. I added d meter as P1 mode. Not via api v2 I think. Am I doing something wrong? What is the difference between the different modes I can choose when adding a device?
I only added this feature for the P1 at this moment, so yes it is not there for you (yet).
As the idea is/was experimental and hence only added it for the P1.
Moreover some like it, some don’t so mixed feelings. 
1 Like
Hello, since two days ago Home Wizard has problems in Homey. Does anyone know what to do?
“Baseload niet bijgewerkt: geen gegevens ontvangen. 6 januari 2026 om 06:00:00”
Is in my timeline and the the energy tab shows this. The readings of the devices look fine but the p1 gets stucks.
thank you!
Restart of the app solved this on my end.
I tried that allready. Rebooting Homey Pro 2023 seems to solve the problem for now.
Sounds like your Homey struggled to get a connection with your P1.
– edit –
After a lot more testing, the energy socket finally gave up totally (for sensoring part). This also declares why the sensor was a bit wobly at the end of lifetime (2,5 years, 6000KW)
– edit –
Since a few days my energy socket is giving me incorrect stat.
I use it to monitor the status of my washing machine
To trigger the flow I use the card:
(if power < 4W for a duration of 60 seconds)
But since a few days, the flow is triggerd multiple times during a washing cycle (this wasnt in the years before).
Did something in the code change that the behaviour now turns to 0 consumption when a reading failed? This is at least the reading I see in Homey.
When I try it manually with the local API, I don’t get any errors, even when spamming it.
Also wifi stats seems to be perfect
Yes maybe, I’ve been recoding everything to expose all the errors and issues in the app settings in debug tab so I wont have to act on every diagnostic report or question raised here so people can investigate themselves. I am not aware that it turn to 0 consumption at this moment.
Not every user has the same problem so hard to trace, even when I have updated version running with about 100 users without questions or problems till it hits stable and you find this.
v3.10.0 (test/beta)
- Bugfix: Homewizard Legacy fetch (tab was empty, no entries while there were errors in the log)
- Remove fetchQueue feature in favor of capture debug information in the app settings page
Hi Jeroen, it needs to check the power for the amound of time you fill in.
see the cards i use within the homewizard app now
yes, thats exactly how i would like it.
but i can’t select this one now right ?
You can already
Scroll down in that view. It must be there.
Hi Jeroen, can’t scroll further down these 6 cards is all there is in my vieuw.
can there be a difference in the homey ( early 2019 ) or the version of the P1 or water meter?
