Lutron Pico Button Press in HomeKit

[kappa12]

This is a continuation of an original post I made in the Lutron RRA2/Caséta plugin support area, but since confirmed it's likely an issue related to HKLS: viewtopic.php?t=28755. So, I'm posting here for support.

I'm using the Lutron RRA2/Caséta plugin and set it up to expose several Pico remotes to HomeKit via the HomeKitLink Siri plugin. I'm using the Pico button presses to trigger opening/closing/etc of non-Lutron shades (Eve Motionblinds) that are accessible only via HomeKit (no direct Indigo control is possible afaik). This works, but I need to press the Pico buttons for several seconds before the button status is reflected in HomeKit and any HomeKit automations are triggered. I can see the button presses almost instantaneously in Indigo (the state changes from off to on, then back), so I know the Lutron plugin is working properly. My guess is the quick presses where the button state in Indigo changes from off to on to off again within a tenth of a second is too short of a duration for the HKLS plugin to recognize it and broadcast it to HomeKit.

Has anyone else had a similar issue and found a way to work around it? I was thinking I could set up a virtual device in Indigo that shadows the Pico button but stays on for some predefined duration that's long enough for HKLS to recognize it, then the shadow button automatically turns itself off, but this seems a bit complex for such a simple problem. I'm hoping there's a more elegant solution that can solve the issue.

[GlennNZ]

Hi

If I’m following correctly - then not sure there is much HKLS can do.

There is no delay to HKLS recognising device state changes. It should happen immediately. Likely what is happening here is it is happening immediately but either not being registered by Indigo (which obviously we need - I would guess this is unlikely) or is very quickly off again - and HKLS is getting a On/off and acting on the latest only. If you turn on debug device for this device in HKLS you should set any registered device state changes.

Probably best to change to action group type approach - eg.
Create action group for these plugin devices (Noting that plugin devices aren’t as a major HKLS priority)
And publish these action groups to HKLS

Action groups are stateless (they have no states) simply run the action groups once on press. This is likely the approach you need.
(Alternatively there may be a HKLS button type that is better suited - believe it does exist)

Glenn


Sent from my iPad using Tapatalk

[kappa12]

Thanks for the feedback. With your hint about the debug logging, I was able to confirm that the issue is what we thought: HKLS is getting a On/off and acting on the latest only. I was able to work around it by injecting a 1 second delay to the "off" action on the Lutron plugin side.