Replies: 1 comment 3 replies
-
If setting a multichannel lifeline association on the root device, the controller is implicitly telling the device that the destination support multichannel, and the device will send lifeline reporting from the endpoints multichannel encapsulated. It is not necessary to set lifeline associations on the individual endpoints. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@hanskroner this one is motivated by #1721
In zwave-js, all lifeline associations are created on the root device, even if endpoints support Multi Channel Associations.
When receiving an unsolicited report from endpoint 0 by a device that supports the same CC on an endpoint and does not support MCA V3 (because in that case, no Multi Channel Lifelines are configured), we map those reports to endpoint 1.
In the above issue, the device supports MCA V3 on the root device and endpoint 1. However, it sends unsolicited reports from endpoint 0, but multi channel encapsulated (which is not allowed, but zwave-js does not care):
Since it supports MCA v3, the report is not mapped to endpoint 1 and thus silently ignored.
Should this be mapped anyways? Or could this wrong report caused by the fact that we're not setting up the association on endpoint 1?
Beta Was this translation helpful? Give feedback.
All reactions