[OBSOLETE] Hue B Smart (Smart and FAST Hue Lighting)

SmartApps & Automations Community Created SmartApps
, , , ,
263

Hmm. I am unaware of an update to the Hue Hub - Philips’ website indicates that the latest firmware update occurred April 2016, and the latest change to API occurred in February 2017. What makes you say that your Hue Hub updated last night? Do you have v1 or v2 hue hub?

So I guess its too late to address what was causing your devices to not update status.

I don’t understand what you mean by “trying to delete the Hue ‘Thing’ ) not the bulbs” - especially since you have said you have deleted all of the bulbs, scenes, and groups.

If you are having difficulty deleting any Hue B Smart (or any other) device, the first thing to check is whether any other smartapp uses that device (such as CoRE, Smart Lighting, Ask Alexa, Echosistant, etc.). When another app uses / subscribes to a device, it may (not always) prevent deletion. Check the smart apps tab for the device in the SmartThings app and/or the locations → smartapps page in the IDE.

If you are unable to delete the Hue B Smart smartapp - which is a completely different thing - please let me know what error is displayed in the ST smartapp when you try, and please let me know what the error is in the IDE log. What does the IDE locations → smartapps show? Does it show any HBS devices? If there are, then your issue is almost certainly caused by that device being used / subscribed by another smartapp (as discussed in previous para).

-Tony

264

I went into the Hue app and it said an update was required, searching the revision number other people upgraded to it in Feb.

Sorry - I’m aware how annoying things like that can be, but I was impatient.
So what I did was is delete the “Hue B Smart Bridge” device via Smart Things directly, when I did this I just got errors in the Smart Things app. I therefore decided to go all out and delete every single “bulb” device, when I did this the Hue B Smart app opened but wouldn’t let me find my Hue Hub, listed my existing one but said I wasn’t Authorized when I tried to go into it or remove it. I couldn’t delete the app as it said “An error had occurred” with no indication that it was trying to delete it in the IDE logs.

So I’ve got a bit further, I rewrote your app so on search for bridges I did state.bridge = [:] and state.linked_bridges = [:] - I ran this, then I pulled your latest code down and relaunched Hue B Smart.

I can now add bulbs and have full control back, apart from every single bulb, group and scene is called “null” within the Smart App, once I add it it is named correctly in the device tile, but obviously I don’t actually know which is which!

For now I will add everything then go through and manually delete.

265

Glad to hear that you’re back online. I updated the smartapp last night to address the null name issue.

266

I updated to your latest (.9c) and got the null issue.

They were named correctly in the devices though, not named “Hue B Smart Scene” like Stacy_Butera.

267

Ok. I guess I misunderstood what you were saying. Is it that the devices that you previously added now appear as “null” in the SmartThings app? If so, I think it may have happened because you tricked ST into adding a new bridge before fully deleting the old one. The new bridge wouldn’t have the device info from the old one.

268

I had to re-add the hub from scratch, then I searched for all my lights, groups and scenes. All of them were “new” as far as Hue B Smart was concerned, but each one was named “null” I tried changing something to resolve it, but removed the hub and am not physically there to press the button now, so can you get you a screenshot later.
I haven’t tried adding them as a “thing” purely from the HBS smartapp.

269

Getting much closer to having everything working. Had the same issue as Stacy_Butera with things being named incorrectly when doing a local discovery, but I’ve sorted that by renaming everything.

One small thing is that the status of my Hue Hub is “0” and it doesn’t appear to have an ID, although it does appear to be picking up updates from Hue, so it’s a pretty minor issue but one which would be good to have resolved so I know it’s all running well.

270

Ignore the status of hue Bridge - it’s not reflective of anything at the moment.

271

I’ll update to the new code either tonight or tomorrow night. Just to keep things fresh. The only thing I’m struggling with is a delay in seeing the status of Hue lights when they are turned off/on.

When I update the code … should I start fresh by removing everything then re-add back in? Otherwise, I’ll just update the device handler.

My Hue Bridge also shows “0” as status but I figured it wasn’t harming anything.

272

You shouldn’t need to remove everything.

The delay is one of them things you get with Smart Things often I’m afraid.

And to prove i wasn’t going insane. https://www.reddit.com/r/Hue/comments/621gs0/new_bridge_update_changelog/

273

@infofiend you also need to update lines 382 397 411 to use label as well, otherwise when bulbs are added they will not have the correct name, which @Stacy_Butera and @Gavin_Melling have run into as well.

I had to remove all bulbs, change those lines to use label and then re-add bulbs.

274

@infofiend I’ve made the changes to the code and the manual changes as suggested by @Collisionc

I will test these changes tonight and report back.

@Gavin_Melling I’ve never had a delay with Hue bulbs reporting their status between Hue and ST before this last update and Hue B Smart has been an awesome handler.

275

I’ve always seen a bit of a delay with mine. Definitely doesn’t seem any worse than in used to be for me.

276

So I updated everything and re-added my groups and scenes. Everything came over as expected. I did make a manual update per @Collisionc suggestions.

Still have the lag showing status of the lights. I’m assuming that’s caused by the ST change making the Hue bulbs local. But otherwise, all is as expected.

Thanks for all the help @Collisionc @infofiend @Gavin_Melling

