-
-
Notifications
You must be signed in to change notification settings - Fork 672
fix(config): correct Fibaro FGMS001 association groups #7463
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
Conversation
https://manuals.fibaro.com/motion-sensor/ Group information: 1st Association Group – “Lifeline” reports the device status and allows for assigning single device only (main controller by default). 2nd Association Group – “Motion” is assigned to the motion sensor – sends motion detection and alarm cancellation frames to the associated devices. 3rd Association Group – “Tamper” is assigned to the tamper – sends tamper alarm and alarm cancellation frames to the associated devices. 4th Association Group – “Motion BC” is assigned to the motion sensor – sends motion detection and alarm cancellation frames to the associated devices. Provides backward compatibility with controllers not supporting Z-Wave+ protocol. 5th Association Group – “Tamper BC” is assigned to the tamper – sends tamper alarm and alarm cancellation frames to the associated devices. Provides backward compatibility with controllers not supporting Z-Wave+ protocol.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been having lots of problems with this incorrect file, but the changes to the definitions of the groups seems correct now. Please someone with the correct permissions provide an approving review so it can be merged. Thanks!
Thanks! |
@AlCalzone My bad, I thought I had to merge the PR, but by closing it I disabled the auto merge. |
I had a lot of trouble with setting up associations with my FGMS001 motion sensor from Fibaro.
Turns out the configuration in the documentation was incorrect. After reviewing the documentation at https://manuals.fibaro.com/motion-sensor/ I came to the conclusion ZwaveJS was reporting the associations groups incorrectly.
ZwaveJS documentation link: https://devices.zwave-js.io/?jumpTo=0x010f:0x0800:0x1001:0.0#
This PR corrects the association group names and limits.
Group information:
1st Association Group – “Lifeline” reports the device status and allows for assigning single device only (main controller by default).
2nd Association Group – “Motion” is assigned to the motion sensor – sends motion detection and alarm cancellation frames to the associated devices.
3rd Association Group – “Tamper” is assigned to the tamper – sends tamper alarm and alarm cancellation frames to the associated devices.
4th Association Group – “Motion BC” is assigned to the motion sensor – sends motion detection and alarm cancellation frames to the associated devices. Provides backward compatibility with controllers not supporting Z-Wave+ protocol.
5th Association Group – “Tamper BC” is assigned to the tamper – sends tamper alarm and alarm cancellation frames to the associated devices. Provides backward compatibility with controllers not supporting Z-Wave+ protocol.