You aren’t using this driver. You are most likely using the SmartThings implementation for Hue. Don’t use the Hue branded method for adding devices. Just “Scan Nearby” and don’t press the link button on the Hue hub.
Thanks for getting back to me.
I don’t have Hue linked via the official way.
To add, I followed your link, enrolled my hub and install the Hue Beta driver. I think pressed Scan Nearby on SmartThings and pressed the pair button on the Hue hub. It pulled through my Hub and all lights but doesn’t allow me to see the features you can see on the hub, linked button etc.
I’m using the Smartthings hub that is build into my TV, I had to unplug my Smartthings Dongle (ZigBee) as with this plugged in, the driver caused my hub to not respond.
Don’t do this. It is isn’t needed and will trigger the ST implementation to find the device. Just scan for it and make sure it on the same network. Linking is done later in the setup after the device is added.
1 Like
Thanks, will try this today.
Any idea on why the hub stood responding once I put the ZigBee single back in?
So. I’ve uninstalled the driver and unenrolled my hub. I’ve removed all Hue devices from my ST hub.
Starting from scratch. I have enrolled my ST hub. I have installed the driver. I am now trying to “Scan for devices” with my ST hub but it isn’t picking anything up.
I’ve waited about an hour or so.
I’m I missing something or doing something wrong?
It’s possible that the TV hub is incompatible. Maybe @JDRoberts can comment on Edge compatibility without a physical hub.
@blueyetisoftware I have an issue that started some time on 4/25 but I didn’t notice until last night. I noticed that rooms and zones are not updating in the ST app (I don’t have Hue lights on this driver) unless I manually refresh them. I can turn a room or zones on/off from the ST app okay. I then took a look at my motion sensor history and noticed it has stopped updating. This is happening for both my Hue bridges.
I’m not seeing any errors in the logs.
Any ideas? Is anyone else seeing the same?
Note, this appears to be the very same thing that is happening on the Meross integration.
I am not seeing anything like this and the event stream seems to still be working. Based on the commands working, and the sync not working, it sounds like your event stream is down. It should restart automatically though.
Can you look for something like this in your logs:
2023-04-27...... DEBUG Philips Hue Dev onmessage 1111111111:0
It will normally be followed by messages about emitting events:
2023-04-27...... INFO Philips Hue Dev <Device: XXXXXX (My Light)> emitting event: {"attribute_id":"switch","capability_id":"switch","component_id":"main","state":{"value":"off"}}
I’ve been watching the logs on and off while this issue has persisted. But I gave it another look just now. I started the logs, switched a zone on in the Hue app, the physical lights came on all okay (as do the ST light devices in ST via DTH), the zone device in ST does not update and nothing appeared in logcat for that event. I just get this as it does its update:
2023-04-27T02:44:22.417384069+00:00 DEBUG Philips Hue Beta [200/OK] https://192.168.254.87:443 GET /api/0/config
2023-04-27T02:44:22.421201518+00:00 DEBUG Philips Hue Beta Hue Bridge device thread event handled
2023-04-27T02:44:23.515903846+00:00 DEBUG Philips Hue Beta [200/OK] https://192.168.254.89:443 GET /api/0/config
2023-04-27T02:44:23.522412849+00:00 DEBUG Philips Hue Beta Hue Bridge - MR device thread event handled
1 Like
This morning I tried a driver reinstall. That did not resolve it. I then rebooted the ST hub and that has fixed it.
2 Likes
These event sockets utilize file descriptors on the ST hub. It is possible that it was somehow corrupted or ST reclaimed it for something else. Restart of the ST hub makes sense, as it causes everything to be reinitialized. I was going to suggest one more thing to force it to reconnect, but I’m glad you have it running again. I will review the logic in the driver to see if there is anything else I can do to handle this sort of scenario.
2 Likes
I had a power outage yesterday and after that had the same issue, no report back from sensors and lights, just reading the last posts and I rebooted the SmartThings Hub, just after that they start to get info again, not sure if the power outage had something to do or not…
2 Likes
Maybe of interest (or maybe not 
), although I do not think I have seen this issue with Hue and this driver recently I have with the stock Sonos LAN driver.
It keeps loosing Sonos → ST communications. Initially perfectly happy switching on, announcing ect. but fails to update in ST and then looses connection in both directions shortly afterwards. Hub reboot and all is well again.
This has been happening for a couple of weeks now, maybe 5/6 times.
Stable network with all software upto date on a UK v2 hub.
Wondering if the 47.11 update changed something as, initially, that caused all my LAN devices (Hue, Sonos, Harmony, UPnP) to drop off… Reboots across the board on that occasion…
Just a thought 
1 Like
Same situation with Edge Drive for Bose
I have been watching those other threads as well. Both of my LAN drivers are experiencing this to some degree. Something does seem to have changed, but I haven’t narrowed it down. It could be something as simple as a response code being changed in the ST platform, so I just need to find a way to reproduce it. If I can, I’m fairly certain there is a workaround.
2 Likes
OK, I finally got all my old Zwave removed and a new one added, and coming back to handle the Hue. I installed the drivers and notices items on its from the previous native drivers used by SmartThing. I was thinking of the following, and would like some inputs before moving forward
-
Power off the bridges, and remove all Philips bridges within ST to get a fresh start (as I renamed the bridges and move some bulbs around). When I remove the bridges, would any of the remaining blubs in ST get remove also when its associated bridges get deleted?
-
Once ST is all clean up, would it be easier to add in one bridges at a time, as I have 9 active right now, and will end up with 12 total.
-
Is there anything I need to do to add in a bridges (enter hue account info, or click on the top button on the bridge), or just a simple discovery process without any interaction?
-
If I understand you correctly, once the bridge is discovered and added to ST, all the bulbs and its name that are associated with the bridge will come over also? How does the mapping work between Hue and ST? As all the bulbs are grouped within a room inside the Hue App. Assuming I have the same room names, “Master Bedroom” on the Hue App, “Master Bedroom” on ST, the bulbs should drop in “Master Bedroom” on ST without addition interaction?
Sorry for the long list of questions but just want to get as much insight as possible
dwc
That step is up to you. It isn’t required by the driver and you can leave it if you want. You’ll just have duplicates.
When you run discovery, it will add all of the bridges on the network.
Don’t do anything other than run discovery to add the bridges. Everything else is added from you bridge device. I suggest watching the video in the top post.
No. It doesn’t add these automatically. You should watch the video.
No. ST drops them where it wants. Normally this is either in the same room as your ST hub or in a room called “No room assigned”
1 Like
OK, I am using version 2023-04-18 and followed the direction provided by the video. I also deleted all prior bridges from ST, and cleaned up all Hue bulbs/room on Alexa.
I was able to add the bridge by using.
Add device → scan for nearby devices, and then the new bridge shows up (with only ONE bridge power-on, figure easier to start).
However, upon the new bridge showing up on ST, when I click on the end, I notices two issues
- On the bottom of page, it say “This device hasn’t updated all of its status information yet. Check again later” I Didn’t think much as I saw the same thing in the video
- However, the “Hub Link”, is greyed out. I am not seeing the “Not Linked” status as I see on the video.
Any feedback would be appreciated
dwc
Same as above here. Any clue’s?