Add button to trigger ota firmware update for Shelly devices

[mib1185]

Proposed change

This will add a new service to the Shelly integration which allows the user to trigger an ota firmware update for their Shelly devices (follow-up of #57005 (comment))
This add two new button entities to trigger a so called OTA firmware update of Shelly devices, each one for stable and beta (disabled by default) channel.
This is limited to only update to latest stable or beta release (uploading an image or triggered update from specified url is out of scope and will not be integrated).

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: Add OTA update button to Shelly home-assistant.io#20194

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 @balloob, @bieniu, @thecode, @chemelli74, mind taking a look at this pull request as it has been labeled with an integration (shelly) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[mib1185]

as discussed on Discord, split this PR into 3 parts

1. Use constant CONF_SLEEP_PERIOD instead of string "sleep_period" in Shelly integration #59195
2. Bump aioshelly to 1.0.4 #59209
3. the OTA update service itself

Those this PR goes back into draft, until 1) and 2) are done

[mib1185]

support for battery powered devices has been removed, since there are to many challenges with them, which solution would overwhelm this PR.

[mib1185]

recent changes

• remove "beta channel" switch
• add second button for update to beta version
• "beta update" button disabled by default, since most users will run on stable builds

[frenck]

After pressing the button, the state should be the time the button was pressed, not None. There seems to be something wrong?

[mib1185]

it is not the state.state ... it is just the check that the beta button is not enabled by default, so not present in the state machine

[frenck]

is not enabled by default, so not present in the state machine

In that case, I'm confused, why can it be called by the above service call in that case? If the button entity isn't enabled, that shouldn't be working...

[mib1185]

the service call is for button.test_name_ota_update (without beta suffix) ;)

[frenck]

[mib1185]

it's ok ... the weekend is near ... take a beer and relax 🍻

[frenck]

Thanks, @mib1185 👍