[APP][Pro] Homewizard 🧙‍♂️

Apps
, ,
3293

Looks wifi problems to me. I think you Homey struggles:

User Message:
    Alles is offline

    stdout:
    2026-01-08T09:34:01.260Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-08T09:34:09.087Z [log] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Added capability "meter_water.daily"
2026-01-08T10:51:40.805Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-08T11:11:30.968Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-08T11:11:32.545Z [log] [ManagerDrivers] [Driver:SDM230] [Device:e94fe462-621f-4ca6-b7ab-989fc37e7ad0] Restored URL from settings: http://192.168.1.19:80/api/v1
2026-01-08T11:12:06.375Z [log] [HomeWizardApp] HomeWizard app ready!
2026-01-08T11:12:12.128Z [log] [ManagerDrivers] [Driver:SDM230] [Device:e94fe462-621f-4ca6-b7ab-989fc37e7ad0] Restored URL from settings: http://192.168.1.19:80/api/v1

    stderr:
        at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:19:03.521Z [err] [ManagerDrivers] [Driver:SDM230] [Device:e94fe462-621f-4ca6-b7ab-989fc37e7ad0] Failed to disable cloud: FetchError: request to http://192.168.1.19/api/v1/system failed, reason: connect EHOSTUNREACH 192.168.1.19:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:519:28)
    at emitErrorEvent (node:_http_client:107:11)
    at Socket.socketErrorListener (node:_http_client:574:5)
    at Socket.emit (node:events:519:28)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2026-01-08T11:19:44.642Z [err] [ManagerDrivers] [Driver:SDM230] [Device:e94fe462-621f-4ca6-b7ab-989fc37e7ad0] Failed to enable cloud: FetchError: request to http://192.168.1.19/api/v1/system failed, reason: connect EHOSTUNREACH 192.168.1.19:80
    at ClientRequest.<anonymous> (/app/node_modules/node-fetch/lib/index.js:1501:11)
    at ClientRequest.emit (node:events:519:28)
    at emitErrorEvent (node:_http_client:107:11)
    at Socket.socketErrorListener (node:_http_client:574:5)
    at Socket.emit (node:events:519:28)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  type: 'system',
  errno: 'EHOSTUNREACH',
  code: 'EHOSTUNREACH'
}
2026-01-08T11:20:13.873Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:20:14.079Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:20:43.876Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:20:44.077Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:24:14.202Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:24:14.209Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:24:24.206Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:24:24.210Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:25:14.253Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:25:14.260Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:24.405Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:24.411Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:34.392Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:34.400Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:44.423Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:44.427Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:54.410Z [err] [ManagerDrivers] [Driver:SDM230] [Device:d3a0a6a0-bbb1-489c-87ec-3c9e574b1308] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/SDM230/device.js:23:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
2026-01-08T11:26:54.415Z [err] [ManagerDrivers] [Driver:watermeter] [Device:76d7eb9c-904a-4aaf-981c-fe128cc584f2] Polling failed: Error: TIMEOUT
    at Timeout._onTimeout (/app/drivers/watermeter/device.js:17:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7)
3294

oke i will look in to it this evening, thanx

But the strange thing is that homey is on ethernet, and no other wifi device is having a problem.

And the android app of homewizard doesn’t have any problems.

3295

Yes that is strange, but log is pretty clear. Homey can’t reach your HW devices. Unrelated to my app. So if it is not your Homey, as its ethernet connected, then something else is a problem. I can’t answer that. Is it your DHCP that changed IP’s on those devices and mDNS not updating?

But again, I can’t fix your wifi that is yours to figure out.

3296

Hi Jeroen, I’ve rebooted Homey and the app as well (after Homey). Now all fine. Hope will stay that way and for now no action needed. Thx for prompt response!

1 Like
3297

Cannot connect Homewizard P1 dongle to Homey Pro 2026. Since yesterday i’m using a homey Pro 2026. Mainly bought for smart home but also planning to use for controlled charging / discharing Homewizard PIB. I’ve downloaded this app an added my 2 PIB, 1 x waterflow meter & 4 x smart plug and 1 x kWh meter without any issues. But I can’t connect my P1 meter.
Tried several things, e.g. only over 2,4 gHz, reset the P1 meter in the Homewizard app, closed and opened the API port, tried via a laptop / iPAD / Samsung smartphone but still it won’t connect.
Does anybody have an idea how to resolve?
Attached the error code.

Regards Bob.

Schermafbeelding 2026-01-09 091425
Schermafbeelding 2026-01-09 091425439×148 2.99 KB

3298

Your Homey Pro 2026 is unable to reach (EHOSTUNREACH) your P1 so investigate why that is.
I can’t determine your wifi set up or stuff around it. Maybe P1 firmware not updated?
Accesspoint with Guest Wifi? AP client Isolation?

3299

Hi Jeroen, the Homey pro is connect to my Fritzbox (KPN internet) router through the Homey ethernet adapter. P-1 meter is according to the homewizard app up to date (version 6.0206).
What I found typical was that all other HW components were easy to connect. Only the P-1 meter doesn’t.
Perhaps is use a direct wired connection with my laptop an option?

Rgds Bob

3300

No clue Bob, as you say. All other HW devices are fine but your P1 isn’t.
You share a error that says unreachable so yeah Homey cant reach it.

3301

Hello Jeroen, happy with the HomeWizzard app but the past days i have i think communication issues. Homey 2023, HomeWizzard dongle, 3fase kWh meter, water meter and 3 plug-in batteries. The batteries regulary lost p1 connection. Complete removal and re-setup according HomeWizzard instructions. All works. Next installation of homey homewizzard app and again loss of p1 connection between batteries in homewizzard app. Again removal of the homey homewizzard app and now the installation works as expected. Next week i will re install the homewizzard app but it apearres to me this will introduce communication overload. Tp link WiFi netwerk with 84-100% strength. Intention control of batteries, car charge and solar power. Latest versions and firmware. New HomeWizzard dongle expected monday.

1 Like
3302

Unfortunately I’ve the same as the people above here. Haven’t had any issues with the Homewizard app for the last years, but last week the watermeter and P1 meter loses connection with homey. The smart plugs keep working. A restart of the Homewizard app resolves the connection, but after a (few) day(s) it loses connection again. I’m using a Homey Pro 2019.

Nothing changed on my side like wifi wise etc. Only thing I saw we’re a lot of updates of the Homewizard app. Unfortunately it looks like they made the P1 meter and water meter homey connection unstable. Hope you can find the issue..!

1 Like
3303

That is odd as code for sockets share same structure. Drop me a diagnostics report.

3304

Drop me a diagnostics report.

3305

Try v3.10.5

3306

P1 went offline again after restart yesterday evening. So you must see anything in the diagnostics i think! I’m trying the test version now!

75fdafa9-ae1b-4137-b0e8-5308d2ab7cf2

3307

I think the code on recovering from wifi problems didnt work as exprcted. Test version should be better.

3308

Great you found it! Works for now, no news is good news!

3309

After yesterdays update of the test version app the 1 phase kwh meter is offline again. Going back to the non test version of the app gets it online.

1000076981
10000769811344×2992 183 KB

3310

Strange it makes no sense. You tried the v3.10.6?

3311

Yes, yesterday at 17.34 the app updated to 3.10.6, then the meter went offline. Tried a reboot on de the app with nog luck. Went back to 3.10.4 and it was back online.

3312

Let me review that driver why it stops.