Skip to content
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 data3 for responder records to PLM scene #328

Merged
merged 5 commits into from
Dec 19, 2013
Merged

Fix data3 for responder records to PLM scene #328

merged 5 commits into from
Dec 19, 2013

Conversation

mstovenour
Copy link
Collaborator

Fix Issue #327. This fix also applies when a responder is I2CS and the controller
is I1. Added logging for the data3 value. Aligned the logging levels between
sync_links() and update_link().

Fix Issue #327. This fix also applies when a responder is I2CS and the controller
is I1. Added logging for the data3 value. Aligned the logging levels between
sync_links() and update_link().
@krkeegan
Copy link
Collaborator

krkeegan commented Dec 6, 2013

Ahh yes, I did mix that up.

Thank you Michael for catching my error.

@mstovenour
Copy link
Collaborator Author

Ah no problem. This issue was easy to overlook in testing if you have a number of I2CS devices. Thanks for all the work on the sync_links and delete_orphan_links routines. They are significantly easier to follow.

Add link_data3() function at the device level
Modify aldb functions that set or check data3 to use the new function
Add grotesque, level 5 logging that should be removed later
mstovenour added a commit that referenced this pull request Dec 19, 2013
Move aldb link data3 logic into Insteon objects

Fix data3 for responder records to PLM scene
Add flexibility to how aldb link data3 values are specified; each Insteon device can specify a unique behavior
Update so that most Insteon objects use group 00 for endpoint 1 responder links (was 01 for all I2CS devices)
Override logic for Insteon::SwitchLincRelay to use group 01 for endpoint 1 responder links for I2CS devices
Note:  Might consider doing the same for data1 and data2 in a future update
@mstovenour mstovenour merged commit 5dd6363 into hollie:master Dec 19, 2013
@mstovenour mstovenour deleted the fix_responder_data3 branch December 19, 2013 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants