-
-
Notifications
You must be signed in to change notification settings - Fork 635
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
FGD-212 not reporting Scene Activation Command Class #7546
Comments
Please make a driver log of a re-interview, loglevel |
See driver log attached. |
Should be fixed in latest release. Try to upgrade to zui 9.30.0 |
@robertsLando: thanks for coming back on this. Unfortunately, I cannot see any improvements under 9.30.1 (see screenshot). The "Scene Activation v0" capability still shows up only after having triggered a scene from FGD-212 device. Any indication you can provide on why you are thinking that this issue would have been solved with 9.30.0+ version? Thanks. |
Sorry, that recommendation is on me. I thought we added that fix for the FGD-212, but it was a different fix for a different Fibaro device. |
Checklist
Deploy method
Manually built (git clone - npm run build - npm install
Z-Wave JS UI version
9.29.0
ZwaveJS version
14.3.7
Describe the bug
FGD-212 (both FW 3.4 and 3.5) are not reporting (at beginning) Scene Activation v0 Command Class capabilities.
It will report this capability once the buttons attached to the device are clicked multiple times (triggering an actual scene).
This is problematic for users (as me) using openHAB ZWave-JS binding (under development) leveraging ZWave-JS debug JSON to introspect nodes configuration + command classes.
It looks like FGD-212 has special treatment regarding Scene Command Class which might be related to this issue.
See:
#1849
#1848
To Reproduce
Fresh Z-Wave JS UI instance hooked with Controller + 1 FGD-212 device.
Look at node info: no Scene Activation v0 reported
Then double/triple click a button attached to the FGD-212 device.
Look at node info: Scene Activation v0 is reported
Expected behavior
Scene Activation v0 capability shall be reported at the beginning so that it is exposed in debug.json which is used by 3rd-party integration to introspect and reflect node capabilities.
Additional context
No response
The text was updated successfully, but these errors were encountered: