With the release of HS3 API calls to maintain users in locks, the plugin can now implement the following changes:
1. Add user codes to locks
2. Delete user codes from locks
3. Get user code for a certain pin location
4. Get all user codes from lock
5. Get max users for the lock
I will be adding a new option to the options page that will allow you to turn on a "Plug-In Controlled Lock Users" option in the plugin that will allow the plugin to maintain the user codes for all locks.
NOTE
Any users that were programmed directly at the lock cannot be read by the HS3 API calls. If you added all users through the device settings in HS3 then the plugin can read them. I know some users have over a hundred users programmed into their locks. That is why I am making this new addition as an option in the plugin (it is not forced on anyone). You can leave the option disabled and the plugin will run just like it does today.
If you do choose to use the new option, then that means that the plugin will re-program your lock based on the users you have added to the plugin. I will create a process that will run that will take all of the users created in the plugin for each lock and add their codes and names to the lock using the HS3 API calls. This process could take some time depending on how many users you have created for each lock. All additional users then must be added to the lock using the plugin or else they will not be seen by the plugin.
I will need to test out all of this and I am currently waiting on a replacement lock from Weiser before I can start really testing this. It will take me some time to make all of these changes.
I welcome any feedback
UPDATE: See next post for more info
1. Add user codes to locks
2. Delete user codes from locks
3. Get user code for a certain pin location
4. Get all user codes from lock
5. Get max users for the lock
I will be adding a new option to the options page that will allow you to turn on a "Plug-In Controlled Lock Users" option in the plugin that will allow the plugin to maintain the user codes for all locks.
NOTE
Any users that were programmed directly at the lock cannot be read by the HS3 API calls. If you added all users through the device settings in HS3 then the plugin can read them. I know some users have over a hundred users programmed into their locks. That is why I am making this new addition as an option in the plugin (it is not forced on anyone). You can leave the option disabled and the plugin will run just like it does today.
If you do choose to use the new option, then that means that the plugin will re-program your lock based on the users you have added to the plugin. I will create a process that will run that will take all of the users created in the plugin for each lock and add their codes and names to the lock using the HS3 API calls. This process could take some time depending on how many users you have created for each lock. All additional users then must be added to the lock using the plugin or else they will not be seen by the plugin.
I will need to test out all of this and I am currently waiting on a replacement lock from Weiser before I can start really testing this. It will take me some time to make all of these changes.
I welcome any feedback
UPDATE: See next post for more info
Comment