12/22/2023 0 Comments Loxone login![]() Security Information on your lock’s security when using this integration Support for requesting the current lock state when the Loxone Miniserver boots. ![]() The LOQED Bridge currently cannot connect to Wi-Fi networks with special characters in the SSID network name or password (for example, the letters é or ï). If you send the “OPEN” command to a lock with only two states (DAY LOCK and NIGHTLOCK), the lock will interpret this as if it received the DAY_LOCK command. About 2 seconds after such a lock reached the OPEN state, the lock will automatically release the latch, and send the “DAY_LOCK” state to the Loxone server. The lock state “OPEN” is only available for locks without a movable handle on the outside of the door. This is normal behaviour, simply don’t send duplicate commands too fast. OPEN) twice within 10 seconds, the LOQED Touch Smart Lock will turn the lock as far as it can (an emergency opening). A workaround for this problem is to use the LOQED web API, which is secured via HTTPS.Īfter a reboot of the Loxone Miniserver, the lock status will be unknown, until the lock state changes once, or the virtual input status interval triggers. Any person or device with access to your local area network can potentially see this encryption key. Therefore, the encryption key is sent to the bridge by Loxone in plain text. At the time of writing, Loxone does not support generating such a signature. Therefore, commands to the bridge can be digitally signed, such that the LOQED bridge can validate if the message was sent by a trusted party. Open/lock commands to the LOQED Bridge: within your local network, connections cannot be secured via TLS certificates signed by a certificate authority. turn off your alarm system).Ī workaround for this problem is to use the LOQED web API, which validates the security certificate of the domain it is connecting to. This might trigger other sensitive actions depending on your situation (e.g. This means that any person or device with access to your local area network could make Loxone “think” the door was opened. However, at the time of writing, this is not yet supported by Loxone. The LOQED Bridge therefore includes a signature which could theoretically be validated by Loxone. Status updates to Loxone: within your local network, connections cannot be secured via TLS certificates signed by a certificate authority. If you cannot ensure this, we recommend using our web API instead ( Read the Web API article here). We highly recommend to only make a local integration between Loxone and LOQED if your Wi-Fi network is properly secured, and you trust all devices with access to this Wi-Fi network. Now the lock status and battery percentage will be sent to the Loxone server on every status change. ![]() Go to “Add function block -> General -> Status” and add the status block (do not use the virtual status block). So after your server will boot, it will take one hour for the status to appear if the lock itself has not been used within that first hour. Now, the Loxone server will ask the bridge for the current status every hour.Ĭurrently, there is no way to have Loxone request the current status on startup. If you get the error "Error on saving in the target location", please first make the directory "VirtualIn" in the "Loxone\Loxone Config\Templates" directory (case-sensitive).Ĭopy the 'Status' URL from the API page and paste it to 'Settings -> URL Select 'Virtual Inputs' from the Periphery list. ⬇ Download the virtual input template here To do so, you need a Virtual Input in Loxone to receive the current status. The LOQED bridge can update your Loxone server with every status change, even when the App is used, or when you manually open or close the lock. Save the configuration to your Loxone server, activate the live view with manual value adjustment, and test if the commands work.Ĭreate a virtual input to receive the lock’s status state?command=DAY_LOCK&local_key_id=&secret= Starting from /state? It should look like: Select the 'Latch' item from the Virtual OutputĬhange the 'Command for ON' to the Latch bridge API URL you created in step 1
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |