You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is the result of a meeting about current issues that block Home Assistant from becoming Z-Wave certified.
Multilevel switch entities, dimmer etc, need an optimistic state update with the passed value, eg brightness, to avoid toggling back and forth in the GUI. This is a workaround to be less confusing for the user. Add the state update in the service handler in the relevant Z-Wave platforms.
Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of zwave_js can trigger bot actions by commenting:
@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
The problem
This issue is the result of a meeting about current issues that block Home Assistant from becoming Z-Wave certified.
Multilevel switch entities, dimmer etc, need an optimistic state update with the passed value, eg brightness, to avoid toggling back and forth in the GUI. This is a workaround to be less confusing for the user. Add the state update in the service handler in the relevant Z-Wave platforms.
See eg: #47388
What version of Home Assistant Core has the issue?
core-2023.4.0.dev0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Core
Integration causing the issue
Z-Wave
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: