I’m restructuring my LAN at home right now, grouping different device types onto different VLANs. I want to move my ST hub and Philips Hue hub to a VLAN dedicated to IoT devices, but am concerned about how to get ST to recognize the IP of the Hue hub after the move.
I already ran into this issue when swapping out my router, as the Hue hub obtained a new IP address at the time, and the only way I could get it working again was to statically assign the old IP that the ST hub was looking for.
Is there any way to update / force ST to find the Hue hub again after making this move? Without completely removing and re-adding the Hue hub and all of the attached bulbs?
Strange… I recently upgraded my entire network to Ubiquity’s Unifi equipment and reorganized all static IPs, including the ST hub and the HUE hub. I did not have any issues with either one changing their IPs (statically assigned) and I did not do anything (intentionally at least) to make it work.
Just in case it matters, I have a v2 ST hub and I no longer use any SmartApps to add support for Hue lights as the ST hub can find them on its own.
On this point, do you mean you paired the Hue bulbs with ST, or that ST can easily find the bulbs attached to the Hue hub on its own?
Hah, that’s exactly what I’m in the middle of. Got everything else pretty much done, just shifting things around onto their own VLANs now… So when you changed your network, did you not assign static IPs for the ST and/or Hue hubs, or you mean it didn’t have any issue handling it after the IPs were changed?
Seemed like ST couldn’t send any commands to my Hue hub when the Hue IP changed… And looking at the setup in the IDE, I couldn’t see the Hue IP changing from the original address (x.x.x.108)… Seemed like it only started working again once I put the Hue hub back on that x.x.x.108 address again.
@talz13 - I used to have a Hue “Connect” smartapp that added my bulbs to ST but at some point ST introduced the “Super LAN Connect” which allowed me to uninstall the app. The bulbs are still connected to the Hue hub… uhm… box… uhm bridge (that was for you @JDRoberts … BUT you are RIGHT). When I moved devices around to other IPs, I do not recall doing anything to get everything back up and running. If I did it was likely by pure coincidence.
One thing I did NOT do was assign different VLANs. I wonder if you have introduced an issue there where the ST hub can’t ‘see/talk to’ the Hue bridge.
To keep things organized I decided to reserve the first 15 IP addresses x.x.x.1-15 for my dozen Unifi networking devices so the ST Hub and Hue bridge that were assigned to .4 and .5 got pushed out beyond x.x.x.15. I power cycled the devices and they soon picked up the new IP. I really do not recall doing anything more to restore functionality.
Maybe the only thing I did do what check things out here:
In the new world (after groovy) I had this issue and was able to resolve it by changing the driver on the hue bridge to something random, then back to the hue bridge driver using the advanced web UI (Samsung account).
… BUT you are RIGHT). When I moved devices around to other IPs, I do not recall doing anything to get everything back up and running. If I did it was likely by pure coincidence.
