Its solverd! I think I know what happened. Lately, I’ve often experienced Homey losing its connection to the network, and at Athom’s request, I had to go through some procedures. As a result, Homey was moved to a different location and switched from a wired LAN connection to wireless (hopefully temporarily). Today I restarted my entire network now that everything is running wirelessly, and within moments, Homey was able to find the HomeWizard devices again. I’m not sure if this sounds plausible? But it worked for me.
1 Like
By the sounds you have your wireless network AP client isolation activated. This is a setting that blocks AP client to client communication. While the LAN isnt impacted like that. To me is the only plausible reason it would fail like that. But good to hear it works.
Any IoT vlan active? Maybe Homey reboot (mDNS lost in homey), as I am out of options at this moment. If it would be a bug in the app this would hit more people than just you.
No IoT or vlan. I will investigate further for other possible solutions.
Thanks for your support.
After rebooting my Homey, the problem was solved for me.
I had the same issue since this morning after the update to 3.6.50.
Is working again. Had to enable wifi on my Homey. This was not enabled while it was using a cable connection. Was no problem before… maybe Homey issue.
Thanks for your update and confirmation/reason of your issue.
Dear,
First of all, thank you for the fantastic app! I’m very happy with it!
One small thing. In the latest update (3.6.50), the polling update interval for the p1 meter seems always 1 second, regardless of what I set it to. The problem is that the p1 meter freezes every few hours. It stops responding (even in the official app itself) until I power cycle it. Is this easy to fix? Thanks for your help!
Try changing it and restart my app.
I have done that multiple times. I’ve set it now to 3 sec but still updating every sec. Diag report : bd30a931-ecc6-4bfb-9fbf-ae1896fb9768
Thanks for your time!
Ps. It looks like that a change is working. But when I look back after 15-30 min it is again updating every second.
It is not polling every second but due to the retry code it maybe feels like that. Your problem is wifi connection related. Please focus on improving your wifi first:
Stack Trace
Note: this log has been manually submitted by a user.
Log ID: bd30a931-ecc6-4bfb-9fbf-ae1896fb9768
User Message:
Diag report polling interval
stdout:
polling_interval: 2,
cloud: 1,
number_of_phases: 3,
phase_capacity: 40
},
changedKeys: [ 'polling_interval', 'phase_capacity' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:07:43.369Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 3
2025-07-22T05:12:07.080Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings updated
2025-07-22T05:12:07.081Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings: {
oldSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 2,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:12:07.081Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 2
2025-07-22T05:13:26.429Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings updated
2025-07-22T05:13:26.430Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings: {
oldSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 2,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:13:26.437Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 3
2025-07-22T05:46:31.608Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings updated
2025-07-22T05:46:31.608Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings: {
oldSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 4,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:46:31.608Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 4
2025-07-22T05:46:36.983Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings updated
2025-07-22T05:46:36.983Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings: {
oldSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 4,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:46:36.985Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 3
stderr:
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-22T04:59:47.920Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-22T04:59:47.943Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-22T05:00:32.973Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-22T05:00:32.976Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-22T05:01:13.856Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect ETIMEDOUT 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ETIMEDOUT',
code: 'ETIMEDOUT'
}
2025-07-22T05:05:32.436Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-22T05:05:33.984Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ECONNRESET',
code: 'ECONNRESET'
}
2025-07-22T05:05:34.030Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: read ECONNRESET
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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: 'ECONNRESET',
code: 'ECONNRESET'
}
1 Like
Thanks!
Strange. My WiFi (Asus mesh) is very stable. I have more than 100 devices online and none of them have issues. This device is at 1 m from a router.
I also see settings in the diag report that are different than my settings. Is it possible that there is a mismatch in the settings in the diag report and my device settings?
Update: sorry, see now the changed values too. Was reading on my phone. Will restart WiFi now.
Thanks for your time!
(P.s. until yesterday, this p1 meter never fails. Will reboot all the routers now)
Maybe accidentally an other user diag report. Sorry getting nuts on unasked reports.
Sent me a diag report.
1 Like
I think I see the problem. When I block Wi-Fi for 20 seconds for the p1 meter and then unblock it, Homey goes crazy with updates. It seems that the polling timer does not start after a successful ‘poll’, but that they pile up and are caught up. Assumption: The meter crashes due to the many requests/updates and needs a power cycle.
Is this a strange thought?
Here my diag report. Thanks again for your great support!
2ae38e6b-b98d-4178-a4ca-0d0d7ab844af
Why would you block your P1?!
Sorry you enforce your WiFi connection and ask me to explain why P1 doesn’t update properly?
Sorry, my English isn’t very good. Maybe I didn’t explain it clearly.
I never block my Wi-Fi. I was trying to see what might have happened. You said that my Wi-Fi seemed unstable. So I thought I would block the meter from the Wi-Fi for a short time and then unblock it to see what happened. After releasing it, Homey seemed to update once or twice per second (setting polling 3 sec), and then the meter stopped working again. I thought maybe I had found the problem and that the dongle was ‘overloaded’ with (stacked) poll requests and had crashed or something.
Of course, I don’t normally block devices on the network. I did it in the hope of identifying the problem.
Then last report you sent is pointless for me to check as the errors I see can’t be linked to the real problem or the one you forced by disabling your P1 wifi.
Restart my app, wait 15min and then hit diag report again.
Thanks! Done (2 hours ago) and here the diag code: b042e327-aa50-42b6-b485-7a568f6e6a30
So yes your wifi is still a problem:
Hi Jeroen Tebbens,
Your app HomeWizard has received a diagnostics report.
You can reply to this e-mail to get in touch with the user. Note that the user will then be able to see your e-mail address.
App ID
com.homewizard
App Version
v3.6.50
Homey Version
v12.5.1
Stack Trace
Note: this log has been manually submitted by a user.
Log ID: b042e327-aa50-42b6-b485-7a568f6e6a30
User Message:
And a new report
stdout:
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 2,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:12:07.081Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 2
2025-07-22T05:13:26.429Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings updated
2025-07-22T05:13:26.430Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings: {
oldSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 2,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:13:26.437Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 3
2025-07-22T05:46:31.608Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings updated
2025-07-22T05:46:31.608Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings: {
oldSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 4,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:46:31.608Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 4
2025-07-22T05:46:36.983Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings updated
2025-07-22T05:46:36.983Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Settings: {
oldSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 4,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
},
changedKeys: [ 'polling_interval' ],
newSettings: {
energy_cumulative_include: true,
energy_exclude: false,
polling_interval: 3,
cloud: 1,
number_of_phases: 3,
phase_capacity: 25
}
}
2025-07-22T05:46:36.985Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] Polling_interval for P1 changed to: 3
2025-07-22T06:05:12.466Z [log] [ManagerDrivers] [Driver:watermeter] [Device:2dd19179-6a1f-4d7f-a20f-1160de44fa70] URL: http://192.168.1.190:80/api/v1
2025-07-22T06:05:12.471Z [log] [ManagerDrivers] [Driver:watermeter] [Device:2dd19179-6a1f-4d7f-a20f-1160de44fa70] URL: http://192.168.1.190:80/api/v1
2025-07-22T06:05:17.357Z [log] [ManagerDrivers] [Driver:watermeter] [Device:2dd19179-6a1f-4d7f-a20f-1160de44fa70] URL: http://192.168.1.190:80/api/v1
2025-07-22T06:06:31.656Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] URL: http://192.168.1.126:80/api/v1
2025-07-22T06:06:31.782Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] URL: http://192.168.1.126:80/api/v1
2025-07-22T06:06:31.786Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] URL: http://192.168.1.126:80/api/v1
HomeWizard app ready!
HomeWizard EnergyLink has been inited
HomeWizard Heatlink has been inited
HomeWizard has been inited
HomeWizard Kakusensors has been inited
HomeWizard Rainmeter has been inited
HomeWizard Thermometer has been inited
HomeWizard Wattcher has been inited
HomeWizard Windmeter has been inited
Polling settings for P1 apiv1: 3
Offset polling for Watermeter: 10
2025-07-22T06:52:46.271Z [log] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] URL: http://192.168.1.126:80/api/v1
2025-07-22T06:52:46.370Z [log] [ManagerDrivers] [Driver:watermeter] [Device:2dd19179-6a1f-4d7f-a20f-1160de44fa70] URL: http://192.168.1.190:80/api/v1
stderr:
type: 'system',
errno: 'EHOSTUNREACH',
code: 'EHOSTUNREACH'
}
2025-07-22T06:06:02.878Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
2025-07-22T06:06:05.950Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
2025-07-22T06:06:09.023Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
2025-07-22T06:06:12.094Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
2025-07-22T06:06:18.911Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
2025-07-22T06:06:21.982Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
2025-07-22T06:06:25.055Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
2025-07-22T06:06:28.126Z [err] [ManagerDrivers] [Driver:energy] [Device:f7783c34-5099-4660-9bcd-51f89db140e2] FetchError: request to http://192.168.1.126/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.1.126:80
at ClientRequest. (/app/node_modules/node-fetch/lib/index.js:1501: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'
}
You can manage your email settings in the Homey Developer Tools.
1 Like
