Skip to content

Add service ota_update to shelly integration#17163

Closed
mib1185 wants to merge 2 commits into
home-assistant:nextfrom
mib1185:shelly_add-otaupdate-service
Closed

Add service ota_update to shelly integration#17163
mib1185 wants to merge 2 commits into
home-assistant:nextfrom
mib1185:shelly_add-otaupdate-service

Conversation

@mib1185
Copy link
Copy Markdown
Member

@mib1185 mib1185 commented Mar 28, 2021

Proposed change

This PR adds a new service ota_update to the shelly integration, which is intended to trigger OTA updates to a single or multiple devices at the same time.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

@probot-home-assistant probot-home-assistant Bot added has-parent This PR has a parent PR in another repo next This PR goes into the next branch labels Mar 28, 2021
@mib1185 mib1185 changed the title add ota_update service Add service ota_update to shelly integration Mar 28, 2021
@mib1185 mib1185 force-pushed the shelly_add-otaupdate-service branch from b57e5a7 to a268f55 Compare March 28, 2021 21:45
Comment thread source/_integrations/shelly.markdown Outdated

### Service `shelly.ota_update`

Triggers an over-the-air update for selected Shelly device(s). At least one of `area_id` or `device_id` has to be provided. This could be easily done via the target selector on UI.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was the indication for me to go to the parent PR and leave a comment on the implementation. This should be implemented as an entity service.

That way, it can use a target (meaning, entity_id, area_id or device_id and even a mix of it, is accepted).

@frenck frenck added the in-progress This PR/Issue is currently being worked on label Mar 29, 2021
@frenck frenck assigned frenck and mib1185 and unassigned frenck Mar 29, 2021
@mib1185 mib1185 force-pushed the shelly_add-otaupdate-service branch from bc2fa9b to 8a9746d Compare April 5, 2021 17:22
@mib1185 mib1185 force-pushed the shelly_add-otaupdate-service branch from 8a9746d to b4462c0 Compare April 5, 2021 17:59
@probot-home-assistant probot-home-assistant Bot removed the in-progress This PR/Issue is currently being worked on label May 11, 2021
@github-actions github-actions Bot locked and limited conversation to collaborators May 20, 2021
@mib1185 mib1185 deleted the shelly_add-otaupdate-service branch October 7, 2023 14:28
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla-signed has-parent This PR has a parent PR in another repo next This PR goes into the next branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants