Password - The password used to connect to (opens new window)
Only the bridge require manual configuration. # DiscoveryĪfter the configuration of the Verisure Bridge all of the available Sensors, Alarms, SmartPlugs, SmartLocks, Climate and Mice Detection devices will be discovered and placed as things in the inbox. NOTE: To be able to have full control over all SmartLock functionality, the user has to have Administrator rights. You must also configure your pin-code(s) to be able to lock/unlock the SmartLock(s) and arm/unarm the Alarm(s). You will have to configure the bridge with username and password, these must be the same credentials as used when logging into (opens new window). This binding supports the following thing types:
This binding uses the rest API behind the Verisure My Pages:īe aware that Verisure don't approve if you update to often, I have gotten no complaints running with a 10 minutes update interval, but officially you should use 30 minutes. In Confirmation, click Configure to apply your selections, and then click Close.This is an openHAB binding for Verisure Alarm System, by Securitas Direct. If you specify locations other than the default locations, ensure that the folders are secured with access control lists (ACLs) that prevent unauthorized users or computers from accessing the CA database and log files. On the CA Database page, in Specify the database locations, specify the folder location for the certificate database and the certificate database log. The default setting of five years is recommended. On the Validity Period page, in Specify the validity period, type the number and select a time value (Years, Months, Weeks, or Days). Ensure that you are certain the CA name is compatible with your naming conventions and purposes, because you cannot change the CA name after you have installed AD CS. On the CA Name page, keep the suggested common name for the CA or change the name according to your requirements. It is recommended that you keep the default setting of 2048. Large key character lengths provide optimal security however, they can impact server performance and might not be compatible with legacy applications.
On the Cryptography for CA page, keep the default settings for CSP ( RSA#Microsoft Software Key Storage Provider) and hash algorithm ( SHA2), and determine the best key character length for your deployment. On the Specify the type of the private key page, verify that Create a new private key is selected, and then click Next. On the Specify the type of the CA page, verify that Root CA is selected, and then click Next. On the Setup Type page, verify that Enterprise CA is selected, and then click Next. In Role Services, click Certification Authority, and then click Next. Read the credentials information and, if needed, provide the credentials for an account that is a member of the Enterprise Admins group. When installation is complete, click Configure Active Directory Certificate Services on the destination server. Do not close the wizard during the installation process. In Confirm installation selections, click Install. In Active Directory Certificate Services, read the provided information, and then click Next. When you are prompted to add required features, click Add Features, and then click Next. In Select Server Roles, in Roles, select Active Directory Certificate Services. In Server Pool, ensure that the local computer is selected. In Select destination server, ensure that Select a server from the server pool is selected. In Select Installation Type, ensure that Role-Based or feature-based installation is selected, and then click Next. The Before You Begin page of the Add Roles and Features Wizard is not displayed if you have previously selected Skip this page by default when the Add Roles and Features Wizard was run.