You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a HUE GU10 bulb running in HA successfully for weeks as I am testing out moving the rest of my bulbs off of the bridge.
All of a sudden, that one bulb went offline in HA. It has always been available in Z2M and is fully controllable in Z2M. But in HA, the device reports unavailable. All my other Zigbee devices are online and accessible in Z2M and HA. Just this one bulb.
I deleted the bulb from Z2M and went through resetting the bulb and re-pairing it. Once the re-pairing was completed, I re-named the bulb in Z2M with the option to rename in HA enabled. It showed up in HA but immediately went unavailable again.
I found one post here that mentioned the same behaviour, but they weren't sure what they did that fixed the problem. I tried the same thing they did, reconfiguring the broker's address. But that made no difference in my case.
I'm a newbie, so If there are logs I can post here, I'd just need some direction as to where those are found.
Has anyone else run into this and figured out the fix?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I had a HUE GU10 bulb running in HA successfully for weeks as I am testing out moving the rest of my bulbs off of the bridge.
All of a sudden, that one bulb went offline in HA. It has always been available in Z2M and is fully controllable in Z2M. But in HA, the device reports unavailable. All my other Zigbee devices are online and accessible in Z2M and HA. Just this one bulb.
I deleted the bulb from Z2M and went through resetting the bulb and re-pairing it. Once the re-pairing was completed, I re-named the bulb in Z2M with the option to rename in HA enabled. It showed up in HA but immediately went unavailable again.
I found one post here that mentioned the same behaviour, but they weren't sure what they did that fixed the problem. I tried the same thing they did, reconfiguring the broker's address. But that made no difference in my case.
I'm a newbie, so If there are logs I can post here, I'd just need some direction as to where those are found.
Has anyone else run into this and figured out the fix?
Beta Was this translation helpful? Give feedback.
All reactions