Fix Shelly button device triggers

[thecode]

Proposed change

Shelly button is a sleeping device which it is not initialized after HA core restart until manually waked up by a button press.
When having device automations based input triggers for this device getting or validating the triggers will fail when device is not initialized.
Since this device has fixed input triggers it is not needed to wait for the device to wake up and input triggers types can be fixed.

Should be tagged for milestone 2021.4.3

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

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes Shelly button issue with automations when used as trigger #48837
• 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.
• 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 @balloob, @bieniu, @chemelli74, mind taking a look at this pull request as its been labeled with an integration (shelly) you are listed as a codeowner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Please address the comment in a new PR. Thanks!

[MartinHjelmare]

We don't want to interact with integration details in the tests. We should just set up the integration and patch in the periphery, eg the library, as needed.

https://developers.home-assistant.io/docs/development_testing#writing-tests-for-integrations

[thecode]

This is not specific to this test, I am planning to rewrite all the tests, already tried some options but I was not happy with the result, If it is OK by you I would like to use your help for mocking the library in the right way.

[MartinHjelmare]

Sure!

[MartinHjelmare]

Looking at the library, one thing that makes the library harder to patch is that it is mixing the business logic of the Device class with the transport handling (aiohttp, coap and socket). If we'd break out the transport handling into a client class that the device can use, it would be easier to patch the client and know that all I/O is patched.