Ah, this probably explains a lot of the issues then…
If it’s based on IP address then we all probably need to assign static DHCP routing to these devices too?
Surprised this hasn’t been an issue for more people!
Also, just to add, not criticising your coding at all - appreciate all the work on the app - just really really frustrated as I’ve been through my 30 odd flows twice now only for the devices to disconnect and be b0rked again!
Edit: @Phuturist is there any way for me to update the IP address of the device? (maybe even via CLI?) to save me having to redo all my flows again!?
Edit2: Also, can you tell me how I can add these devices now? I have tried to add them again via the devices and even after having removed the old one it’s not finding the bulbs (LAN mode is on…)
The IP is currently saved in the data object of the device. I dont think it’s possible to edit/update this any other way than with a Homey app. Seeying the issues you are having I will move this to the settings object and make it available for editing under the device settings. But that’s of no use to you right now.
Try restarting the app after removing the bulb before doing a new discovery. That should clean any temporary data which can cause the light to not be discovered.
I tried all the methods to find the token of the bridge, without success (1, 2, 3 …) and I realized that there was more simple: ( Activate the mode develloper)
I’ve had no issues getting Sonoff or any other devices to communicate this way, and having Homey on the different subnet is important for the security functions I use it for…
By the looks of it you could hardcode your subnet into the discovery function to have it look in that specific subnet. For this you would need to fork my repo and add it yourself in /lib/yeelight.js.
I did find out that it could also be a router setting and I have also added a specific command to could fix it as well. Could you try a CLI install and see if that fixes the issue already.
So, sorry to follow up on this, know I’m dominating the thread here, but wanted to let you know I have actually centralised my system with the mesh network doing all of the routing now so there is only one subnet being used for all devices… after resetting all my Yeelights once more (due to a new wifi change) fingers crossed everything seems to be working as hoped now
Thanks for the troubleshooting help - not sure we ‘fixed’ the actual issue but it’s certainly now fixed in my setup via simplification
Been experimenting a bit and it seems it works, so long as the light isn’t at 0% when you start it…
Therefore, if you’re dimming, it works as expected. If you’re trying to wake up, you need an additional card setting the light to 1% brightness before you kick it off!