Can this issue be fixed?
Every time after a update one or more devices are not responding. I know that a reset of the wifi network will fix this, but this not a solution. It is possible to store the connected IP address in the app devices for reconnecting. So there is less mDNS involvement to reconnect.
As you can see in the screenshot all HW devices are seen in mDNS.
I hope you can put some effort in it to fix this for a lot of users that are also having this issue.
Hi Jeroen, i am tweeking a load balancing flow for my EV-charger. Today i have the update off your great app. But i think ther is now missing a translation. See picture 
No rush, yust for information
Strange, sounds like your Homey is unable to process all mdns updates from the network.
If the records are there then you Homey should pick them up. Have you raised this with Athom support? Is this with the Homey Pro 2023 or the older one?
And what error message do you see in the device cards met the ! sign?
Yeah was a rush job. Back from holiday and all my free time got claimed.
No problems any longer after the update to V3.6.63
Thanks for confirming that. I’ll keep this version for a while.
test/beta
v3.6.66
NOTE: First time running this version might fail on some HW devices as the url setting is still empty so it should improve on wards.
Hello Jeroen,
ik have several product from homewizzard.
Also 2x 3fase meters.
One of them i got the message “apparaat onbeschikbaar” (not availeble), but at insight i get data.
so flows working.
sinds a few day’s (i think after i restarted the app at homey) i not get data alswel.
This is the second time i have this problem with the 3fase meter.
After the first time i added the 3fase meter again to homey.
The original app from homeassistent works normal.
ofcourse i cloud add the meter again (after delete), but i think i get this problem again.
I’ve added extra code to “hopefully” bypass this issue which is general is a poor wifi connection with flaws in mDNS. Get the test version that I made available earlier. It probably fail on first start but should be ok after the restarts onwards. Please let me know.
Its a bit frustrating that I ask questions by other users on earlier concerns and not get feedback. I do my best here but I can’t fix peoples poor wifi or work magic.
i understand, my wifi is perfect i have 5 ap’s everywhere, and the PIB’s (3x) and 3fase and 1fase meter is 1m away from one of the ap’s 
Fine, mDNS also involves your router, and DNS (internal?).
Local domain isnt .local ?
VLAN’s? IOT? (proxy mdns/relay/repeater).
mDNS used is same as Apple bonjour protocol, no issues there?
Known issues with vendor wifi and Apple devices (bonjour)?
At my wifi u see 5 homewizzard devices the only one wat not working (till i reinstall it) is the “HW-pv-woning” that is the 3fase meter.
Routing is for all devices the same.
The second 3fase meter is at the garage (other AP) that one works fine is als a newer model 3fase meter.
Forcing a disconnect from your AP is enough. No need to reinstall.
done that, disconnected from the ap, but directly connect again.
after i shutdown the ap wifi, so all the devices connect to a other ap.
only the 3fase gives a not available
Does it appear in the mDNS browser/discovery app (see first post in this topic)
Not at home, and remote i can’t use mDNS
Ok at home.
Started mDNS and i see the 3fase meter who not working at my Homey.
But the 3fase at the other room i cant find but it is working
With the homewizzard app i reconnect it to my wifi, and not its is working again.
Everything works now again, strange.
Edit:
Looked at the Energy tcp there the where all of them
Which confirms my struggle to support it from my end.
It’s just frankly impossible to answer/fix these all different wifi issues and usage if mDNS/multicast troubles on those wifi connections.
THats the difference between APIv1 and APIv2.
_homewizard._tcp is APIv2 (p1, battery and kwh meters).
_hwenergy._tcp is APIv1 (also those as they support both and the watermeter is only APIv1 based)
Ok.
But everything seems t work again with Homey
Homewizzard was Always fine
