Sorry if this is the wrong thread to post this scenario/question/issue… Before switching over to this driver (which is amazing and surpasses the stock ST hue driver by miles), my setup consisted of an Alexa utilizing the hue and ST skills together. And inside of ST, I also had hue connected so that I could do ST specific automation there.
I believe Alexa (or maybe ST) figured out how to recognize duplicate bulbs, because for a while I did not have duplicates. Moving over to the hue edge BETA driver, I know have duplicates showing up. I realize I could remove the hue skill from Alexa to solve that, thus removing all hue coming from the Alexa side. I haven’t thought through that impact as I do have many automations through alexa that affect hue bulbs and groups.
I guess what I’m getting at is… how are others handling the need to have both systems recognize the hue ecosystem. Because of the slight delay in ST updating the hue hub (i.e. dimming a bulb in ST which can take a bit to update inside hue), I’d rather not kill the Alexa hue skill and solely rely on ST to control hue. But maybe my thinking is way off here. Wondering if anyone else has a solid setup and/or an easy way to stop having duplicates in Alexa. Because anytime there is a new discovery, Alexa will pull everything back in.
As I think about it, I guess the real question for this specific thread is “is there a way to permanently prevent the hue devices from getting pulled into Alexa through the ST skill?”
I am using the skill and this driver without issue. Since the skill has all of the bulbs individual, I was using an Alexa grouping to handle turning on/off, etc. I removed the Alexa groupings after installing this driver and only use this driver for importing my Hue Groups.
If I say, “Turn on Kitchen” it uses the room that this driver made.
If I say, “Turn on Kitchen light 1” it uses the single bulb linked via the Skill.
I hope that helps.
Yes, I follow. I think the issue is really more around how to prevent duplicate devices if at all possible. I am able to control everything without issue. But with around 45 total hue devices, it would be ideal to not have them all showing in Alexa devices twice (one set from hue skill and one set from ST skill). This was not the case with the ST stock hue driver.
This driver has settings to decide what you want to import. I imported only rooms/groups and no individual lights imported from it.
Once the Hue Hub is paired with ST Hub via the driver, you can select ‘Add Devices’ and choose from a number of different options (Rooms, Zones, Motion Sensors, Buttons, Lights)
I have been unsuccessful in getting any of the Lutron Aurora knobs to work with this Edge Driver. I have about 6 and all of them show as offline in the Smartthings app and unavailable in the Hue app even though they function just fine with your hand at the actual knob. Any suggestions to get these lutron aurora knobs working in smartthings?
If they’re not working the Hue App, they won’t work in ST since this driver leverages what’s in your Hue app.
Have you tried troubleshooting in the Hue app to see what the issue is there?
I just figured it out. I just turned the knobs and they became active again in the hue app and smartthings. All is good now! I think in getting a new router recently they just need to be used again and I had not had this driver enabled before the router switch.
This occurs when the knobs don’t checkin to tell the Hue hub they are still active. When you turned the knob, Hue realized it was still alive.
This is true. If you see this agin, the issue is likely with your zigbee mesh network on the Hue side.
You’re probably right. I have moved some things around recently. I will see if there is a way to have the hue hub rebuild it’s zigbee mesh network
Same method as any Zigbee network:
Unplug the hue hub while leaving all other devices connected to the hue hub on power.
Wait about 20 minutes. During this time since the other devices cannot reach the hub, they will go into “panic mode.“
Put the Hue hub back on power. This will cause all of the devices on the zigbee Network created by the hue hub to rebuild their neighbor tables. This process can take several hours, so you may not see results until the next day.
Is anybody using this driver on the Wifi Mesh Hub? I have a user that is seeing a fatal crash in the ST socket code when using that hub. Curious if it is tied to that model of hub, or possibly the version of his firmware. If you are using the Wifi Mesh hub, can you please DM me your firmware version and let me know if you are able to successfully refresh your Hue hub device from the ST app.
Looking for some help. I installed and everything works great, until a few days ago. Had major storm here, and wifi cut out for a few hours. Now wifi is all connected. Problem is ST is saying philips hue hub and lights are all “offline”. They are not offline because when I got to philips hue app I can control every from there no issue. ST and philips hue is no longer communicating. How can I get them to communicate again? Any ides on preventing this issue?
What does the Hub Link setting in the ST Device say? If it says something else besides ‘Linked’ I would try to link it via the gear icon next to it.
I cannot click on the gear icon because ST is reading it as “offline”. The only thing I can click is “learn more” which bring up the usual troubleshooting things turn on off device, restart router, etc. None of which worked.
Pull down to refresh on the hub device. Otherwise, just restart your ST hub.
It seems like i am on a older driver.
Am i right that i need to follow this steps indicated here to upgrade to the latest driver? Thanks
so been at this for a few days, but no matter what I do, I can’t have my hue hub discovered by this driver, it always defaults back to the native hue one.
things I’ve already tried:
- letting default default hue driver find the hub and then attempting to readd it afterwards (with a tap that can’t be stolen by the default driver). this just results in an infinite scan, never finding the hub a second time.
- manually uninstalling the default hue driver and attempting to scan devices with only blue yeti’s present. this results in the devices being discovered, but there’s no “authenticate” in the menu, and shortly after, the default hue driver reappears and is identified as the hub’s active one.
desperately want to use this driver, but currently at a loss. any ideas?
@blueyetisoftware not sure what changed (nothing on my side, same firmware on the SmartThings station, same driver version) but the lights I have with your driver stopped working, I already reboot the SmartThings hub and nothing work, I observed something weird on the SmartThings App, the sensors and the hub now appear like lights (instead hub or motion sensor as before), also looks like capabilities was changed because all my routines using your driver was automatically disabled.