English here please as this is the English section so non Dutch people understand as well. Thx 
1 Like
@Jeroen_Tebbens a PTP is the clue! Thanks a lot. Now I added the watermeter. You are the second best 
#prettigweekend
1 Like
No problem 
Hi Jeroen, yes sorry about that. So restarting the driver in Homey pro and switching on the local api in the app did it. Thanks for the support!
1 Like
v3.2.9 is live
Should be fixed in v3.2.5 and later
Hello, as of yesterday afternoon, the moment my HomeWizard app upgraded to 3.2.9 I lost connection to my P1 and Energymeters.
Have checked:
- Soft restart of app, soft restart Homey. PtP, waited 10 minutes, power on and restart of the P1 and energymeters
- JSON read from Homey to local API of P1 and Energy meter : working
- Multicast Homey, P1 meter and Energy socket showing in network trace : working
- Homey Pro (Early 2019) 8.1.5
- Diag report : 6ccb0543-f273-4757-bf4b-5ca6bdc87757
Any help or suggestion is welcome!
Can’t see any device at all. Did you restart the app after troubleshooting as the log is empty so have no clue at this moment.
---- 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 ----
Thanks @Jeroen_Tebbens for your quick response. I did reboot the app about half an hour before I posted the initial message. Now I’ve only ptp’d the P1 meter and Energy meters and consumed energy. Still all devices show as unavailable in the app. (I do see them in the Developers Console and ID’s match the serial number I see in the multicast)
New diag : 626b9092-056e-4306-84a2-02e46fc24191
Still nothing, same output. I’ve updated my early2016 to 8.1.5 today and all fine. I feel it is mdns of Homey itself or wifi accesspoint related.
What are you using as wifi accesspoints? Anything changed there? Are ip addresses for the p1 and sockets static as well?
Using Fortinet over here, already checked multicasts and see them on local clients in same network and checked in logs and see them also forwarded to the Homey. I don’t know how to Wireshark in Homey (if even possible) to double check.
Devices have DHCP enabled but get same addresses assigned by DHCP, devices are still available for my HTTP Request Flowcharts I’ve got running on Homey.
No changes on the network. The notification on the timeline for the 3.2.9 update is at 12:30 yesterday, checked in the Homey Insights and 12:30 is the last moment the devices did report any updates of the meters. The last couldn’t be coincidence
Not a fan, because I need to rework quite some flows, but deleting a device and adding again is that worth a try? (Tried adding new device but then the app reports that there’s no new devices)
Same ssid? Or different vlan (IoT network), proxy/mdns repeater involved in your fortinet?
No guest ssid/vlan that potentially can filter on the client end point?
You can try to just unplug a socket or p1 to allow the socket or p1 to start the mdns announcement process again. Else something new in 8.1.5 has been introduced as v3.2.9 code change were legacy homewizard code only and nothing on p1 or sockete compared to v3.2.5 (previous stable).
I added a new socket myself today (bought 3 new sockets). Firmware 8.1.5 and v3.2.9 works fine here (unifi wifi + opnsense firewall + mdns repeater plugin).
Hi, first of all thanks for helping! Homey and sockets are on the same WifiSSID/VLAN as they’re both IoT, MDNS forwarding to other network segments is enabled for other media devices. As a test added the Energy Sockets to forward to all interfaces and now also receive the announcements in other networks if I unplug and plug.
Did a couple of Wiresharks on the FortiGate and local machines and the broadcast is always visible.
Is there any way to do TCP Dump or Wireshark in Homey?
No, havent found a way to whireshark it, maybe the new HomeyPro2023 can but not sure. Problem with whireshark is you need root access to the wifi driver to pcap traffic. Not sure if there are mirror/spam port options in the fortinet wifi’s.
Is there any mesh wifi between AP’s locally?
Honestly I am running out of options here. Homey fails to see or use Multicast dns via wifi from what I can understand from your logs or derive from the steps you took. Am afraid this will be an issue for Athom Support as I have no issues.
OK thx. Yes I can monitor on the WIFI Interface, there I still see the mdns. Just tried to delete one of my EnergySockets and that’s now gone in the config but also not showing when trying to add as new device.
Indeed looks like a MDNS issue here
I had the same issue. After toggling the local API in the HW app (not the Homey one) and restarting the HW app in Homey solved the issue for me.
Thanks! Tried but didn’t solve it here. (just to be sure: open HW APP, go to the devices and just toggle off/on the local API for all devices, then in Homey restart the HW app?)
