[Release] Logitech Harmony Hub Driver v0.1.20230311

Your Device id for the very top of your log would begin at hue-00:17 and copy all the way to 3e:0b

I fixed it. Should have it now.

Yep, I see it. I had to reorder the button numbers to work with the concept of a variable number of Home Control device IDs being defined in the settings. I'll send you a PM with my current updates to have you give it a test in a little while.

gotcha thanks! I was looking for it to say something like "ID= 12345678" like it returns for activities and devices. Didn't realize it would be a string. Got it working now.

Before you go too far, we are working on a slightly revised version that is going to change the Hubitat Button Numbers a little. Please hold off until the new version is posted to avoid having to redo all of your Button Apps.

@michael.sbrocchi and @abuttino - I have updated my GitHub repo with the latest version.

3 Likes

This driver just changed my world. WAF+++

Thanks so much!

4 Likes

@ogiewon and @abuttino Amazing work! Thank you for making and sharing all this with us.

1 Like

I have released v0.1.20200920 of the Logitech Harmony Hub Driver.

There are now only 4 buttons defined, each with 'pushed' and 'held' events. This aligns with the physical behavior of using the Home Control buttons on the Harmony Remote. I also made sure only one event is generated per activation of any of the 4 buttons. Be aware that clicking the increase/decrease home control button, will result in additional button pushed events for the last home control button pushed. No easy way to prevent this. The 'numberOfButtons' attribute will now be either 0 (no Home Control device IDs defined in the user preferences) or 4.

Enjoy!

5 Likes

so just as something i noticed.

the Child Switch is called just that "child switch" in my apps its kinda hard to find. I recommend that it is named "Logitech Harmony Hub Child Switch" or something keeping it more in line?

just an idea.

Thanks for the feedback. It is the same Child Switch Driver that I use for my Hubduino integration. Thus, I am not really wanting to rename the driver.

I have been considering changing the Parent to use Hubitat's built in "Generic Component Switch" driver which is now available in the platform firmware. However, this will probably break existing users' setups... :thinking:

1 Like

I got this to work but with a very long delay. Is this a normal condition?

Please describe what/when you’re seeing a delay. This driver has numerous pieces and parts, and thus I am not sure what you’re describing.

If you’re referring to using the Home Control buttons on the remote..the only time you might see a delay is immediately after clicking SAVE on the device details page. Immediately following, the driver queries the Harmony Hub for new Activities which can take a while to process (somewhere in the 5-20 seconds range.)

I have so far only set button 1 to control a lamp and this was done by identifying the device id for button one (from debug in logs), pasting it into the driver page for button one, saving preferences. After this i tried to turn on off the lamp and the delay for both actions. I tried again this morning and same thing. I may have missed some steps for implementing this. I updated the code and then turned on debug found the button id and pasted. Did I misunderstand the update and fail to do it correctly?

It sounds like you configured it correctly. Let's simplify the problem by breaking into its two main parts... Open up the Harmony Hub Parent Device details page. With that page open, click the EVENTS link in the top left corner. You should now seen any recent activity for this device. Now push the home control button on your remote control, and then start refreshing the EVENTS web page for the Harmony Hub Parent device... You should see a 'pushed' event appear pretty quickly that corresponds to the button press on the remote. Try the same thing with Holding the same button on your remote, and then refresh the Events page. You should see the Hold event appear relatively quickly.

If you're not seeing these events generated with about 1 second of pushing/holding the Home Control button on your remote control, we know the issue is with the Remote/Harmony Hub/Harmony Hub Parent Driver...

If you are seeing the events generated relatively quickly, then the issue is with the Automation you created on the Hubitat hub to handle the button 1 pushed/held events to turn on your lights.

This is much simpler to debug if you set up multiple Home Control buttons in the Harmony Hub Parent Device. Once you do this, you can simply watch the status of the 'pushed' and 'held' attributes in the Current States section of the device details page for changes from button 1 to 2 to 3 to 4 as you push or hold the buttons on the remote. With only one button defined, it will never visibly change on the device details screen, which is why I recommended refreshing the EVENTS page instead.

Okay, I will set another after work. Should toggle on/off be stayed away from and only use single action for pushed and held? I am no programmer so I am learning as I go. Thanks for the help!

What Hubitat App are you using to handle the 'pushed' and 'held' events? You should be able to use a Toggle action on a light. But, if that light is slow to respond with an updated state back to Hubitat, that could result in poor performance of the automation. This is why it is always a good idea to determine where the delay is coming from...the button device (in this case, the Harmony Hub parent device) OR the automation.

I rarely use TOGGLE as an action. When I was testing this particular functionality yesterday, I used 'pushed' to turn on a light and 'held' to turn off a light.

I am using ABC (advanced button controller). I will change to pushed and held and post if there is an improvement. I will looking into the other suggestions you made too!

I am also using ABC to handle these button pushed and held events.

:+1::+1::+1::+1::+1: Thank you so much for this. Not having the home control was the only feature I missed after tossing Smartthings into the abyss. Mapped the buttons to 4 new virtual buttons on my parents smartthings unit, got the codes and mapped them with the built in Button Controller. Devices respond so quick. Thanks again!!

1 Like

Instructions coming for using this properly. I just want to make sure all the edits are done before I type them all up.

2 Likes