Everything should be fixed with latest update v3.8.11 that rolled out today.
1 Like
installed the update and it works again indeed.
Yes it was confirmed fixed Saturday as you can read up on this topic. It only needs to be validated by Athom team till they release it as public.
But good to hear it’s working again. 
live
v3.8.13
- Extra error handling (updateCapability) based on received crashreports
Works fine again. Thanks for the updates. Now time for Homey to introduce dynamic pricing.
They have. Else look at power by the hour app
1 Like
Yeah, but not (yet) for gasconsumtion.
Goodmorning,
I currently trying to pair a Homewizard 3 phase kWH meter with Homey.
I have connected it succesfully to the Homewizard app and local API is turned on.
However in homey it doesnt detect any new devices therefor i can’t link it.
Ive tried to restart both the device, and homey app.
As well as reconfigure the device Wifi but nothing has worked so far.
a8e09c6a-0082-4292-bfaa-53391da80aa0
You face a multicast/mDNS problem in your (wifi) network.
Try to reboot/restart your access point that connects your Homey and/or kWh meter.
This is not an app problem but a detection problem that Homey seeks devices but doesnt find any.
---- stdout ----
HomeWizard app ready!
2025-11-13T08:48:42.264Z [log] [ManagerDrivers] [Driver:energy] [Device:0d8fe8e5-95de-4289-a545-208501a90d4b] Polling settings for P1 apiv1: 10
2025-11-13T08:48:42.386Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:db09fdea-5078-4901-bf42-a6d7a87c626c] offset_polling 10
2025-11-13T08:48:42.388Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:3c5e8dcb-d5d2-4cc7-a6d4-bf652c099bfd] offset_polling 10
2025-11-13T08:48:42.390Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:db09fdea-5078-4901-bf42-a6d7a87c626c] URL: http://192.168.178.49:80/api/v1
2025-11-13T08:48:42.459Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:3c5e8dcb-d5d2-4cc7-a6d4-bf652c099bfd] URL: http://192.168.178.151:80/api/v1
2025-11-13T08:48:42.514Z [log] [ManagerDrivers] [Driver:energy] [Device:0d8fe8e5-95de-4289-a545-208501a90d4b] Discovered device URL: http://192.168.178.22:80/api/v1
2025-11-13T08:48:42.817Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:db09fdea-5078-4901-bf42-a6d7a87c626c] URL: http://192.168.178.49:80/api/v1
2025-11-13T08:48:42.825Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:3c5e8dcb-d5d2-4cc7-a6d4-bf652c099bfd] URL: http://192.168.178.151:80/api/v1
Discovered devices: {}
Discovered devices: {}
---- stderr ----
Hi Jeroen.
Is it possible for you to check which error(s) occur when I change the Plugin Battery mode via a flow? I want to use that within Homey but it isn’t possible now, it keeps on my mind…
I have 3 batteries, when I change the flow via my P1 advanced settings I can change the mode without a problem.
Via a flow I sometimes get a time out or a message it’s comlete but the mode doesn’t change never.
Via the P1 directly is handled different then via a flow?
My wifi works now for months with no problems (knock on wood).
I haven’t made a diagnostics report yet, will wait for your request for that. Thank you!
Or, is it a good idea to remove all batteries and P1 form Homey and start over again?
Thanks for your paypal donation.
And yes you can drop me a diag now I will catch it.
Received but I dont see you triggered the flow to change mode.
Make sure you try and then sent me a diag.
Thanks!
51f4d363-351c-472b-b05c-1c36d480c171
2025-11-13T14:05:07.156Z [log] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] 📈 Gas delta: 0 m³
2025-11-13T14:07:51.935Z [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
Error set mode to full charge: Error: Fetch failed: P1 Connection problem, max retries reached
at module.exports.api.setMode (/app/includes/v2/Api.js:184:23)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /app/drivers/energy_v2/device.js:241:28
stderr:
(node:133555) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
2025-11-12T12:22:20.845Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] ❌ Preflight check failed: request to https://192.168.1.131/api/system failed, reason: socket hang up
2025-11-12T16:50:47.056Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:8944f425-5096-4d69-b5d9-c3ada2ad16ef] ❌ Preflight check failed: The user aborted a request.
2025-11-13T13:43:17.720Z [err] [ManagerDrivers] [Driver:energy_v2] [Device:c76ed9d6-99fd-46e9-b534-1a3963ebb4dc] ❌ Preflight check failed: request to https://192.168.1.22/api/system failed, reason: Parse Error: Expected HTTP/, RTSP/ or ICE/
Attempt 1 failed: res.text is not a function
Attempt 2 failed: res.text is not a function
Attempt 3 failed: res.text is not a function
Attempt 4 failed: res.text is not a function```So, as I understand, the flow activates but the P1 cannot be reached. P1 IP-nr is correct (ending with 131).
Something to do with authorisation? Why does it work directly via advanced settings on the P1? For me not logical.
Or, perhaps my other P1 (ip ending with 22) is making trouble?
No issue is that the P1 is not accepting a new session (PUT).
Reason of that is not clear as I made an error in status text handling.
Let me improve that and put a test version with the adjustments.
In short, we should not change anything at your setup (yet).
I added realtime feature (websocket) and I am the first one using this for P1 (and battery).
Question here is if the http / put for changing the mode is impacted this way.
Sadly you are my first victim. 
Ah, thank you.
I checked the battery mode of the other P1 (ip ending 22) which doesn’t has batteries connected: I had problems and got a new P1 and connected the batteries to that. The mode of my old P1 (ip ending 22) was on full charge. I changed it via advanced settings to zero mode and run the flow again: mode was set to full charge. The flow card is for the other P1 (ip ending 131), see the image of the flow
Are there any other automation platforms connecting to your P1?
Just to be sure we are not overloading it from Homey and perhaps Home Assistant or other tasks.
Just to rule out if it is now related to websocket based communication with a fetch calls to adjust the mode for the battery.
Alright v3.8.14 is in test, try that. Trigger flow and sent diag please.
Hope we get more information what is going on there.
58b69a17-0fbb-4a60-8c28-105287cf64ce
I removed the P1 from HA, it was monitoring
