Repository navigation
Zigbee/Zwave: Add explicit index mins for lock capability defs - #3305
hcarter-775 wants to merge 2 commits into
Conversation
|
Channel deleted. |
|
zigbee-lock_coverage.xml
Minimum allowed coverage is Generated by 🐒 cobertura-action against 581819e |
|
zwave-lock_coverage.xml
Minimum allowed coverage is Generated by 🐒 cobertura-action against 581819e |
Test Results 73 files 545 suites 0s ⏱️ Results for commit 581819e. ♻️ This comment has been updated with latest results. |
| capability = capabilities.lockCredentials, | ||
| attribute = capabilities.lockCredentials.credentials, | ||
| max_entries = capabilities.lockCredentials.pinUsersSupported, | ||
| minimum = 0, |
There was a problem hiding this comment.
Before making this change, we also need to make sure that we sync the master codes from devices that already have them but either weren't present before migration or weren't synced when onboarding to the new lock experience. Otherwise the driver will see that slot 0 is available and we would have failures when writing to that index if that slot already exists but we just hadn't synced it to our capabilities yet.
|
Do we need to decouple credential index and user index in the auto case here? |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
62294d5 to
581819e
Compare
Description of Change
In Zigbee, the minimum for PIN code indices starts at 0, not 1, which was previously being skipped even though it is an allowed value. This change makes that allowable, and makes the minimum handling for other index values more explicit (though the rest were, correctly, 1).
Summary of Completed Tests
Unit tests continue to pass.