New Hue Bridge Integration in .706

Not sure I know what you are referring to (Harmony Hue Discovery). Did I miss an alternative route?

One of the more interesting side effects of our Alexa local discovery is that we emulate a hue bridge on your network. So the same devices you allow in the Alexa app would show up in the Harmony Hue Integration if you find Hubitat.

Harmony can then find and control any virtual switch (enabled in Alexa app).

Or maybe I miss understood your use case. Are you wanting Hubitat to trigger Harmony devices?

This is an important item off the check list. For me personally, the Insteon stuff still needs ST and I’m still going to use it with OH for a sudo mobile UI since I don’t have SmartTIles. So it still has some usefulness, but the way things have been going, Samsung isn’t helping their cause.

No, I use the harmony/smartthings integration to activate virtual switches (watching move/watching game) to set lighting scenes in my theater room based on current activity. Maybe there is a better way to do this and finally ditch ST all together?

So, you want to have a harmony remote action trigger something in Hubitat? Yeah, just have Harmony discover Hue Bridges, it should find Hubitat and set up your actions in Harmony to do just that.

1 Like

If you're having issues with Alexa discovering Hubitat, send a message to @justin.bennett. He finally was successful in getting it working in his environment, but didn't confirm what he did to resolve.

I’ll play with that and see if it solves my use case. Thanks @patrick

1 Like

OK, so harmony is seeing the hubitat as a hue bridge, but when I try to pair it the app just sits on the page waiting for me to hit the center button that doesn’t exist on the hubitat unless I’m missing something.

Have you looked at simply integrating Harmony directly with Hubitat? This would provide you with essentially the same integration between Hubitat/Harmony that exists with ST/Harmony today.

Here is a great post at a method to do exactly that.

Note: This method assumes you have an existing ST/Harmony integration already as you'll need to 'borrow' the keys from it. I'd recommend leaving the integration on ST as removing it would probably break the Hubitat/Harmony integration as well.

I have been using this for a few weeks now, and it works very well for my simple use cases.


Yeah, good catch… Forgot harmony needs authentication, but Alexa doesn’t. Sorry for the fire drill.

I forgot the last item on the checklist...SONOS
ST lives to fight another day but it received a hell of a whooping today in any case.


@ogiewon Yes, I’m using that method now to control harmony activites from hubitat. However, unless i have something setup wrong the “current activity” states takes a long time to update (maybe long isn’t the correct word, but it’s far from realtime). Basically I want to be able to tell hubitat that I’m watching a movie based on current harmony activity and have it change the lighting scenes. I also have different seems for when the kids are gaming.

@halfrican.ak Gotcha. I assume that means you are changing the Harmony Activity using something other than Hubitat, correct? Like a Harmony Remote Control? Or Alexa-to-Harmony direct integration? These will result in up to 5 minutes of delay before the Hubitat devices for these Harmony Activities are updated due to the polling refresh.

If you’re using Alexa, you could expose the Hubitat-Harmony Activities to Alexa, instead of direct Alexa-to-Harmony. This should make sure the Hubitat-Activity devices are kept up to date in real time.

Not ideal, for sure…

Yes, ST is what causes the delay. I’ve always had issues with the refresh, so the method I described in my post is good for initiating the activity, but not for monitoring its state. If you need to do that, you might have better success with the port @mattw did. I was using that, but as @stephack noted, it seems to have resulted in weird slowdowns on the Harmony, which was a problem for the WAF. I’ve removed it, but I’m still having problems I haven’t totally resolved. Might be unrelated, but my Harmony Touch is frequently re-syncing since adding that.

I’m actually more interested in controlling devices directly via Harmony because they support Insteon and August Lock among others and I really don’t want an Activity for every Insteon bulb I have and Activities mess with the state of other activities, so that’s definitely not a preferred method for me. I don’t have a free computer that is capable of running Docker, so I have not tried the port @Keo did of KuKu Harmony yet.

The ideal scenario is of course going to be when we have direct local control of Harmony and the completed Hubitat Alexa Wizard and Alexa Skill.

Yes, I am using the a harmony remote to control activities. And yes, the delay you describe is definitely there. Perhaps I should just buy an Alexa for the sole purpose of allowing the harmony/hue integration with hubitat that @patrick was mentioning? I am open to this if it is a reasonable “work-around” until native harmony integration is available?

If you just want to discover Hubitat virtual switches in Harmony, you should be able to do it without purchasing an Echo. There’s a free app called Roger for iOS, and one other (can’t remember the name) for Android that gives you a AVS (Alexa Voices Services) on your phone. If you configure one of these, it adds them to an Alexa account, just as if you had a physical device. That Alexa account is all you’re looking for to accomplish the Harmony bit @patrick was mentioning.

Using a Pico to control Hue bulbs via Hue Bridge with 4 sec faster response than ST … priceless.
This is fantastic, thank you Hubitat!


A note about controlling Hue groups in Hubitat.

It’s handy that you can access groups, but groups always default to their previous level. This is good, but might not be the result you are always looking for. For example, if you turn ON just one light in a group to a different level, and then turn it OFF, when you turn the entire group ON, that one light will be at the previous level. This is Hue behavior Nothing wrong with the Hubitat Hue Integration.

Access to Hue scenes would resolve this, but of course, RM and Virtual Switches are a viable workaround until that is possible.

I had to press the hue button while detecting the habitat devices.

That’s odd. How long did you wait before you made the decision to try pushing the button for the devices?