[APP][Pro] Homewizard 🧙‍♂️

Apps
, ,
3172

Thermometers work, but doorsensor does not.

3173

Strange ok, will check later. Log doesn’t show it is there. Maybe battery of the door sensor empty? Does it show in the Homewizard?

3174

I got this

v3.9.22

Homey Version
v12.10.0

Homey Model ID
homey3s

Homey Model Name
Homey (Early 2019)

Stack Trace
Note: this log has been manually submitted by a user.
Log ID: deabe110-07a7-477c-8750-d1878679ac46

User Message:
Door sensor not coming through, smoke detectors not tested.



---- stdout ----
2025-12-30T16:34:10.227Z [log] [HomeWizardApp] HomeWizard app ready!
2025-12-30T16:34:11.857Z [log] [ManagerDrivers] [Driver:homewizard] [Device:98b42a04-8212-420a-ae49-b465c1ea83a3] add device: "HomeWizard"
2025-12-30T16:34:11.870Z [log] [ManagerDrivers] [Driver:homewizard] [Device:98b42a04-8212-420a-ae49-b465c1ea83a3] HomeWizard preset polling every 30s (from main unit)
2025-12-30T16:34:11.875Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:49ba0864-2389-4d40-b6b7-7cc1a117689f] add device: "Zolder"
2025-12-30T16:34:11.876Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:49ba0864-2389-4d40-b6b7-7cc1a117689f] add device: "Slaapverdieping"
2025-12-30T16:34:11.878Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:49ba0864-2389-4d40-b6b7-7cc1a117689f] add device: "Woonkamer"
2025-12-30T16:34:11.879Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:49ba0864-2389-4d40-b6b7-7cc1a117689f] add device: " Keukenraampje "
2025-12-30T16:34:11.883Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:fd36eb42-a3d9-42a2-9f4f-28f2cdf74af6] add device: "Zolder"
2025-12-30T16:34:11.884Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:fd36eb42-a3d9-42a2-9f4f-28f2cdf74af6] add device: "Slaapverdieping"
2025-12-30T16:34:11.888Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:fd36eb42-a3d9-42a2-9f4f-28f2cdf74af6] add device: "Woonkamer"
2025-12-30T16:34:11.891Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:fd36eb42-a3d9-42a2-9f4f-28f2cdf74af6] add device: " Keukenraampje "
2025-12-30T16:34:11.892Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:eba9283a-f998-4e80-8137-de8efec09220] add device: "Zolder"
2025-12-30T16:34:11.893Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:eba9283a-f998-4e80-8137-de8efec09220] add device: "Slaapverdieping"
2025-12-30T16:34:11.895Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:eba9283a-f998-4e80-8137-de8efec09220] add device: "Woonkamer"
2025-12-30T16:34:11.896Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:eba9283a-f998-4e80-8137-de8efec09220] add device: " Keukenraampje "
2025-12-30T16:34:11.897Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:7e6d7b3b-1f27-42e7-8f69-f086fb6db7b9] add device: "Zolder"
2025-12-30T16:34:11.898Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:7e6d7b3b-1f27-42e7-8f69-f086fb6db7b9] add device: "Slaapverdieping"
2025-12-30T16:34:11.899Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:7e6d7b3b-1f27-42e7-8f69-f086fb6db7b9] add device: "Woonkamer"
2025-12-30T16:34:11.900Z [log] [ManagerDrivers] [Driver:kakusensors] [Device:7e6d7b3b-1f27-42e7-8f69-f086fb6db7b9] add device: " Keukenraampje "
2025-12-30T16:34:12.077Z [log] [ManagerDrivers] [Driver:energy] [Device:dae3366f-6c40-4572-8709-9ee9cf8032c3] Discovered device URL: http://192.168.2.9:80/api/v1
2025-12-30T16:34:27.978Z [fetchQueue] timeout: http://192.168.2.9:80/api/v1/data
2025-12-30T16:34:27.981Z [fetchQueue] timeout (abort): http://192.168.2.9:80/api/v1/data
2025-12-30T16:34:27.985Z [fetchQueue] retrying once: http://192.168.2.9:80/api/v1/data
2025-12-30T16:36:28.218Z [fetchQueue] timeout: http://192.168.2.9:80/api/v1/data
2025-12-30T16:36:28.220Z [fetchQueue] timeout (abort): http://192.168.2.9:80/api/v1/data
2025-12-30T16:36:28.221Z [fetchQueue] retrying once: http://192.168.2.9:80/api/v1/data
2025-12-30T16:39:28.589Z [fetchQueue] timeout: http://192.168.2.9:80/api/v1/data
2025-12-30T16:39:28.590Z [fetchQueue] timeout (abort): http://192.168.2.9:80/api/v1/data
2025-12-30T16:39:28.591Z [fetchQueue] retrying once: http://192.168.2.9:80/api/v1/data
2025-12-30T16:39:34.603Z [fetchQueue] timeout: http://192.168.2.9:80/api/v1/data
2025-12-30T16:39:34.604Z [fetchQueue] timeout (abort): http://192.168.2.9:80/api/v1/data
2025-12-30T16:39:34.605Z [fetchQueue] final fail: http://192.168.2.9:80/api/v1/data
2025-12-30T16:40:28.718Z [fetchQueue] timeout: http://192.168.2.9:80/api/v1/data
2025-12-30T16:40:28.720Z [fetchQueue] timeout (abort): http://192.168.2.9:80/api/v1/data
2025-12-30T16:40:28.721Z [fetchQueue] retrying once: http://192.168.2.9:80/api/v1/data

