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

FGD-212 not reporting Scene Activation Command Class #4078

Open
3 tasks done
Matsuo3rd opened this issue Jan 3, 2025 · 1 comment
Open
3 tasks done

FGD-212 not reporting Scene Activation Command Class #4078

Matsuo3rd opened this issue Jan 3, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@Matsuo3rd
Copy link

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

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:
zwave-js/node-zwave-js#1849
zwave-js/node-zwave-js#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
Capture d’écran 2025-01-03 à 12 50 11

Then double/triple click a button attached to the FGD-212 device.
Look at node info: Scene Activation v0 is reported
Capture d’écran 2025-01-03 à 12 53 06

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

@robertsLando
Copy link
Member

@AlCalzone ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants