Add reboot button to Shelly devices#60417
Conversation
|
Hey there @balloob, @bieniu, @thecode, @chemelli74, mind taking a look at this pull request as it has been labeled with an integration ( |
It's marked as the config entity category and doesn't update frequently, so there should not be a reason to disable it from that perspective? Is there any specific other reason? |
|
I agree with @frenck, we try to minimize irrelevant entities (for example BETA OTA is disabled), but since it is a configuration entity would be nice to leave it enabled by default. |
The beta OTA button is also a configuration entity.
I agree, that this will not pollute the state machine, but ...
... since both (beta OTA and reboot button) are assumed to not be common used - only by advanced users. |
|
We used to disable less common entities in the past, to prevent generated dashboards and such to be cleaner (and thus clean from less commonly used entities). The introduction of the entity categories made that a lesser problem. The beta case, I agree, that should be disabled by default, but this case: I don't see a reason why it should be disabled. |
|
IMO a regular OTA update is somehow normal during usual lifetime of a device, but a beta firmware or rebooting the device would fairly not commonly be used (for me there was no use case till now, to reboot a Shelly device), so i assumed to disable them (for same reason) should be ok. For sure, if we want the reboot button be enabled by default, than i will change it 👍 |
Yes :) |
Your wish is my command 😃 |
Proposed change
This reworks the recent implemented buttons to use entity descriptors and adds the new button to trigger a reboot of the Shelly device.
Since this feature is fairly not common to be used, the button is disabled by default.
Type of change
Additional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: