Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add warning line to update entities, warn for some Z-Wave OTA updates #44

Open
AlCalzone opened this issue Jul 4, 2024 · 0 comments
Open
Assignees
Labels
architecture This request needs an architecture discussion for the HA core project

Comments

@AlCalzone
Copy link
Member

AlCalzone commented Jul 4, 2024

e.g. if the device requires being re-included after the update

In some cases a device can be updated but the update has consequences, like it needs be re-included. We do not want users to just update the device without telling them about the fallout. The users needs to do an additional confirmation and we want to show a warning.

  • A user should see a special visual element that the update is major / has additional actions.
  • When a user wants to update, the update entity should;
    • have an additional parameter in the service call
    • has a extra prompt in the UI

Architecture Discussion: home-assistant/architecture#1103

Design suggestion:

Add a parameter to the service call that allows such updates, otherwise raise an exception in the service call, and a state attribute to mark the entity as major/breaking? Frontend should be updated with confirmation dialog or similar.

@AlCalzone AlCalzone converted this from a draft issue Jul 4, 2024
@marcelveldt marcelveldt moved this from Later to TBD in Z-Wave JS: Road to Certification Jul 4, 2024
@MartinHjelmare MartinHjelmare added the architecture This request needs an architecture discussion for the HA core project label Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture This request needs an architecture discussion for the HA core project
Projects
Development

No branches or pull requests

2 participants