The Notifications section allows users to manage all of the device, user and account-wide notifications that can be received when certain events occur. A Notification is a request to receive an alert when something happens. For example, users may want to get a text message notification when a specific access user unlocks a door, or get notified when anything happens on a specific lock.
Setting up Notifications is a two-step process:
- First, Contacts must be created. These are phone numbers and email addresses where the Notifications can be sent.
- Next, a Notification (a request to receive an alert when something occurs) needs to be created so that when a specific event or set of events occur, a Notification is sent to a specified Contact (email or text).
After clicking into the Notifications main tab, you will see a list of any notifications already created for the account. You can also Add new notifications by clicking the Add Notification button. The Contacts tab allows you to edit or add the email and cell phone numbers where notifications can be sent. The Notification History tab shows a history of any notification sent out from your account.
Before Notifications can be received, Contacts must first be added to the system. Contacts are email addresses and phone numbers for text messages. Under the Contacts tab, there are three sub-tabs for the three types of contacts that can be added; Email, Text & Webhook.
To add a Subscriber, first select the type of subscriber you want to create; Email, Text message (phone number), or Webhook.
What's a Webhook? Honestly, if you don't know you probably won't need to use it. It's something for nerdy developer types ;) Webhooks allow you to build or set up integrations which subscribe to certain events on RemoteLock's webservice. When one of those events is triggered, we'll send an HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external software system.
Notifications (Also called "Alerts") can be set up for an Access User can either be set up here from the Access User management page, or from the global Notifications manager section.
In order to receive a notification when an Access User unlocks a door, account managers need to set a "Notification Subscription" to receive notifications to a particular "Contact". A Contact can be an email address or cell phone number where the notification is sent.
Before a Notification can be set, Contacts (email addresses or phone numbers) must be previously set up by navigating to the main Notifications section, then selecting Add Contact.
Please note, additional notifications are made available to Premium and Pro Billing plan customers.
The following notifications are available for the Basic Plan: connectivity,power_level_low, access_guest_late_sync, access_person_sync_failed
The following notifications are available for the Premium Plan: connectivity, power_level_low, access_guest_late_sync, access_person_used, access_person_sync_failed, access_person_synced, acs_door_opened, acs_door_closed, acs_door_held_open, acs_requested_to_exit, unlocked, locked,access_denied, temperature_changed, humidity_changed, relay_enabled, relay_disabled, reset
To begin, click on the Add Notification button. In the pop-up screen, select the Contact type (Email, Text message or webhook), then select the contact from the drop-down.
Next, select the "Source". This is the entity that will trigger the notification. You can select "Account" if you want anything from the account to trigger an alert for the chosen event. Or, you can select an individual lock, location, access user, access guest, ACS reader, Thermostat, or Power Plug if you want the events that the user or device trigger to create a notification.
Finally, select the type of Events that you want to be notified on out of the available list. For example, click on Access granted to receive a notification when a particular access user unlocks a door. The list of events available will depend on the source selection.
Click Create to save your Notification.
Low Battery Alerts
Alerts can be created for devices showing low battery voltage. However, the correct battery type is required for low battery alerts to work properly. Within each lock's settings tab, there is a setting for Power Source. The choices include Alkaline and Lithium batteries.
This setting needs to reflect the type of batteries in the lock because each battery type has a significantly different end of life voltage curve. Many factors contribute to determining a batteries end of life, but our system needs to key off of the voltage reported. Although lithium batteries usually last much longer than alkaline batteries, battery failure (low battery) occurs very quickly after reported voltage drops below 5 volts (opposed to 4 volts for alkaline). As a result, our system has a different alert point depending upon battery type.
Low Power Notifications are initially sent when the device reports battery at 30% or less. Once the battery has reached 30%, we will send additional low power notifications once per week until the device is dead.
Battery life is monitored from our end in voltage and will report as 0% when voltage reads 3.5 on alkaline batteries and 4.8 on lithium batteries.
To create a Low Battery Alert
- Click Add Notification from the main Notification menu
- Set Subscriber to receive the alert
- Select the Publisher
- Account: Select Account to receive low battery alerts for any device that reports low batteries within the entire account
- Location: Select Location to receive low battery alerts for any device that reports low batteries within a specific Location
- Lock: Select Lock to specify one specific lock to receive low battery alerts from
- For Events, select "Power level low"
Connectivity (or offline) alerts are intended to notify users when a device hasn't connected to the system in an amount of time that indicates a problem. From time to time, a device may miss a regularly scheduled Heart Beat due to any number of issues like high traffic on a router, low signal strength, etc. In order to not create false alarms, we therefore set the alert point at 2 times the heartbeat interval. For example, if you have your heartbeat interval set for 1 hour, we do not send an alert until the lock has not checked in for over 2 hours. When a device comes back online, the system sends another alert to indicate the connection.