---- stderr ----
2025-12-30T16:39:34.647Z [err] [ManagerDrivers] [Driver:energy] [Device:dae3366f-6c40-4572-8709-9ee9cf8032c3] Poll failed: AbortError: The user aborted a request.
    at abort (/node_modules/node-fetch/lib/index.js:1458:16)
    at AbortSignal.abortAndFinalize (/node_modules/node-fetch/lib/index.js:1473:4)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:827:20)
    at AbortSignal.dispatchEvent (node:internal/event_target:762:26)
    at runAbort (node:internal/abort_controller:486:10)
    at abortSignal (node:internal/abort_controller:457:3)
    at AbortController.abort (node:internal/abort_controller:505:5)
    at Timeout._onTimeout (/includes/utils/fetchQueue.js:29:16)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7) {
  type: 'aborted'
}
3175

Yes, it shows opening and closing in HomeWizard.

Will try smoke detectors in one hour, when the dog is out :grinning_face:

3176

Ok I do see kaku sensors do something is working but don’t see errors at this moment.

3177

As far as I understand the log, it looks all right.

Will test “keukenraampje” and smoke detectors in about one hour and then come back.

1 Like
3178

It’s pretty dodgy and old. I try my best to improve with the ongoing Homey progression. WiFi stability is challenging.

Even your P1 struggles at the bottom (polling abort)

3179

I very much appreciate all your work to keep HW connected. I kept it because of the quite expensive (and new) Smartwares smoke detectors.

HW updated the P1 app. Looks nice, but it is messy. Changing colours, lots of closing and reopening the app for correct readings…

3180

Ah ok. I updated the test version (again) and will stick to the old method I used before directly node-fetch rather than the utility I made fetchQueue to streamline all fetches inside this app (Energy sockets, P1, kwh’s etc.) The old Homewizard unit has a very poor old wifi which seems to have problems with this so I tried and failed.

3181

Homey told me this morning around 06:00:

Sluipverbruik nacht ongeldig sterke fluctuaties in gebruik

En

Sluipverbruik fallback 110W

In the HW p1 app it was a mess. L3 is normally waving beautifully, refrigirator on/off… Now, up and down frantically, but… total consumption 0,7 kWh (normally around 2)

I start my tests now.

3182

Yes new feature I added. You can turn it off in the settings.

3183

Ok, but sorry, I do not understand, otherwise than that P1 gave false information.

Tested the “zolder” smoke detector, everything OK, reactions too.

And “keukenraampje” meldde daarna ineens ook keurig :thinking:

3184

Good, yes sorry I added “sluipverbruik” feature to P1.

3185

v3.9.24 (test/beta)

  • Wsmanager optimize
  • Homewizard legacy custom polling
  • Driver.js (apiv2) log fix (this.log undefined)
  • Thermometer rollback (name index matching doesnt work as expected)
  • Homewizard legacy → node-fetch and not the fetchQueue utility (bad user experience feedback)
  • Baseload (sluipverbruik) improvement (fridge/freezer should not be flagged as invalid )
3186

I guess my HWE-P1-G1 is “legacy”?

After v3.9.20 release my P1 stopped reporting in the middle of night and my power peak shaving flows stopped working. Manual restart of HomeWizard app solved the problem in the morning. The same problem occured last night, so I try v3.9.24 from now and automatic updates disabled.

I did some fallback flows for peak shaving in case of P1 not reporting and restart of Homewizard app after a while not reporting.

3187

No the Homewizard unit from 2012 is legacy which I still support. Your problem is different, I guess wifi problem but drop me a diagnostic report.

3188

I also noticed the “Baseload night invalid: strong consumption oscillation” in v3.57.20. After the update to v3.57.21 I received a “Fallback baseload” notification and further analysis showed the P1 values were only updated every hour or even less frequent since the last update. So far a restart of the app solved the issues. I have an older P1 with v1 api version.

Additional note: there is a “Watermeter” insight visible (with no data) as part of the P1 device.

3189

Watermeter is Belgium related. They have it linked to their P1 hence I had to add support for it. Might be something go wrong to remove it if that situation is not valid for others.

Yes I added sluipverbruik or baseload tracking during the night. You can turn it off in settings if you don’t like it.

3190

I also get the “Baseload night invalid” and “Fallback baseload” messages for my P1 meter. Figured out that it could be disabled, but what does it mean? Maybe it’s something that can be useful for me.

1 Like
3191

It’s an attempt to trace night usage of power adapters or other standby device lurking your energy usage. Any deviation on this would help detect this. But it is also a bit complex as there are freezers fridges EV cars eh heat pumps.

Maybe my quest has been a bit bold or enthusiastic.