fix(config): correct Fibaro FGMS001 config to conform to Fibaro official #7463
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
xyanide
changed the title
xyanide
changed the title
xyanide
changed the title
xyanide
changed the title
xyanide
changed the title
xyanide
changed the title
manutremo
approved these changes
Dec 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.