Use Remote Group When Adding Resp Link on Modem #453
Merged
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.
Proposed change
This is a significant bug fix. Not sure how long this has been an issue. I only noticed it when I had to replace a PLM.
The Issue
When pairing a multigroup device such as a keypadlinc, remote, motion, ... The responder links for the secondary groups (not 0/1) were not being added to the modem.
This was happening because
_db_update
on the modem was treating the local_group as the scene group number for responder links. Since all responder links on the modem have a local_group of0x01
this essentially meant that only one responder link would be added to the modem per device since all responder links looked the same.The Solution
The solution is to use the remote_group as the scene group number on responder links. This code is written properly for all other devices except the modem, so I just copied the same code.
Additional information
I am not sure how long this has been happening. The code I modified is 4 years old. But I believe things were working at some point. Strange
Checklist