Discovery Issues

[jltnol]

So I'm still having some problems with Lifx Discovery. In the end, I'm at the point where I think this is a local network issue rather than something wrong with the plugin. In short, my router is running Tomato firmware, and I have UniFi AP's, with a dedicated UniFi iOT network. Some devices show up and work fine, but some don't. ALL lights are seen by the iOS app, and can be controlled from the app, so they are all on the local network.

I took the time to grab a spare router, set it up with a different built in WiFi network, got the problem devices connected to this WiFi network, and then created a new Indigo Database. Under this setup, the Discovery process is able to find the lights that are otherwise problematic, and can easily be added and controlled by Indigo.

I know enough about networking but far from everything, so am guessing there is something in the UniFi settings causing my problems, but wouldn't have the faintest idea of what to check or change. I have deleted my primary UniFi IoT network, and created a new UniFi IoT network, but basically have the same results.

So, for my own education:

Once a Lifx light is included into a Indigo database, does something happen to the light itself that binds, ties, or otherwise connects the light only to that Indigo database and prevents it from being added to a different Indigo database?

Regardless of the answer, if my primary Indigo setup is shut down, will lights that are part of my primary database(that is off) be discoverable in a 2nd, new Indigo database?

And is either the MAC address or the IP address of Lifix devices permanently stored somewhere in Indigo or the plugin that might be creating issues... ?

just pulling other the rest of my hair.....

[autolog]

Thanks for the further detail on the issue you are experiencing.

LIFX Lights can be accessed from multiple Indigo systems at the same time. I can do this from my Development and Production Indigo systems.
The LIFX plugin stores the MAC and IP Address of the LIFX light in the associated Indigo device. This means that if a future discovery fails, the light can still be potentially accessed by the plugin using the stored details. The fact that you were previously able to do this suggested that it was the discovery process itself that was not working. The discovery does use the UDP protocol to discover the LIFX lights. So a firewall, or similar, could be blocking this.

Anyway, I done some further investigation and it looks like the plugin was restricted to finding LIFX Lamps in the 192.168.0.x and 192.168.1.x range. I looked at the latest LIFXLan library discovery code which is much more generalised and have ported that to the plugin.

I have tested this change and it works but my lamps are in the 192.168.1 range.

Not sure if this is the issue you have but it could be if your LIFX lights aren't in the 192.168... range?

Give the new pre-release version a whirl and let me know if it sorts out the issue: LIFX Controller V2025.1.0

[jltnol]

So oddly enough, my main network is in the 192.168.7.x range, so I think that may have been part of the problem. Not at all sure how or why they would have been "discovered" previously, but it's been so long ago I honesty don't remember having a problem.

Regardless, the updated plugin worked perfectly. I had to shut down the lights for a few minutes, but once they came up, and I reloaded the plugin... ALL are back!

Thank you so much for taking the time to look into this. Based on my tests, I was pretty sure the issue was something with my network, as I've had problems with UniFi AP's and Lifix before. In the interim, I put all the Lifx on an old Apple Airport, as that would have removed the UniFi issue from the equation. May try to move one back to UniFi as a test to see how that goes before moving them all over.

Again...THANK YOU for getting this to work again!!

[autolog]

Thanks for letting me know and I am pleased you are back up and running again.