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

switch multilevel duration problem #2645

Open
kdschlosser opened this issue Nov 10, 2022 · 0 comments
Open

switch multilevel duration problem #2645

kdschlosser opened this issue Nov 10, 2022 · 0 comments

Comments

@kdschlosser
Copy link
Contributor

The duration value for a multilevel switch is flawed. If the device supports version 4 of the command class there is going to be a bumping of heads because the duration value is used by both the report command and also by the set command. If there is a current transition taking place there are going to be reports that contain the mount of time left. The bumping of heads is going to occur if there is a transition happening and the user wants to change the transition. They would set the duration and then set the level. If a report comes in after the user sets the duration but before the user sets the level the duration from the report is going to get used instead of the duration a user has set.

The fix would be to add a "target_duration" value just like there is a target_level value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant