Correct, a Ziggo router + wifi + pods can be nice “out of the box” but when you starts to play with the advanced stuff you will hit walls of settings you can’t find or change. TP-LINK DECO also a challenge. Lovely meshing features but when you have to start adjusting or disabling multicast you end up with empty hands.
I can say Unifi + AP’s work fine, using them myself even IoT-vlan for all the sockets, 2x P1’s, 1x PIB, Display, Kwh without problems.
But as you noticed, while I do understand and have the knowledge what are common issues here I cant support this from this app point of view.
Nice to know and I understand!
I use the “batterij” in app settings. But it seems that the price per battery doesnt multiply in the bottem where it says “werkelijk gemeten rendement”. Or do i read this the wrong way?
when i put it on 1400 per battery the actual roi of my settup seems verry positive 
When i put it on 4200, it seems more correct at the bottom but the top seems a bit long for the extra battery:
But maybe im wrong at this, im verry new to this homey and homewizard.
Good catch, lost track of that tab lately.
I would like to run the test version, does this run next to the regulair version? I would not want to lose my settup or data
Besides this i have an other question, I am using the battery pollacy but is there a way to pause the learning?
For instance, I have a mobile airco and i use it on irregualar times, I dont want that in the learning data. So i want to make a flow:
when xx has started or question etc etc then pause learning for … min/hour or set on/off. I thought maybe the flow card EV charging would do the same but that is only for the battery charging mode.
No it does not run on the side / parallel. It basically runs a test/beta version with the last fixes I added and then it I find it stable it gets a prod/stable flag in the store. Data used stays as is independent of the version.
You can only jump between live and test version or homey cli install an other version from git (not for the faint hearted).
I would suggest to temporarily disable learning is to disable the policy in general and then enable again when you want it.
Other option is the “away” card that has been added on that device. You can pick “zero” / nul op de meter mode or standby (battery does nothing). That too stops learning and should not polute your learning. But these incidetal airco on / off will not hurt that much over the longer timespan as they will fall away on the precentile method used in the learning process. Which is also split per day.
Hi @Jeroen_Tebbens sinds 3 dagen staan mijn HomeWizard apparaten 's ochtends als niet beschikbaar. Zowel de P1 meter, watermeter als twee stekkers. Na een herstart van de app starten ze wel weer op, maar er lijkt iets structureel mis te gaan. Mogelijk kun jij het uit het diagnostische rapport halen wat er mis gaat? Alvast bedankt!
a0b67e91-551b-41cf-a8fd-f88b9b9212ec
Hi @Jeroen_Tebbens for the past 3 days, my HomeWizard devices have been showing as unavailable in the mornings. This applies to the P1 meter, water meter, and two plugs. After restarting the app, they do start up again, but something seems to be going wrong structurally. Perhaps you can figure out what is going wrong from the diagnostic report? Thanks in advance!
a0b67e91-551b-41cf-a8fd-f88b9b9212ec
Hi, looks like you are still running a version from February moreover you restarted the app after the issue observed so all log is lost so cant help:
App Version
v3.13.28
Homey Version
v13.2.4
Homey Model ID
homey3s
Homey Model Name
Homey (Early 2019)
Stack Trace
Note: this log has been manually submitted by a user.
Log ID: a0b67e91-551b-41cf-a8fd-f88b9b9212ec
User Message:
Iedere nacht gaan alle apparaten op 'niet beschikbaar'. Een herstart van de app laat ze weer online gaan
---- stdout ----
---- stderr ----
Thanks for checking, there was no update possible everytime I checked, but now it’s updating..! And yes I did a restart after the diagnostic report, but won’t do that the next time then..
But biggest chance is the old app version, I hope that will already fix the problem!
Yeah, a lot has changed and more cpu/memory fixes are coming from the alpha version I am working locally on my homey.
From your comments that all stops at midnight hints to your wifi (mdns / bonjour protocol) problems but that is what based on experience with this app and all the different wifi setups people have.
Ah okayy! But I didn’t change anything on my side with wifi or so, didn’t even update the Homewizard app for months 
And everything worked like a charm this year, until 2 days ago.. Hope the update will keep my devices working again
Yeah I hear you, typical wifi issues where nothing is changed but a sudden reconnect of Homey or HW devices to an other AP makes it crumble. I’ve seen it here myself. New AP or router firmware, reboots the unit, forces AP clients to reconnect elsewhere and see the devices mark unreachable.
For your convenience you can check the fetch tab troubleshooting in app settings.
Homey → settings → apps → Homewizard app → app settings. This will open a new window and contains some tabs to see what is bothering your connections.
Hmm, since the update this morning my Homey is really slow because of the memory usage of the HW app (normally 35mb, now 135mb). The suggested fetch tab isn’t reachable, not on phone and browser. It keeps spinning.
What to do for the memory usage?
e4077a22-f768-4ce3-9404-de5a62127e34
Update: P1, watermeter, two sockets unreachable again, maybe you can see something this time because I won’t restart the app: 697baed1-4dcd-4c88-8c58-d85c340bdfd8
Clearly a wifi issue:
App Version
v3.17.3
Homey Version
v13.2.4
Homey Model ID
homey3s
Homey Model Name
Homey (Early 2019)
Stack Trace
Note: this log has been manually submitted by a user.
Log ID: e4077a22-f768-4ce3-9404-de5a62127e34
User Message:
Enorm geheugengebruik, fetch tab niet te openen
---- stdout ----
2026-08-03T08:53:33.711Z [log] [HomeWizardApp] HomeWizard app ready!
2026-08-03T08:53:35.071Z [log] [HomeWizardApp] ✅ Global error handlers installed
2026-08-03T08:53:37.667Z [log] [ManagerDrivers] [Driver:cloud_watermeter] HomeWizard Cloud Watermeter driver initialized
2026-08-03T08:53:38.520Z [log] [ManagerDrivers] [Driver:cloud_p1] CloudP1Driver has been initialized
2026-08-03T08:53:38.586Z [log] [ManagerDrivers] [Driver:battery-policy] BatteryPolicyDriver initialized
2026-08-03T08:53:38.610Z [log] [ManagerDrivers] [Driver:battery-policy] Flow cards registered
2026-08-03T08:53:44.133Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:a37e4415-2678-450f-a556-90d8663515a2] ⏱️ Polling interval 10s (user: 10s), spread offset 1s (device 1/2)
2026-08-03T08:53:45.172Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:7ab17bc9-0428-440b-8d9f-480a3b776120] ⏱️ Polling interval 10s (user: 10s), spread offset 5s (device 2/2)
2026-08-03T08:53:45.353Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:a37e4415-2678-450f-a556-90d8663515a2] 🚀 First poll starting (after 1s delay)
2026-08-03T08:53:50.179Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:7ab17bc9-0428-440b-8d9f-480a3b776120] 🚀 First poll starting (after 5s delay)
2026-08-03T09:19:59.821Z [log] [ManagerDrivers] [Driver:energy_socket] [Device:7ab17bc9-0428-440b-8d9f-480a3b776120] ❌ Connection lost after 5 failures (556s since last success)
---- stderr ----
2026-08-03T08:58:39.758Z [err] [ManagerDrivers] [Driver:watermeter] [Device:cbe96189-d4ff-4eaf-b08e-946343be5b76] Polling failed: Error: TIMEOUT
at fetchWithTimeout (/includes/utils/fetchWithTimeout.js:35:42)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at runNextTicks (node:internal/process/task_queues:69:3)
at process.processTimers (node:internal/timers:520:9)
at async HomeWizardEnergyWatermeterDevice.onPoll (/drivers/watermeter/device.js:227:19)
2026-08-03T09:00:47.362Z [err] [ManagerDrivers] [Driver:watermeter] [Device:cbe96189-d4ff-4eaf-b08e-946343be5b76] Polling failed: Error: TIMEOUT
at fetchWithTimeout (/includes/utils/fetchWithTimeout.js:35:42)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async HomeWizardEnergyWatermeterDevice.onPoll (/drivers/watermeter/device.js:227:19)
2026-08-03T09:16:48.363Z [err] [ManagerDrivers] [Driver:watermeter] [Device:cbe96189-d4ff-4eaf-b08e-946343be5b76] Polling failed: Error: TIMEOUT
at fetchWithTimeout (/includes/utils/fetchWithTimeout.js:35:42)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at runNextTicks (node:internal/process/task_queues:69:3)
at listOnTimeout (node:internal/timers:549:9)
at process.processTimers (node:internal/timers:523:7)
at async HomeWizardEnergyWatermeterDevice.onPoll (/drivers/watermeter/device.js:227:19)
2026-08-03T09:17:35.117Z [err] [ManagerDrivers] [Driver:watermeter] [Device:cbe96189-d4ff-4eaf-b08e-946343be5b76] Polling failed: Error: TIMEOUT
at fetchWithTimeout (/includes/utils/fetchWithTimeout.js:35:42)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at runNextTicks (node:internal/process/task_queues:69:3)
at process.processTimers (node:internal/timers:520:9)
at async HomeWizardEnergyWatermeterDevice.onPoll (/drivers/watermeter/device.js:227:19)
What to do?
I’ve a unifi network at home, zero issues.
Only the ‘Droger’ and ‘Wasmachine’ sockets are losing their wifi sometimes because of their bad location hided behind the devices, but for me and the HW app this is never a problem.
The P1 and watermeter are the important ones for me, and they never loose connection. In the Unifi network portal I see that there are no disconnections or other mutations for the P1 and Watermeter the last 24h so they’re steady on the wifi.
Then it is your homey struggling to keep wifi stable somehow. The log shows it fails to reach your watermeter and energy sockets (ie timeout / unreachable). Maybe focus on that one first?
Homey connection is stable as always too.. Locked to his own 2.4ghz AP and no issues the last 24 hours.
It looks for me like a kind of polling issue from the HW app, it’s checking the connection really often and for the Wasmachine and Droger it won’t find that stable connection? Would that be something? On the other hand: it worked for months on my february app version, nothing changed but the HW app starts to set the devices as unreachable since 2 days,..
