Hi Jeroen, good morning. I have now more time to setup flows for my 3 HW batteries.
When I change the mode via the P1 meter advanced settings the battery mode changes accordingly.
When I use a flow to set the mode for example to “volledig oplaad modus” then the battery mode doesn’t change, no error message btw. I use the beta version, and I switched to a new p1 meter a few months ago, the old P1 meter is still active and used for monitoring. The batteries are connected to the new P1 meter and everything is working fine.
I made a new flow this morning and got the same result, no mode change.
Do you have an idea what I’m doing wrong?
You added the 2nd one as a APIv2? Drop me a diagnostic report so I can have a look in your app log.
Homey can’t reach your P1….
2025-08-19T05:06:20.345Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Error: Network error: request to https://192.168.1.22/api/batteries failed, reason: connect ETIMEDOUT 192.168.1.22:443
at /app/includes/v2/Api.js:122:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getMode (/app/includes/v2/Api.js:116:17)
at async /app/drivers/energy_v2/device.js:466:29
2025-08-19T05:09:30.803Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Error: Network error: request to https://192.168.1.22/api/system failed, reason: connect ETIMEDOUT 192.168.1.22:443
at /app/includes/v2/Api.js:84:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getSystem (/app/includes/v2/Api.js:78:17)
at async /app/drivers/energy_v2/device.js:301:26
2025-08-19T05:40:54.964Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Error: Network error: request to https://192.168.1.22/api/system failed, reason: connect ETIMEDOUT 192.168.1.22:443
at /app/includes/v2/Api.js:84:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getSystem (/app/includes/v2/Api.js:78:17)
at async /app/drivers/energy_v2/device.js:301:26
2025-08-19T06:27:43.235Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] Error: Network error: request to https://192.168.1.131/api/batteries failed, reason: socket hang up
at /app/includes/v2/Api.js:122:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getMode (/app/includes/v2/Api.js:116:17)
at async /app/drivers/energy_v2/device.js:466:29
That’s weird, I do not understand, ip ending 131 is the new one with the batteries connected.
They (P1 meters and batteries) are working in Homey, I can see them in the overview and they are sharing realtime data. When I change the mode via advanced settings on the P1: that is working every time, there is also a network connection needed or it works differently?
Hi Jeroen back in town 
Short reminder for the coming weeks; implementing day usage also for P1 APIv2.
Is your flow updated as well using the new P1 as changing the mode? Maybe rename both P1’s and then check your flows you sending the mode.
But this is what I observe from the log.
1 Like
Thanks, I knew I forgot something..
I will delete all flows and start again. I wll let you know!
A new flow didn’t work…
You don’t have to, just replace the card but fine, up to you.
Ok restart app (to clear logs),
Execute flow, then sent diagnostic report again.
Done, restart, new flow: 12e5636f-6556-47e2-bd2b-e11e0cbda79f
And after rename p1: 60288c70-07c6-4334-8926-c45a5fc3a948
I am afraid you have some wifi work to crack:
Homey cant reach your P1 it seems struggling connecting, socket hanging etc.
See if you can move your Homey a little? Check access point etc. But this is beyond me or my app.
2025-08-19T07:36:33.733Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] Mode for Plugin Battery via P1 advanced settings changed to: zero
api.setMode: This mode will be sent to P1apiv2: zero
2025-08-19T07:41:19.163Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Set mode to standby: standby
2025-08-19T07:41:21.985Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Battery mode changed to: standby
2025-08-19T07:45:18.512Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Full Charge Mode
api.setMode: This mode will be sent to P1apiv2: to_full
Set mode to full charge: to_full
2025-08-19T07:45:21.847Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Battery mode changed to: to_full
2025-08-19T10:35:08.031Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Set mode to standby: standby
2025-08-19T10:35:13.164Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Battery mode changed to: standby
2025-08-19T10:38:30.638Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Set mode to standby: standby
2025-08-19T10:42:43.675Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Set mode to standby: standby
2025-08-19T10:45:08.099Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Set mode to standby: standby
2025-08-19T10:52:12.495Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Set mode to standby: standby
2025-08-19T10:55:07.111Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ActionCard: Set Battery to Standby Mode
api.setMode: This mode will be sent to P1apiv2: standby
Set mode to standby: standby
stderr:
2025-08-19T03:30:20.062Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] Error: Network error: request to https://192.168.1.131/api/batteries failed, reason: socket hang up
at /app/includes/v2/Api.js:122:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getMode (/app/includes/v2/Api.js:116:17)
at async /app/drivers/energy_v2/device.js:466:29
2025-08-19T05:06:20.345Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Error: Network error: request to https://192.168.1.22/api/batteries failed, reason: connect ETIMEDOUT 192.168.1.22:443
at /app/includes/v2/Api.js:122:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getMode (/app/includes/v2/Api.js:116:17)
at async /app/drivers/energy_v2/device.js:466:29
2025-08-19T05:09:30.803Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Error: Network error: request to https://192.168.1.22/api/system failed, reason: connect ETIMEDOUT 192.168.1.22:443
at /app/includes/v2/Api.js:84:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getSystem (/app/includes/v2/Api.js:78:17)
at async /app/drivers/energy_v2/device.js:301:26
2025-08-19T05:40:54.964Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] Error: Network error: request to https://192.168.1.22/api/system failed, reason: connect ETIMEDOUT 192.168.1.22:443
at /app/includes/v2/Api.js:84:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getSystem (/app/includes/v2/Api.js:78:17)
at async /app/drivers/energy_v2/device.js:301:26
2025-08-19T06:27:43.235Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] Error: Network error: request to https://192.168.1.131/api/batteries failed, reason: socket hang up
at /app/includes/v2/Api.js:122:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getMode (/app/includes/v2/Api.js:116:17)
at async /app/drivers/energy_v2/device.js:466:29
2025-08-19T10:00:47.519Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] Error: Network error: request to https://192.168.1.131/api/measurement failed, reason: socket hang up
at /app/includes/v2/Api.js:65:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getMeasurement (/app/includes/v2/Api.js:59:17)
at async /app/drivers/energy_v2/device.js:299:20
2025-08-19T10:27:51.674Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] Error: Network error: request to https://192.168.1.131/api/system failed, reason: socket hang up
at /app/includes/v2/Api.js:84:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getSystem (/app/includes/v2/Api.js:78:17)
at async /app/drivers/energy_v2/device.js:301:26
2025-08-19T10:50:45.239Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] Error: Network error: request to https://192.168.1.131/api/batteries failed, reason: socket hang up
at /app/includes/v2/Api.js:122:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async module.exports.api.getMode (/app/includes/v2/Api.js:116:17)
at async /app/drivers/energy_v2/device.js:466:29
Thanks!, I will look into that this evening and try rebooting things and change location. Perhaps the connected pod has issues…
Cant tell from the logs. I can only see the Homey side of it and that is unable to communicate reliably with your P1.
1 Like
Yeeh, it works! Thanks!
No problem, thanks for your donation 
1 Like
Since some time my p1 meter is displaying an error
However, insights are updated 
so everything still works flows-wise. When I reset the Homewizard app the device is displayed correctly but at the most for a couple of hours.
The device is also online at the IP-adress (of course, otherwise insights also would not work)
Any advice?
Homey can’t reach your P1 randomly so it’s WiFi problem. So some flows only need a datapoint from your P1 so it triggers but it needs to be stable steady.
For me it is impossible to support all WiFi setups as I don’t know the brand, how many AP’s. First post in this topic has some suggestions but it really depends on your own WiFi network coverage and stability for all your HW devices and your Homey.
Another note if you changed the interval from 10 to 1 I would suggest to raise it a little.
What interval are you talking about? Btw the Homewizard app reports 50% wifi coverage (never seen this functionality before), so I think that could be better indeed
edit: I see what interval you mean. Did not change it
