Brisant Secure Ultion Smart Lock Quickstart Install Guide

Version: 20221021
Date: Friday, October 21, 2022
Authors: Justin Bateson

Setup
The bridge driver will automatically add this driver.
You shouldn't need to manually add this driver to the project.
Configure the Bridge
The bridge driver will configure this driver when it adds it to the project.
The only change you need to make is to add the Licence Key to the Properties field
Troubleshooting
The driver will print error messages to the Lua output window when: 
Debug Mode = Print and, 
Debug Level = 7 - Debug
Use the Lua output logs with the table below as a first step to troubleshooting.
Message	Actions	
DETECTED THAT THE IP ADDRESS HAS CHANGED UPDATE THE BRIDGE'S fCallback	Manually update the callback registered in the bridge, using the Actions tab Clear Callback List and Add Callback	
fCallback does not match an existing lock with nukiId:	Use the Actions tab Get Callback List, Clear Callback List and Add Callback to troubleshoot	
Detected change to bridge's number of locks	The bridge now has a different list of locks to what is available on the bridge. Run Actions tab Import Locks	
something went wrong. perhaps you ran out of time or pressed the button on the wrong bridge?	You have to press the button on the bridge within 30 seconds. Use Actions tab Bridge Discovery to run this process again	
Unexpected response from the bridge while authorising	Contact Brisant with the output	
DISCOVERY ERROR:	The bridge returned unexpected data. Contact Brisant with the output	
No bridges found.	Brisant do not have any bridges registered for this network. Please contact Brisant for support	
Invalid discovery data	Please contact Brisant for support	
The bridge has the maximum number of callbacks set.\n Please use Actions > Clear Callback List.\n ### WARNING This will remove all 3rd party callbacks listed above.	The bridge can only notify three network devices of a lock change. Use the Actions tab's Get, Clear and Add Callback buttons to troubleshoot.	
Failed to remove callback…	Try again to remove all the callbacks or contact Brisant for support	
…is either too long or too short	You haven't entered the correct number of characters for the Licence Key. Double check and contact Brisant for support	
Activation has failed.	Double check and contact Brisant for support	
Invalid Battery State:	The bridge is reporting unexpected data for the bridge. Contact Brisant for support	
Slave driver on binding >X< does not exist…	The bridge driver is providing data for a different lock. Confirm the bindings are correct. If this doesn't work, try re-adding the bridge driver and configure it from scratch