feat: lock()
accepts a userId
param if it's required to complete the login
#136
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.
Related Issues
userId
#123Proposed Changes:
This change adds support for all main units that require a
userId
parameter, such as the ETR128.When the system is armed and disarmed, the
AlarmDevice
splits and sends theuserId
and thecode
if they are both required by the main unit. Thelogin_without_user_id
value from the panel details defines if the unit requires it or not.In case the
userId
is not required, that parameter is not sent. If panel details are not available, the device assumes it's not needed (true for most recent main units).Users can insert both code directly from the alarm panel simply combining first the
userId
and then thecode
.Example:
Testing:
n/a
Extra Notes (optional):
n/a
Checklist