[APP][Pro] Homewizard 🧙‍♂️

Jeroen_Tebbens · August 16, 2025, 3:46pm

Yes wifi trouble (Homey cant reach your SDM630 3 fase kwh and P1).

2025-08-16T10:05:22.556Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.101:80
    at ClientRequest.<anonymous> (/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-08-16T10:05:22.557Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.101:80
    at ClientRequest.<anonymous> (/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-08-16T10:05:25.376Z [err] [ManagerDrivers] [Driver:energy] [Device:7724cf9c-3acd-4372-b2cf-28c002ce4d36] FetchError: request to http://192.168.68.65/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/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-08-16T10:05:25.447Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/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-08-16T10:05:25.449Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/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-08-16T10:05:25.451Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/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-08-16T10:05:25.454Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/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-08-16T10:05:25.455Z [err] [ManagerDrivers] [Driver:SDM630] [Device:075a9b25-d6a8-4876-9da8-853177a05957] FetchError: request to http://192.168.68.101/api/v1/data failed, reason: read ECONNRESET
    at ClientRequest.<anonymous> (/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'
}

Melvin_Weerwag · August 16, 2025, 3:59pm

Thats strange because the kWh meter isnt giving any problem and giving thru all data. Have no missing data on the kWh meter side.

Will check my network log on the connection between the homey and my network. Will update you after i checked.

Jeroen_Tebbens · August 16, 2025, 4:00pm

Sorry can’t help it, this is what your log tells me.

This log clears every time my app is restarted.

Jeroen_Tebbens · August 16, 2025, 7:21pm

Found your issues, polling is 1s for both and probably with all other tasks you do with Homey and bit to much. Lower down the polling from 1 to perhaps 3s and see if it improves:

Settings for SDM630:  1
Polling settings for P1 apiv1:  1

Melvin_Weerwag · August 16, 2025, 7:35pm

Thanks Jeroen!

I indeed changed this to 1 second a few days ago. I’m going to rase it step by step to see what holds it.

After your previous message I trouble shoot everything in my network and I couldnt find anything. I even ordered the homey pro ethernet adapter to make a more stable connection and check if that will solve it.

Really didnt understand how it could be a network problem, have a really strong and stable home network

Jeroen_Tebbens · August 16, 2025, 7:39pm

I understand, I think the 1s is just to much for your current Homey set up.

Melvin_Weerwag · August 16, 2025, 8:59pm

Sadly even setting it to 10 seconds didnt solve it. But i’m seeing that the Homey Pro is going offline for a fraction of a second and after that it gives trouble with the P1 meter. So made a support ticket to Athom.

Thanks for you help so far Jeroen, i will give an update when Athom has more information and if it has something to do with the HW app.

Peter_Kawa · August 16, 2025, 9:50pm

Not to nag, but wouldn’t every HW app user report here if that was the case?

Melvin_Weerwag · August 16, 2025, 10:03pm

It doesnt have to be a thing everybody is experiencing. Could be something that happens to some kind of combined hardware combination.

i didnt said it to be negative. Just to lett Jeroen know that I will follow up if Athom comes with new information regarding the problem. Jeroen helped pretty well, so he deserves some kind of follow up.

Kevin_Vullings · August 17, 2025, 11:09am

5845e750-7d2b-433c-ad3e-9cb2010b54d7

Problemen met de app, wie kan me helpen?

SunBeech · August 17, 2025, 11:18am

It helps if your first explain the problem you are running into and only send an error log at the request of / based on the guidance of the developer.

Dijker · August 17, 2025, 11:28am

If you could please keep the conversation in English as much as possible, then more people will be able to participate and help you. Please translate your post into English, otherwise it will be deleted in three days to keep the thread in just one language as stated in the forum rules Welcome to the forum!

Please do also check out the categories in other languages:

Nederlands (Dutch)

If you need help, because depending on the trust level of your account, you may have limited permissions, please PM me or another moderator or reply to this post.

Or

Jeroen_Tebbens · August 17, 2025, 2:39pm

Check first post in this topic for tips:

Logs show wifi problems:

2025-08-17T11:07:05.480Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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-08-17T11:07:15.496Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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-08-17T11:07:25.512Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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-08-17T11:07:35.529Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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-08-17T11:07:45.546Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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-08-17T11:07:55.592Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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-08-17T11:08:05.576Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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-08-17T11:08:15.624Z [err] [ManagerDrivers] [Driver:energy] [Device:3bb15a63-8e39-4b0e-a50f-8a205e5491ac] FetchError: request to http://192.168.68.18/api/v1/data failed, reason: connect EHOSTUNREACH 192.168.68.18:80
    at ClientRequest.<anonymous> (/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'
}

Roger_Gorissen · August 17, 2025, 9:16pm

I’m experiencing the same problem @Melvin_Weerwag describes. Every x minutes my HW P1 meter is having a red triangle, no connection possible. Restarting the HW app solves the problem for some time. The watermeter works fine, no problem.

Although this shouldn’t happen, I’m looking for a way to notice it by a flow to restart the app. Netscan doesn’t help me this far. I thought the P1 meter loses it’s connection to the router. Nope.

The problem arose when I changed from the white Homey Pro (2019) to the mew Homey Pro (2023). Before that everything worked just fine.

I’ll check the polling interval as Jeroen describes.

Edit: I changed the polling interval from 2 to 5 seconds. The energy meter is still online, no red triangle so far (12 hours have passed since I made the change )

Jeroen_Tebbens · August 18, 2025, 10:17pm

beta/test:

v3.6.58

* Bugfix that was caused by experimental firmware Homey 12.5.2RC3 and slider capability that could not be removed

* Added energy flags for sockets so they can trace imported/exported energy in Homey Energy Dashboard (Home Batteries connected via sockets, eg Marstek, Zendure, Anker, eeeeh)

* Code cleanup

* Added some fine tuning to spread the API call’s to the P1

Jeroen_Tebbens · August 18, 2025, 10:21pm

version v3.6.57 should fix this.

Johan_Bruyn · August 18, 2025, 10:34pm

Unfortunately battery 2 lost in the beta.

b9349f21-8776-4a0b-892c-5ffde228f5e9

Jeroen_Tebbens · August 18, 2025, 10:49pm

Fixed in v3.6.58

Johan_Bruyn · August 19, 2025, 7:01am

Thanks, battery 2 is now also reporting values. I’ve reset the P1 meter’s polling to 10 seconds. We’ll see what happens.

Jeroen_Tebbens · August 19, 2025, 7:13am

@Gerard_L is also testing atm

Topic		Replies	Views
[APP][Pro][NL] Homewizard 🧙‍♂️ Apps	585	13713	November 27, 2025
Homewizard P1 dongle 🇳🇱 Nederlands (Dutch)	65	6668	December 12, 2024
Homey Energy Dongle ⚡️ - Megathread Energy	206	6531	October 3, 2025
New low cost P1 energy measuring Wifi "dongle" Devices app , dsmr , wifi	45	5637	September 18, 2020
[APP][Pro] Domoticz - Control at your finger tips Apps app , domoticz , homey-pro	122	11075	October 31, 2025

[APP][Pro] Homewizard 🧙‍♂️

Related topics