expanded docs/examples for keypadlinc?

[dduff617]

Feedback

KeypadLinc (model 2334-222 and other variants) is a device with some unique characteristics and i would daresay for people who still have Insteon devices installed in their houses possibly represents unique functionality that is not easily replaced with other devices/protocols.

I am able to create triggers (automations) based these devices and in particular based on user interactions with buttons. For example I have been able to create some simple triggers based on triggers like this: - platform: device type: turned_on device_id: bf5ddfef8a4ab742e60531d16104d1c0 entity_id: 42cb130736a3ff7ac23d302638638bf3 domain: switch id: button-on

... where the particular device_id and entity_id refer to one of my keypad button entities.

Here are some topics/issues that I believe it would be helpful to have covered in the docs:

• How do I create triggers for other events like when keypad buttons are pushed and held, then released (start/stop brighten/dim)? These are useful for example when I want to use a keypadLinc button (or other Insteon device for that matter) as a controller for other types of devices - Hue or Lutron lights, shades, etc.
• How can I trigger on button double-push (fast-on or fast-off), etc? These are potentially useful for many things such as invoking scenes or automations.
• How can I create a blueprint to create a two-way link of a keypad button to the on/off state of a HA entity? I tried using the same type of trigger (shown above) that worked as an automation, but could not figure out how to get it to work as a blueprint - possibly due to my lack of full understanding of the nuances of the blueprint system, devices, entities, etc. This is why I think an example would be valuable.

I observe that the docs do have a section dedicated to "Events and Mini Remotes" which leads me to wonder whether possibly a better way to write automations/blueprints for keypadLinc buttons might be to use event triggers (rather than e.g. a device/turn_on trigger)... if this is the intent, I think some additional docs and perhaps an example would be useful to show how this is done.

URL

https://www.home-assistant.io/integrations/insteon/

Version

2024.6.4

Additional information

I migrated to HA earlier this year. My previous home control system/architecture was based on (Indigo). Indigo provides full support for KeypadLinc devices, including being able to attach triggers (automations) to the full set of button events. I suspect there are a good number of Indigo users like myself migrating to Home Assistant and looking for corresponding features in the Insteon integration.

I've tried some experiments with limited success as well as searching through forums and I mostly haven't come up with any answers. In a few cases, I do see evidence of others searching for similar info but as far as i can tell, not finding. So this seems like a case where some mention in the docs would be useful -- even if the docs were to mention something like "not currently supported" or "may be supported in an upcoming release" or something.

[home-assistant[bot]]

Hey there @teharris1, mind taking a look at this feedback as it has been labeled with an integration (insteon) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `insteon` can trigger bot actions by commenting: - `@home-assistant close` Closes the feedback. - `@home-assistant rename Awesome new title` Renames the feedback. - `@home-assistant reopen` Reopen the feedback. - `@home-assistant unassign insteon` Removes the current integration label and assignees on the feedback, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information) to the feedback. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information) on the feedback.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved. If this issue is still relevant, please let us know by leaving a comment 👍 This issue has now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.