-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
momentary function (id 20) behaves like a roller blind switch #4057
Comments
Please make a driver log, loglevel cc @AlCalzone |
I don't see how the physical behavior of the end device would depend on the version of Z-Wave JS, but let's see that log. I'm also not sure what you mean by "scene". |
zwave-js-ui: 9.25.0zwave-js: 13.10.1
I press switch 2, scene id=26, the light turns on. It's ok zwave-js-ui: 9.28.0zwave-js: 14.3.7
I restore my VM to the old zwave versionzwave-js-ui: 9.25.0zwave-js: 13.10.1 I press switch 2, scene id=26, the light turns on. It's ok |
debug13_10_1.txt |
Those are not driver logs. Please check the link @robertsLando posted before. |
This --> driver log, |
sorry |
Checklist
Deploy method
Docker
Z-Wave JS UI version
9.27.8
ZwaveJS version
14.3.7
Describe the bug
a double momentary switch is connected to a fibaro FGD212 - Dimmer 2. button 2 is used with a scene (normal press), to turn on another light. When I press the button, the light turns on then off. In the logs 2 actions are executed at the same time as if I pressed the button twice.
it seems to behave like a bistable while id 20 is configured in "momentary"
This behavior is observed on 3 fibaro modules that use scenes.
I restore my VM with version 9.25 of zwave JS UI, everything works normally, one press of the button turns on the lamp, another turns it off
To Reproduce
I restore my VM to the previous version, I no longer have the problem. I redo the update to 9.27.8, the problem returns
Expected behavior
when i press the button the light turns on but should not turn off. The scene action should run once but not 2
Additional context
No response
The text was updated successfully, but these errors were encountered: