Ran into a weird glitch with echo, and just wanted to pass along a workaround in case anyone else is seeing it. I have reported it to support as well.
I have a hue bridge with two hue lux bulbs and five GE link bulbs attached to it. In the Hue native app these are all described as Lux bulbs, but they actually have different behaviors.
A couple of months ago, I had successfully discovered this bridge with echo, and was using it for light control, and everything worked great.
When I added smartthings as a service to echo, I did not authorize the same hue bridge. I just left the Hue bridge with its native connection to echo, and only authorized devices for smartthings that were not already known to echo through other services.
So far, so good. However, for various reasons I ended up having to do a new discovery of the hue bridge from SmartThings. And that’s when things got weird.
DISCOVERING THE HUE BRIDGE FROM SMARTTHINGS WORKED FINE FROM THE ST SIDE, BUT THE HUE BRIDGE THEN DECIDED ALL GE LINK BULBS WERE OFFLINE SO ECHO COULDN’T USE THEM ANYMORE
After I did the discovery of the Hue bridge in the smartthings mobile app, the following things happen:
The smartthings mobile app could toggle all the bulbs connected to the Hue bridge on and off, no problem. However, if I unplugged the Hue bridge, ST could no longer toggle the bulbs, so it wasn’t that ST stole the bulbs.
both the Hue native app and the echo app thought all the GE link bulbs were off-line. However, they could still control the Lux bulbs.
So ST could use the Hue bridge to control the GE link bulbs, but the Hue native app could not, and neither could echo. Like I said, weird.
What you get the situation where the hue app thinks the GE links are off-line, but the smartthings app can control them, the workaround is annoying but simple.
Just cut current to each orphaned bulb and turn it back on. If you have dumb switches, you just flip the switch on and off. You only have to do this once, you are not re-pairing the bulbs or healing the network. Just getting the already identified bulb to say hello to the bridge once.
After that, the Hue bridge will identify the GE link bulb as being online, therefore echo will also be able to control it, and smartthings will also still be able to control it.
Why this problem only occurs with the GE links and not the Hue lux bulbs, I have no idea. The weirdest part of the whole thing is that the ST mobile app can still turn the bulbs on and off using the hue bridge, even though the bridge itself thinks the bulbs are off-line.
Obviously the Hue bridge/GE link integration isn’t perfect.
But I just wanted to mention this in case anyone else is having a problem with echo not being able to control certain bulbs because the Hue bridge thinks they are off-line after smartthings has done its own separate discovery of the hue bridge.
@juano2310 any thoughts? Or is this just a case of “too many cooks spoil the broth” and it’s the Hue/GE link integration that’s fragile?