-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
fix(config): correct lifeline association and param 3 for ZWN-RSM2-PLUS #4046
Conversation
- Force Endpoint 0 for Group 1 Associations Lifeline so that CurrentValue status reports are sent and processed. - Define the one configuration parameters options as per mfg data
I think the documentation of that config setting isn't up to date. You should be able to achieve the same result by setting |
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.
Please try the suggestion, re-interview your device and post a driver log of that. I'm fine with keeping it this way if it won't work, but ideally it should.
Thank you! I was trying to figure this out, but decided to post the PR for some sage advise. I will revise, test and update in the next few days. |
Attached is the Interview log for node 38 with the suggested change in place. |
Looks OK, does it work for you? |
Just did some more testing.
No group associations were created and the configuration parameter does not show up. It is using the modified device configuration, debug for node 38 attached. |
Weird, your log did show an existing multi channel association |
I don't think that interview had the associations removed. Let me get the interview with the associations removed before starting. |
Here is the log for Node 38 Interview with associations cleared. Result, no associations created. |
Heh, the device claims it supports Multi Channel Association V2. However, being able to use 0 as the target endpoint was only added in V3 of that CC, so the driver won't do it. We need to overwrite the reported version aswell, please add that to your config file (before metadata): "compat": {
"commandClasses": {
"add": {
// The device needs a multi channel lifeline association (target endpoint 0),
// but only reports support for V2, which doesn't allow this.
"0x8e": {
"version": 3
}
}
}
} |
Updated device file and tested. Works as expected creating the correct Lifeline Association with a EndPoint Target 0. 😀 |
Fixes: #2280
status reports are sent and processed.
Did some experimentation to get this device to report manual local change (someone turns the switch off or on) and found that setting the Endpoint Target to 0 for Group 1 Association (Lifeline) did the trick. I only found one other example of Endpoint usage in device configurations, so I hope I got this correct.