Trigger Alexa routines from toggles and buttons

[mdegat01]

Proposed change

Switches and input booleans are double listed as both Alexa.PowerController and Alexa.ContactSensor interfaces. This enables users to trigger routines from their state changes using the smart home option. Buttons and input buttons are also double listed as Alexa.SceneController and Alexa.EventDetectionSensor, the latter specifically with supportsNotDetected set to false. This enables users to make routines which trigger when the button is pressed.

This change really has no impact on existing use cases with Alexa. I specifically did not change the display categories so devices appear exactly as they did before and work in the same use cases they did before (alexa can press buttons and change switches/toggles from routines). They just now also appear as routine starter options under "smart home".

It's a bit unintuitive in this particular menu since you see this UI for buttons:

Button pretending its a presence detector

And this for switches and toggles:

Switch pretending its a contact sensor

But it is in line with what users were already doing to solve this use case, it just makes it easier (no YAML/template knowledge required). And we can guide them through it with a bit of documentation.

This will help users interested in HA but invested in Alexa able to transition more slowly by leveraging their existing routines. It also gives all users a way to leverage devices and services which can be integrated with Alexa but not with HA.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @home-assistant/cloud, @ochlocracy, mind taking a look at this pull request as it has been labeled with an integration (alexa) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[mdegat01]

Bonehead move on my part. I was not getting events because I forgot to put endpoint, client_id and client_secret into the config of my test system. Now that I set up proactive events correctly this works great. Pressing buttons and toggling switches triggers my routines.

[github-actions]

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

[emontnemery]

LGTM, thanks @mdegat01 👍