That communication is cloud based and has nothing to do with the direct polling every 10s between Homey and every Homewizard device.
But the log definitely points to connection issues. A json payload that is broken (ie. Json message lacks brackets or lines) gives me proof the connection is dropped or disconnected/broken.
Check the first post in this ticket for troubleshooting tips.
EDIT: my guess your Homey maybe has wifi issues, move it or see how you can improve wifi stability. (try ping test for a long run (1 hour?) to see if ping is dropped, same for P1 and/or energy sockets.
Okay Jeroen, for the sake of troubleshooting I will perform some network stability tests.
Just recovered from another glitch. After restarting the homewizard app in homey, things return to normal.
Screenshot homewizard ;
Screenshot homey ;
Restart app;
Sorry Marco but I try to help/think what might the problem, okay?
I have no clue how everyone has their wifi or network has been set up.
I can only judge on what is said/experienced and what potentially is captured in the logfile. The rest is a black box for me. I do this voluntarily and pure hobby driven. Just read this topic you can see there are other users that almost share the same experience, yet have different problems or causes. Being routers, access points, firmware updates of devices.
I try my best here but also could not care and spend more time with my family.
1 Like
Jeroen, please dont feel/see my report as an insult to your efforts! I know and realise there are many variables, certainly when a device is wifi connected. So please be aware, your efforts are deeply appreciated.
A quick ping to my Homey the last half hour from a laptop showed me
Packets: Sent = 1948, Received = 1946, Lost = 2 (0% loss),
2 packets lost seems negligible.
I will investigate further. Pinging the powersockets and P1.
Update:
Energy socket:
Ping statistics for 172.16.11.136:
Packets: Sent = 1609, Received = 1604, Lost = 5 (0% loss),
P1:
Ping statistics for 172.16.11.163:
Packets: Sent = 1258, Received = 1255, Lost = 3 (0% loss),
1 Like
Your choice of words “for the sake of troubleshooting” that sounded wrong to me. But fine thanks for responding to correct my feeling.
3 Likes
Hi Jeroen,
First of all thanks for making this app so we can see it in Homey.
Maybe I got the same problem as Marco, but the devices are offline and when I want to re-add then to homey, the devices can’t be found. (removed them from homey)
This is my code to see hopefully the problem: 9e189691-5b25-48a1-8ff6-c0a1568ded41
- Running version v3.2.22
- Also used DNS discovery on iOS and then I can find the 2 devices on the network.
- Already rebooted everything to hope solve the issue.
Hope this is enough for now to get an idea of the situation.
Your diagnostic report is empty so got no leads to what might be wrong.
As you removed them I dont have a clue what was the cause. Remove power to P1, sockets etc first and then power them. Then restart the Homewizard Homey app and try again.
Hope photo is viable, but strange that log was empty.
Remove devices and waited around 30 sec - 1 min after it was online in homewizard app I tried to add it in honey but sadly still no luck
Then I cant help you. Something must be wrong with mDNS.
Check if Local API is enabled in the Homewizard Energy app.
Restart your access point that connects both your Homey and/or your Homewizard Energy devices.
Are both in the same network? Same SSID?
Is there no AP Client isolation? Vlans? mDNS relay/proxy active?
Here same problem like Lars.
No connection error and when I try to re add nothing found. Have multiple plugs and the other ones are working fine.
The plug that isn’t found anymore still works fine in home assistant.
Local api enabled, tried restarting router.
Still going to try another IP address.
Did you try static reservation in your DHCP server?
Thanks for your reaction of the diagnostic report. My local API is on and not off. Home assistant also uses local APi
Well the log clearly says forbidden on one of your sockets. I can’t tell which socket is what. Also it shows some host unreachables entries so that refers WiFi connection issues.
Thanks, I will try a full reset than.
Did a full reset, doesn’t work either
82dab557-1ee5-46ec-a2d2-eaf8217206b9
Op address of the socket has changed, still not findable
So yeah…still connection issues:
2024-01-26T16:32:47.787Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:1e3d31f4-25e3-4882-914a-8e7f21744e7e] FetchError: request to http://192.168.2.68/api/v1/state failed, reason: connect EHOSTUNREACH 192.168.2.68:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketErrorListener (node:_http_client:501:9)
at Socket.emit (node:events:517:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: ‘system’,
errno: ‘EHOSTUNREACH’,
code: ‘EHOSTUNREACH’
}
2024-01-26T16:32:47.788Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:1e3d31f4-25e3-4882-914a-8e7f21744e7e] TypeError: Cannot read properties of undefined (reading ‘ok’)
at /app/drivers/energy_socket/device.js:172:16
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-01-26T16:32:50.857Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:1e3d31f4-25e3-4882-914a-8e7f21744e7e] FetchError: request to http://192.168.2.68/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.2.68:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:517:28)
at Socket.socketErrorListener (node:_http_client:501:9)
at Socket.emit (node:events:517:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
type: ‘system’,
errno: ‘EHOSTUNREACH’,
code: ‘EHOSTUNREACH’
}
With mdns app I get this
energysocket-075862._hwenergy._tcp.local.
energysocket-075862.local:80
192.168.2.69:80
api_enabled = 1
path = /api/v1
product_name = Energy Socket
product_type = HWE-SKT
serial = xxxx075862
Ok so error is from other socket.
connect EHOSTUNREACH 192.168.2.68:80
So are all devices on same wifi access point? Same network? No AP client isolation active? Any VLAN in play? Which flavor/vendor/brand wifi are you using? Sorry to many unknown parameters.
Same socket is just about 5cm next to it.
Works fine.
Unifi access point (other socket is on the same access point as well. Same vlan, nothing changed in the network before it stopped working.
All the rest is working fine, socket not showing up is also working fine in home assistant
No socket on .192.168.2.68 anymore btw (moved to 192.168.2.69)
46bf4790-a9b8-494f-bee1-f10d1a251672
