Thx; I requested Beta-access for my P1 and Watermeter
1st impression: the beta-firmware seems to solve it. No connection problems since the update.
I think it’s to early to be certain, but this looks good.
Here also no problems with the beta-firmware for the energy socket. Works fine. Cross fingers that the beta firmware solved the connection problems.
1 Like
I see there is a fix for the connectivity issue with beta software. I will look into that 
I did create a debug log for missing devices I see every morning when I startup homey. Just FYI: 862a5bc1-b814-4ccc-8f0b-7b65a1a54aa9
This is beta firmware is about P1. Not sure if that “bug” is affected in the socket firmware.
Your error is on unreachable which is different from connection refused.
So to me its more a WIFI issue you face.
2024-03-13T06:51:54.768Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:a971430d-1e03-41fc-9557-f01f4cb72df2] FetchError: request to http://172.16.11.140/api/v1/data failed, reason: connect EHOSTUNREACH 172.16.11.140:80
at ClientRequest. (/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:526:28)
at Socket.socketErrorListener (node:_http_client:442:9)
at Socket.emit (node:events:526:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
type: ‘system’,
errno: ‘EHOSTUNREACH’,
code: ‘EHOSTUNREACH’
}
Hi Jeroen
I did some debugging ; 75b8a3a9-e238-43f9-9b42-15dfba9fde15 is a diagnostic report showing all devices online. The devices that report issues have a weak wifi signal and tend to flip ip’s more often then devices with stronger signal.
I have a cabled mesh router setup in my home and with sophisticated devices I can get a good connection even on the spot where a homewizard plug is connected and reports a weak signal. I know the 2,4 band can be cluttered so I will look into moving the channel from auto to designated. It might just do the trick.
Keep you posted
Yeah sounds about I feel is the core problem. Static ip / reserve dhcp scope will help as well for mDNS cycle ip is still a challenge for Homey. Code has “onDiscoveryAddressChanged” but that doesnt seem to trigger, hence I keep suggesting to reserve ip addresses in the DHCP server.
1 Like
That is also a good idea and see if this eliminates the offline experiences. I will revert.
Update: devices stay online-ish, no (dis)connection errors anymore
Installed a P1 , but it does not show all of the voltages and the current . Is it something i have done wrong you think ? Missing: amp 2and 3. , voltage : l2, l3
I think you might still have “older” firmware running on you P1. Voltage has been only recently enabled in newer.
Restart the Homewizard Homey app
Tried that , not working 
Also tried to remove and add it again in Homey.
Strange stuff.
Seems that it belives ti be only 1 phase system.
But in homewizard app it shows voltage for L1/2/3
I need the API output of your P1. Either you hit a bug in my code or your P1 doesnt register voltages.
wifi_ssid":"SkyNet","wifi_strength":54,"meter_model":"HDLC","unique_id":"7359992909443328","total_power_import_kwh":216026.929,"total_power_import_t1_kwh":216026.929,"total_power_export_kwh":0,"total_power_export_t1_kwh":0,"active_power_w":4786,"active_voltage_l1_v":231.7,"active_voltage_l2_v":233.4,"active_voltage_l3_v":232.7,"active_current_l1_a":4.6,"active_current_l2_a":12.9,"active_current_l3_a":3.4,"external":[]}
I need to investigate this.
Drop me a diagnostic report as well, maybe it hints me where the error/bug might be.
caf461ae-e50c-493b-b308-6c93fe1a6ece
Ok got it, thx
Did your share your full API output? As I cant find your l1, l2, l3 watt.
|active_power_l1_w|Number|The active usage for phase 1 in watt|
|active_power_l2_w|Number|The active usage for phase 2 in watt|
|active_power_l3_w|Number|The active usage for phase 3 in watt|
