That really sucks! I was hoping to someday have true local LAN integration between Hubitat and the Harmony Hub. Seems like that day will never come now...
I am betting it was done for security. If Logitech won't allow new integrations, and they now have blocked local access, it seems like users will be forced to move to other solutions. Fortunately for me, I really don't depend on the integration for much, except turning the Home Entertainment system on and off - and that is really via Alexa voice control!
@aaron I hope you haven't put too much time into that other local control solution we've been talking about
Sounds like relying on the native ST integration is going to be one of the few choices for those of us needing to integrate other automations with Harmony going forward, unless this was a mistake and Logitech backs it out.
For anyone who will be left high and dry by this change...the native ST/Harmony integration allows for instant updates if you add the ST activity switches back into the Harmony activities so each activity turns it's own activity switch on & off. This can all be done without a ST hub. You can also install and configure webCoRE in ST IDE without a hub, which can make and receive http calls with Hubitat to accomplish 3-way sync between Harmony <--> SmartThings <--> Hubitat. It's not local, but it's pretty quick...when I start a Harmony activity I have some TV backlights turn on. This usually happens within 1 second of tapping the activity on the Harmony remote.
Mine has still yet to update and checking with a few others, does appear they’ve halted the rollout. Only one reply from Logetech as yet, saying they’ll update soon
Just read it. This would be awesome if he is right about the websockets. He makes it sound like you can do things like activate scene's without needing to authenticate all locally. If possible, a simple driver to do that would be easy if you can get all of the websocket commands.
Yup. I got a quick python script working that queried the hub and pulled the info I wanted. Was really easy. I'll check out their code later to see how they trigger the activity.
But it requires no authentication at all. Just open up a websocket and start firing info at it. All local.
The other downside is that its one way only. No call back yet. So if the activity is activated via the remote the hub will not know. Unless you add polling into the code which adds a delay.
I will be keeping a close eye on their developments.