[ST Edge] Philips Hue LAN [BETA] (3rd Party Driver, Not ST Native)

Thanks, just tried to re-link the Hue bridge to the ST hub within the ST app. Other things I’ve tried is rebooting the Hue bridge, rebooting the ST hub, and using a brand new button. Same issue persists. The switch / button is found by ST no problem, and it even shows the right battery level, same as in the Hue app. However ST doesn’t pick up button presses of any kind.

Edit - I ended up removing all switches and sensors from that particular hue hub, removing the hue hub from ST, and then reconnecting and resetting everything up one by one. Didn’t take long as I didn’t remove lights / light scenes. But I did need to set up all my button commands in Hue all over again. That has worked, ST now sees button presses. Not sure which step solved it, but if anyone has the same issue, then go nuclear, remove everything, and set it up.

1 Like

Not sure what this means. Can you elaborate?

I wouldn’t recommend this :slight_smile:

Since everything got nuked, the logs will not provide any answers. Glad you are working again though.

Ah sorry should have waited! Thanks for responding.

By the top point, I mean I logged into the advanced web interface of ST, went into the Hue Bridge device, went to Commands, and clicked “discover”. I’ve since realised that you can do this directly in the app, but I believe there was a period of time when you had to do it in the web interface, so that was my first go-to approach.

Hi. The same thing has happened again. It worked for a week or so, but now ST is not seeing button presses on my Hue remote. I haven’t changed anything. The history of the device in ST shows button presses being picked up and then a sudden stop a week ago. I won’t do the reset again as per your advice above - what’s the best way to diagnose this? Thank you!

Best to get driver logging which can be done by downloading the ST CLI to a Linux/Windows/macOS computer and issuing the command “smartthings edge:drivers:logcat” and selecting the specific driver to log.

1 Like

Thank you. I have three Hue bridges in the house connected to ST. Have run that command, every few seconds it shows 200/OK and “thread event handled” for all three of them. So clearly the driver sees all three bridges. When I press a button on a switch connected to one of the other two bridges, a whole bunch of logs appear, so the button press is identified. However nothing appears when I press a button on a switch connected to the third bridge (call it bridge 3). And there are also no updates from the sensor or any other devices connected to that bridge.

Physically unplugging bridge 3 leads to the ST app showing the motion sensor as no longer visible, so clearly the Hue Edge Beta driver is not just picking up the bridge, it’s also picking up the devices in real time, it’s just not picking up any signals from them e.g. motion, or button presses. Also bridge 3 works totally fine from a Hue point of view, i.e. all the lights, accessories, automations, via the Hue ecosystem work as expected.

Doing the physical restart of bridge 3 leads to the edge driver picking up the signals again, i.e. I can see in the logs button presses. I assume, since it’s happened twice before, this will continue for a while and then stop working again.

What would be the next step to debug why the driver isn’t picking up anything from the devices on that bridge, even though it sees the bridge itself?

Drivers don’t see devices. Devices generate messages that get handled by the hub and ultimately the driver.

Then either the button isn’t generating events that the bridge passes on or the bridge is receiving events and not passing them on.

The bridge is a proxy to the device. If you unplug the bridge, it is no longer providing status to ST so it will end up appearing offline.

Clearly there is something different about this 3rd bridge. Can you confirm that it’s firmware level is the same as the other two? Is it the same model as the other two? Was it purchased at the same time as the other two or at a different time?

Is there any debugging capability for the bridge?

Ok so it sounds like the issue is almost certainly with the bridge. I’ve checked and it is indeed exactly the same as the other two - Model ID BSB002, same software version, same API version. I do have access to the API and can see via the API the button press events. Sounds like the best step now is to wait for it to stop working now, and then check the bridge’s API. If it’s not showing the events, then the problem is within the bridge itself.

when I try to open the driver invitation link it says “You do not have permission to access the specified invitation” any idea how to get the driver?

Hi all

I seem to be having issues with this :cry:

I reached the hard limit on my hue bridge, so have purchased a new one. It took some doing to get both to get connected to smartthings, I had to remove and readd the original hub and new one together. Anyway they were both connected and now everytime I try and refresh the lights/zones I get an error message. This happens with both bridges

Rebooting the hub seems to sort it sometimes, but all my devices keep reporting offline. Any ideas please?

Hi @blueyetisoftware I’m having trouble to install the driver. Keep saying “Forbidden” can you help me get it please :pray:

Same problem here…

Sounds like the invitation either expired, or ST nuked them all. I see it reported on quite a few drivers. I’ll take a look tomorrow and see if I can’t get a new one posted.

It could definitely be the bridge, but another option is that it is exceeding its max number of connected clients. These Hue bridges max out as you start connecting more stuff to them. At that point they just choose one to drop. I think it is a max of 4 simultaneous connection, but I could be wrong. Integrations often use 2 in parallel. One for receiving events and one for sending events. This is true for this driver as well since ST wouldn’t let me multiplex the messages. Do you have Google, Alexa, Home Assistant, the stock ST driver or anything else connected to it?

Updated invite link. Also updated in the top post…

2 Likes

Is there a fix for grouped devices no longer having color options? They are there in routines and thru Sharptools but not available in device.

I managed to install the drivers, but I have several problems:

  • First I let it detect my Rooms. That worked without a problem. Then I let it detect my zones. That didn’t work. After I reset my Aeotec Hub, it detected the zones. For every new detection I first had to reset my hub.
  • From all the zones only 2 works. The 3 others don’t respond.
  • From all the rooms, none works. They don’t respond to any command. (On/off, dimmer)
  • I reset the Hue Hub. After that a room went offline, and most of my Buttons. I can’t get them back online. In the Hue app everything works fine.

Update: it seems that after a (very) long time some of the buttons and the room got back online. But now after more than one hour, still 4 of the buttons are offline.

Update2: I deleted and then again detected the rooms, buttons and zones that didn’t work. They seem fine now. Let’s hope that stays that way…

Thank you. It looks like an overloaded bridge was indeed the issue, fingers crossed. I removed a bunch of smart scenes and a few devices, and so far so good, the edge driver seems to be working as expected.

1 Like

I really love this. I use it in a lot of things.

So I was wondering, if it is known if it will just work with the new hue bridge pro?

5 Likes

Hi all, can anyone confirm if this drive works with the new Hue bridge pro before I start messing about with it?