Restart your Homey2019
Restart did not solved the issue… still not available. Thanks for your support
Only P1 gasmeter code changed so nothing with kWh for several months, sorry. My kWh-1 is fine as well. mDNS can be annoying in rare cases of WiFi or routers to relay multicast traffic. Next suggestion would be to restart the access point that both Homey and your kWh connect to.
Homey has no clue about your kWh so that supports my thought:
User Message:
Lost connectivity of the 3phase meter. Connectivity in the HW App is working. API toggle on/off and resting the app does not help.
---- stdout ----
HomeWizard app ready!
HomeWizard has been inited
HomeWizard Heatlink has been inited
HomeWizard EnergyLink has been inited
HomeWizard Thermometer has been inited
HomeWizard Kakusensors has been inited
HomeWizard Windmeter has been inited
HomeWizard Wattcher has been inited
HomeWizard Rainmeter has been inited
---- stderr ----
restart of the access point worked. Thanks a lot for your support and have a nice weekend 
Are the new energy sockets working ?
Yes, just make sure you enable local api on all of them.
Sorry this is the english section. Please make sure Local API is enabled again in Homewizard Energy app. If that is enabled please reboot your wifi accesspoint that connects your Homey and your watermeter.
Is it possible to connect these with the homewizard app, without any homewizard hubs?
No you need the Homewizard hub. The 868Mhz protocol is protected/locked so there is no alternative sadly.
Okay, no problem. At least i know i didn’t something wrong 
Ate those sockets working without a hub ?
Yes those recent sockets Homewizard released last 2 years and the new “slim” model version work without a hub. They all have their own wifi chip.
thanks
Hi!
I’m sorry, I did something backwards. I sent a diagnostics report with a suggestion for an improvement, 08b9a7af-0a20-402b-825c-240f154ec798.
In short; a device refresh/reconfiguration, when local ip address has changed would be very useful to have. At least for us with a Netgear (and possibly other) routers that cannot clear its arp cache, and release/renew ip address to p1meters that calculated a new anonymized mac address after firmware upgrade, and got a new ip address from router. Even if I change the old reservation, it won’t release and pick that ip, over the new one. So if Homewizard app could refresh its configuration based on mdns data (it remembers the meter id, right?), then I won’t have to re-configure all flow cards manually, and loose all Insight history every now and then…
Hi, this is already covered in my code and here in action for example a watermeter:
2024-06-04T13:54:47.396Z [log] [ManagerDrivers] [Driver:watermeter] [Device:838fe2d1-c6d6-4bf8-b706-510b2929a8c6] URL: http://192.168.2.17:80/api/v1
2024-06-07T08:31:31.362Z [log] [ManagerDrivers] [Driver:watermeter] [Device:838fe2d1-c6d6-4bf8-b706-510b2929a8c6] URL: http://192.168.1.252:80/api/v1
2024-06-07T08:31:31.362Z [log] [ManagerDrivers] [Driver:watermeter] [Device:838fe2d1-c6d6-4bf8-b706-510b2929a8c6] onDiscoveryAddressChanged
2024-06-07T08:31:31.363Z [log] [ManagerDrivers] [Driver:watermeter] [Device:838fe2d1-c6d6-4bf8-b706-510b2929a8c6] URL: http://192.168.1.252:80/api/v1
2024-06-07T16:50:46.201Z [log] [ManagerDrivers] [Driver:watermeter] [Device:838fe2d1-c6d6-4bf8-b706-510b2929a8c6] URL: http://192.168.1.252:80/api/v1
Jeroen,
Thanks. Why do I run into a problem then, when my p1meter is changing mac/ip? Is there something I should do somewhere to make it work?
I am running v3.3.11
Thanks,
Niklas
I really dont know. I dont have netgear myself so can’t relate.
Multicast DNS can be magic but also a pain in the BEEEEEP. As per topic start post I suggest to reserve the address for your P1 to avoid this problem.
What my might help is checking on your end when it changes to compare the output from an mDNS browser app with the before and after and see if it triggers the “onDiscoveryAddressChanged” trigger in my code.
It is just like zigbee or zwave, every vendor has their own view how it should work but yet are deviating from what it should do to be compatible to all zigbee or zwave standards.
Same as mDNS, vendors support it but it’s how it is compatible with all to make it work.
Ok, thanks.
I’ll investigate further. Perhaps it’s soon time to retire this Netgear router… maybe Ubiquity will be a better option…
