Not working for my p1 meter.
Says “fetch is not a function”.
Which version? Test I just released?
Latest version… since this morning. Restarted the app a few times.
Hi, the update this morning version 3.8.4, my p1 and rail device (kWh Meter) stopped working. Error “fetch is not a function”. Restarted Homey, restarted the app, reconnected the devices on my wifi, did not help. Like @AJ_Roovers
Read up, yes I am aware.
You are probably on a Homey 2016-2019
That’s right, I’m on a 2019. I just tried the exp 2.8.6 version, and that did not work either, same error message.
Early 2019
Sorry, still the same with the test version.
Rolling back to node-fetch module in v3.6.7 so the old Homeys should work again.
I’ve been using this app for nearly a year now. It was working perfect. Since the update from this morning several values are not updated anymore:
Power and current values per phase are not updated anymore.
All other values (total power, counters) still work.
I’m using a Homey Pro early 2023. Updating the P1 dongle (now software version 6.0206) and restarting the app didn’t work.
Added:
Current of phase 1 does update. Current of phase 2 and 3 don’t. Power of phase 1, 2 and 3 don’t update.
This is the same for version 3.8.4 and test version 3.8.7.
Yes. Current test version works. Thanks.
Good, I will be happy when 12.9.x will be stable for all devices…
With the last update, everything is working again. Tnx 
Thank you for confirming this. One error found for a user with a SDM230 in P1 mode to resolve/test. When that is sorted I will push it to public/stable.
Still not working. Items from HomeWizard itself are not actual, too. Thermometer, door-sensor, smoke-detector…
Can I force myself to go back to older versions?
Share diagnostic, need to see what goes wrong.
Done. Do you need the code?
No found it, your problem should be solved in v3.8.8 that I put public now as that is the same as other users.
Thnx. Everything ok now.
No problem, wasn’t sure if you had issues with the test version as well.
But the report showed the last public which had the fetch issue.
I rolled back the functionality so it should be resolved now.