277

Hello All, I have been watching this thread for awhile now and wanted to know if I should take the plunge? I am using the native ST hue connect and want to know if there are true benefits to moving over to Hue B Smart. My majpr concern is to have to redo everything I have done with Hue and ST up to this point. Is it really worth redoing what I already have to move to hue b smart?

278

I’d certainly recommend moving to Hue B Smart. It is dead simple to setup and the time spent having to re-do everything is well worth it, IMO. Especially if you use custom scenes in Hue. From what I remember the native ST connector will only pull in the normal scenes in Hue - Concentrate, Energize, Relax, etc.

1 Like
279

Question, most of my scenes and groups were crated in HuePro. Do you have any idea if those will import?

280

I installed this Smart App and app of the appropriate Device Handlers for my setup, and then spent 3 hours troubleshooting why the Application never links my Hue Bridge.

  1. My Hue Bridge is Online and functioning correctly, on it’s own and as a device in SmartThings.
  2. Looking at logs in IDE, the Smart App is discovering and then rediscovering my bridge, but the routine in Automations never ends and never returns my Bridge
  3. I Validated that my Smart App and all DH are in IDE and Published.
  4. There are no Ghost app references as stayed in another post for another user having this issue.
  5. I went as far as removing everything (DH’s and Smart App and redeploying - didn’t fix.
  6. I removed all Device Handlers and ran test to find out that the bridge discovery is performed specifically by the App itself and doesn’t need the Device Handlers (did this to test with less complexities with logging)
  7. I powered off / powered on Hue Hub to make sure. Didn’t fix.
  8. I rebooted SmartThings - Didn’t fix
  9. Even pressed the button on the Hue Bridge while Hue B Smart was searching (some other external apps require this in order to discover). Didn’t fix.
  10. Based on everything I was seeing in the logs, it appears the App just continuously goes through the process of sending the request, discovers bridge, rediscovers bridge and just stays in lala land.
  11. I ran the simulator from the Smart App in IDE and the results were the identical messages I was seeing in the normal logs. I am attaching a copy of the log file when running the simulator to see if you can figure out why the app won’t return my bridge when I initiate the process from Automations to search for the bridge.

(FYI - I am not removing my Hue Bridge from SmartThings and losing all my devices and I’m not running cleanup in Hue and losing the scenes and everything I already have in place. Plus my lighting Automations built into routines, ifttt applets, widgets, all my ActionTiles, etc. I shouldn’t have to do this.
I spent too much time getting everything setup correctly. I have 10 a19 -. 3rd gen color bulbs, 1 color strip light, and 1 Hue Go in my setup.

If anyone can help in troubleshooting and debugging why this is happening, that would be greatly appreciated. Everything else in my SmartThings environment is functioning 100%. I would really love to have this complimentary app added to my arsenal of things in ST, but if it comes with the price of removing all my Hue devices previously defined, saved and setup, then it’s not worth it to me.

Here is the log snippet from when I ran the simulator on the Smart App itself:

9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:37 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:37 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:37 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:36 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:36 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:36 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:34 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:34 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:34 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:33 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:33 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:33 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:33 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:33 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:33 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:32 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:32 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:32 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:27 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:27 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:27 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:26 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:26 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:26 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:24 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:24 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:24 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:23 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:23 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:23 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:21 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:21 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:21 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:20 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:20 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:20 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:18 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:18 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:18 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:17 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:17 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:17 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:15 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:15 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:15 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:14 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:14 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:34:14 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:48 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:48 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:48 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:47 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:47 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:47 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:43 PM: debug Bridge discovery sent.
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:43 PM: debug Sending bridge discovery.
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:42 PM: debug Previously found bridge discovered
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:42 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:42 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:41 PM: debug Found new bridge.
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:41 PM: debug Discovered bridge 0017882CEA81 (192.168.1.5)
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:41 PM: debug Discovery Response is [devicetype:04, mac:0017882CEA81, networkAddress:C0A80105, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882cea81, ssdpTerm:urn:schemas-upnp-org:device:basic:1, ssdpNTS:null, hub:fb5ff866-9f7e-481d-bcb8-285076f92738].
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:41 PM: debug Sending bridge discovery.
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:41 PM: debug Doing Hue Device Sync! inItems = null
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:41 PM: debug Initialize.
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:41 PM: debug Updated with settings: [:]
9e1ab2d9-fe57-44f9-8958-ce717ed1d090 2:33:18 PM: debug Sending verify request for 0017882CEA81 (192.168.1.5:80)

Greatly appreciated,
WB

281

It will import any scene that is stored on the Hue hub.

I use HuePro as well to create the scenes, then go into Settings on Hue Pro and select Bridge presets. From that screen, you can upload and download your Hue Pro presets onto the Hue hub.

When you import the Hue Pro bridge presets stored in the Hue hub into Hue B Smart/ST, they will say something like: “Relax from Hue Pro.” The only pain is renaming all the presets in ST to remove “from Hue Pro” so that it’s more natural to say to Alexa.

1 Like
282

FYI: I also have 1 Hue Motion Sensor and 1 Hue Tap setup within Hue. I wouldn’t think that would cause any conflict with discovering my bridge, but I thought I would mention it just in case.