You can pick a Homey LOGIC card for that and then use the metric/value from the P1 or kwh (not sure what you need here). And yes I can add an extra condition card for it but the LOGIC card is already available.
Hi there. Since yesterday, I’ve noticed that the app crashes several times. I’m running Beta version v3.13.29, which is an experimental version. As a result, none of the devices are available, and naturally, the linked flows aren’t working either. Is anyone else experiencing this? I have already created a diagnostic report and the code is available.
This is your CPU problem.
Advise on your energy_v2 (P1apiv2) move it from polling mode to websocket based.
Polling mode every 1s is a high CPU reason. Websocket mode changes this from pull to push from P1. So it will sent a stream of data instead (less CPU overhead).
2026-02-27T14:18:46.809Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:403cee1a-bf14-4156-804d-b0f95afbec03] Settings for P1 apiv2: 1
stderr:
CPU Warning Limit Reached
⚠ The app has crashed.
CPU Warning Limit Reached
⚠ The app has crashed.
CPU Warning Limit Reached
⚠ The app has crashed.
CPU Warning Limit Reached
In your advanced settings you can find this set this to “NEE” / “NO” it will then activate the websocket method and your Homey will be happy again.
Thanks for the quick reply Jeroen. The mode was set to “Use polling instead of WebSocket” OFF. I’ve just tested it the last half hour or so on the ‘ON’ Polling mode. It is already “OFF” again and ik still crashes. When viewing from the Developer tools on the ‘App Performance’ I don’t see that much CPU Load on the HomeWizard App before crashing.
Your log is not giving me much to drive on.
Can you check this tab please? Thinking it might be in a reconnect storm or something.
Very strange, I was expecting reoccurring messages within a short timespan closing and opening websocket. But if that is not visible if you scroll down in that view then it must be something else.
Sadly I dont see any of that in the diag report you sent me.
Can you try polling mode for energy_v2 but have interval to 5s. Just curious if somehow your P1 is having a rough time answering all queries. It should then show its information in the other tab Device Fetch Debug.
I’ve changed the setting and the App immediately crashes. The setting for the P1 is now:
But do you think that the App is crashing because of an error with the P1v2 API? Or could it also be something else? I could just power off/on the P1 Meter in the port of the meter. To reset it. I’ve haven’t had any trouble with the Homey App before. I do have an Energy socket which is not connected at the moment but this is for the last month or so.
After a few minutes the App did crash again, need to manually push the ‘Restart App’ to be running again.
I had a question/comment/request.
The HWZ battery.
In the “tile,” you can display a value in the top left corner. There’s now an option to display a battery there, which is red/green.
Is it also possible to display a % value instead insteat the battery color?
Or am I asking something your software isn’t designed for, isn’t very easy to implement, or doesn’t provide values in the API?
It might be an area for improvement. I persnol love to see % values , than battery colors.
I really have no smoking gun that points to a error or problem in my app.
A lot of the problems are/should be logged and if I don’t see anything it is very hard for me to track and solve it. Try to increase the polling interval to 10s and restart the app to see if it still crashes.
How is your Homey overall? Are you hitting memory limits? Amount of apps?
Are the other apps trying to access your Homewizard devices that impact their responsiveness?
Eh yes can do. Not sure when but put it on my list
The Homey is working well. Don’t have any other problems with apps. I’ve restarted the Homey just to be sure. I see the HomeWizard App is using about 20% and the DEV portal tells me most apps should not use more than 1% on average. So the App is using much more than recommended. Overal CPU Usage on the Homey is about 30%.
About the memory, don’t see an issue there. Still have almost ~500MB free and the Homey App is using about 100MB. I have about 15 Apps running but also App that I don’t use at the moment.
I’ve change the Polling to 15sec and removed the P1 Meter for a few minutes just to see if the HomeWizard App would run for 15 minutes without having the P1 connected. Unfortunately the App crashes even if the P1 is offline. And I also see the same CPU usage on the HomeWizard App. Which gives me the impression that it’s not the P1 Meter Device which is causing the crashes?!
I don’t have any other home automation connected to the API of the HomeWizard devices, only have the Plug-In batteries which also use the APIv2 as connection for data exchange.
I see that I’m update yesterday to 3.13.29 at 19:14. And just been update to 3.13.30. Am I the only one who has these issues since this release? Maybe I can go back to a previous version to see if that works?
Yes you are the first one sadly. I released new test version with improve battery policy device so that was the reason to bump the version to v3.13.30.
Try to let it run for a few minutes and then hit diagnostic report before it crashes, maybe the log we need is missed due to the crash and we miss the issue.
Thanks. No probnlem. Keep it calm and one bij one. Keep up the good work, and i will buy again a beer (for) later on
Try v3.13.32 think I found a problem in the energy_v2 driver, websocket and battery combination.
I have sent 
to you for 
Thank you 
Thanks @Jeroen_Tebbens I’ve installed the latest version. Will be monitoring tomorrow. Glad you found an issue this fast, hopefully you’ve helpt others aswell.
Unfortunately not quite right yet.
More websocket issues fixed in v3.13.33
