the correct ip for the wrong kwh meter is 192.168.1.9
the .40 is for the airco which seems to work ok
Update in settings of the device. But something went wrong during pairing
Changed URl from http://192.168.1.40:80/api/v1 to http://192.168.1.9:80/api/v1
After refresh it is still http://192.168.1.40:80/api/v1
I figured both are recognised as one.
I deleted both.
Restarted Homey.
Add new device → choosed homewizard →choosed kwh meter 1 phase P1→ Nothing found → choosed kwh meter 1 phase → nothing found → pressed continu. Then the wizard found the 2 meters. Added them.
The issue is gone.
Thank you for the advice. As I can figure out the issue started in the end of oktober
Always a bit tricky duplicate devices to add in the same time. I added serial number in the discovered name but still hard. Good to hear it is resolved now.
Hello,
Don’t know this is the right place.
But is miss the option, if say for temp sensor, temp or hydro is not changed for periode X like 1h, Day, 1 week to see if sensor is properly working or not so I al an alert to it.
Regards Raymond
You can do this with flows and variables.
This is my fridge check flow every 6 hours but you can adjust that as you wish.
v3.9.20 now live
Hi Jeroen, after the last update I still get the error "Cannot read properties of undefined (reading ‘log’). Now I cannot install the Homewizard P1apiV2 and both my batteries. Please help
Drop me a diagnostic
342fd0fb-a07c-4714-af4e-738e88c34852
Thanks for the quick reply!
Try this fix:
It works!!! Thank you Jeroen! Much appreciated!
1 Like
Good, I juggled to get log a bit more meaningful so it is easier troubleshooting but some of the code are context related and not valid. So restored and older working version.
Edit 30dec: Fix now live for everyone
It seems to have resolved the issue for the KWH meter, the P1 still requires a reboot. It does the mDNS discovery fine afterwards but looks like it might not use the fallback correctly yet? This was still on 3.9.20 - just installed 3.9.21
I am moving to a Unifi cloud gateway from a Fortigate soon, hopefully the mDNS issue itself will then be resolved. I still do not understand why all mDNS devices keep working fine but only the HW hardware works within 1-2 hours after a restart and then they disappear on mDNS cross vlans….
Sorry not familiar with Fortinet as customer. I can only relate to them as business and monitoring tooling.
Somewhere multicast broadcast is stopped or IGMP snooping is acting differently.
Received 3.9.21
Since then, no more actual readings from thermometers etc.
Early 2019
Drop me a diagnostic please
b293628e-1569-43d6-a588-cb63994385a6
Done!
Thank you, I see the problem. I will fix later this evening.
Fixed try:
