Hi Jeroen. I have last half hour/hour multiple crashes. Can you have a look?
Yesterday I have got a new firmware for my Ziggo router Yesterday, I now have now no connectivity issues (with HW app and meters etc). Don’t know if this is important.
Sorry am very loaded with my normal job lately (understaffed team). So giving this a quick glance where I see your watermeter lost it (connectivity). I added some extra guards for this which hopefully ease this situation. The P1 beta firmware is not the cause, at least, I don’t see issues here in my lab with 2x P1’s both having the latest beta firmware so that can be ruled out.
I would suggest you focus on your wifi a little more to get these devices stable, yes I know not that easy we all face these challenges and there is no silver bullet. I hope the guards will prevent the app crashing as I spent a lot of time to lower the cpu and memory footprint which made the app drop 20MB already since a month.
–
Multple messages like these in your report:
2026-07-14T10:23:16.104Z [err] [ManagerDrivers] [Driver:watermeter] [Device:e32dad4b-6ca0-4b39-9178-41f285c080b4] Polling failed: FetchError: request to http://192.168.1.xx/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501:11)
at ClientRequest.emit (node:events:519:28)
at emitErrorEvent (node:_http_client:108:11)
at Socket.socketErrorListener (node:_http_client:575:5)
at Socket.emit (node:events:519:28)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at process.processTicksAndRejections (node:internal/process/task_queues:89:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
⚠ The app has crashed.
CPU Warning Limit Reached
Hi Jeroen, no problem. The new version solved the connection to the watermeter when the app is running. Unfortunatelly the app crashes (perhaps it is live somewhat longer).
I will take the app offline for now, I hope to have a look to the wifi tomorrow afternoon. Sorry for that.
Even your P1 is struggling where this app tries to read it.
Today at 12:22PM, app tries to check battery mode state as it could not get the latest state via de P1. Either wifi or other sources are reading at the same time, can’t tell.
2026-07-14T10:22:21.498Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:a9792a8b-4a44-4ad6-b31f-b31bf9af2abd] 🔍 Battery mode staleness check failed: request to https://192.168.1.x/api/batteries failed, reason: socket hang up
I had a working connection between my Homey Pro 2023 and the Homewizard 3-phase meter. When I set up my new network, this connection was lost. Now, when I try to restore the connection, I get a message saying I need to enable the API. It’s already enabled, but the 3-phase meter isn’t being detected. Just like in the old setup, the Homey is on the regular network and the 3-phase meter is on the IoT network.
That’s not possible. You should either move the Homey to the IoT network or move the Homewizard to the main network
It has worked in the past. I’ve now connected both of them to the same network, but the result is still the same. I restarted the Homewizard app on the Homey, but again, no result. The meter isn’t being detected.
Are you passing Bonjour data on your network?
Beste,
In een huis op 1000km van mijn woning heb ik onlangs plug-in zonnepanelen geplaatst en 2 Homewizard KWh meters geplaatst om de opgewekte strook nuttig te kunnen gebruiken.
Het verbruik van het huis kan ik zien met een ZLinky_Tec meter (= equivalent van P1 meter).
De Homewizard P1 meter staat in mijn woning. Ter plaatse heb ik alles aangesloten met de api verbinding geactiveerd op mijn app en alles heeft, zelfs na mijn vertrek daar, nog 4 weken gewerkt. Sinds een paar dagen zijn de meters “onbeschikbaar”… De modem staat op 1 meter afstand van de meterkast (en dus KWh meters). Hoe krijg ik dit ‘op afstand’ terug werkende?
Dank voor Uw reactie!
Gebruik je de Cloud API van de P1 meter?
Ja…
If you could please keep the conversation in English as much as possible, then more people will be able to participate and help you. Please translate your post into English, otherwise it will be deleted in three days to keep the thread in just one language as stated in the forum rules Welcome to the forum!
If you need help, because depending on the trust level of your account, you may have limited permissions, please PM me or another moderator or reply to this post.
Hello,
I recently installed plug-in solar panels and two HomeWizard kWh meters at a house located 1,000 km away from my own home, in order to make effective use of the generated electricity.
I can monitor the house’s energy consumption using a ZLinky_Tec meter (equivalent to a P1 meter).
The HomeWizard P1 meter is located at my primary residence. I set everything up on-site with the API connection activated in the app, and the system worked perfectly for four weeks—even after I had left. However, for the past few days, the meters have shown as “unavailable.” The modem is located just one meter away from the meter cupboard (and thus the kWh meters). How can I get this working again remotely?
Thank you for your response!
Do you use the P1 meter’s Cloud API?
yes
Hi Jeroen. I have a look into the crash issue. I stopped HA reading HW items on the network, closed down one HW P1 meter, no solution there.
In HW itself there are no connection problems noticed.
In the end I removed the HW app from Homey and reinstalled, together with the battery combination and P1. Default settings (eg polling). So far so good.
No more crashes so I will ad more sockets to see if and where problems occur.
The problem is solved! The meters were automatically connecting to another wifi network… Sorry for disturbing you all with this 
Hi Jeroen,
I have set up a system to heat my boiler using surplus solar power. With the P1 meter, I detect how much energy I draw from or how much energy I feed into the grid. I use an energy socket to measure the boiler’s consumption. From the difference between the two, I calculate the power output with which I can now control the boiler.
Since one of the latest updates, I see that “energy_socket Polling time interval (set on 4 sec) is sometimes not in line with the polling time interval of the P1 meter (also set on 4 sec).
Therefore my system has becomes unstable because value of P1 is not in line with value of energy socket.
Also, the polling time value does not change when I change the polling time setting in the advanced settings of the energy socket. It was originally set to 4 seconds: if I change it to, for example, 10 seconds, the effective polling time remains 4 seconds.
I am on version 3.17.3
I understand your challenge but what you want is really tricky. If your wifi struggles the back off code kicks in and starts to delay next poll to get a proper fetch again that works (responds). Check the debug tab in app settings if you face connectivity issues as that clearly sound what bothers you at this moment.
The fetch logs are empty. The wifi signal is not at the strongest, but it has worked for almost 2 years now with te same wifi signal.
How do you explain that the polling time in the energy socket can not be modified?
