I don’t think it is the Homey update that causes this, although it was probably what triggered it.
The app is depending upon the mDNS features of the Homey Pro to detect the availability of devices. Somehow the Dyson device is not detectable to the Homey Pro and unplugging the Dyson device seems to trigger it to reinitiate the required mDNS traffic.
I have an hypothesis as to why the official Dyson app does not lose connection, as they probably built it so it staticly stores the IP-address of the Dyson device when it is added. This makes the connection independent from any kind of network detection. However this also causes the device to be not found if the ip address is more dynamic (which is as far as i know a known issue with the official app).
When I have time i’ll see if i can combine the two methods to make the connection more resilient both when ip configuration changes and when mDNS detection isn’t reliable.
