Lares4
The KSENIA lares 4.0 is a multi-area security system. The I/O Server has been tested on unit with firmware version 1.72.2. Actually this driver runs only in HTTP mode (port 80 is set by default).
Configuration from Ksenia cloud
Section titled “Configuration from Ksenia cloud”You must firstly configure your panel in the web app at the following address https://<panel_ip_address> (the panel starts in DHCP mode so you have to find the relative IP address assigned). In the web app, select your panel and log into it with installer privileges, then go to settings. In network settings, disable DHCP mode and set a static ip address, then disable HTTPS connection (you must unflag protocol TLS in "Web Server" section and select port 80). When you have finished save your configuration. In alternative, you can configure your panel passing by Ksenia SecureWeb cloud.
ATTENTION: this driver works only with Lares4 firmware version 1.72.2 or higher. You can download the latest firmware version from Kseniasecurity.com in the reserved area.
HSYCO Configuration
Section titled “HSYCO Configuration”Add a LARES4 I/O Server in the I/O Servers section of the Settings and set its parameters:
Communication
Section titled “Communication”- IP Address: host name or IP address of the panel
- IP Port: leave it blank
Authentication
Section titled “Authentication”- Password: pin to access the web server with user privileges (NOT installer!)
High Availability
Section titled “High Availability”- Shutdown when inactive: defaults to false.
Options
Section titled “Options”| ID | Default | Values | Description |
|---|---|---|---|
| startupevents | false | true | generate IO events also during the driver’s start-up phase |
| false | start generating events only after HSYCO is aligned with the current status of the system | ||
| pollinterval | 1000 | n > 1000 | the data acquisition interval, in milliseconds |
| logsize | 50 | 0 ≤ n ≤ 300 | the number of log lines to display in the UI object |
| gui | true | true | enable the UISET "visible" field for all partition zones |
| false | disable the UISET "visible" field for all partition zones | ||
| maxpartitions | 3 | 1≤n≤30 | number of partitions that are configured in the security panel |
Datapoints
Section titled “Datapoints”| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | connection established |
| offline | R | HSYCO can't connect to the panel | |
| armed | 1 | W | arm all partitions in the system |
| 0 | W | disarm all partitions in the system | |
| p<n>.desc | <text> | R | description of partition <n> |
| p<n>.armed | 0 | R | partition <n> is disarmed |
| W | disarm partition <n> | ||
| 1 | R | partition <n> is armed | |
| W | arm partition <n> | ||
| p<n>.alarm | 0 | R | partition <n> not in alarm |
| 1 | R | partition <n> in alarm | |
| mem | R | partition <n> in alarm memory state | |
| p<n>.tamper | 0 | R | partition <n> not in tamper |
| 1 | R | partition <n> in tamper | |
| mem | R | partition <n> in tamper memory state | |
| z<n>.desc | <text> | R | description of zone <n> |
| z<n>.alarm | 0 | R | zone <n> not in alarm |
| 1 | R | zone <n> in alarm | |
| z<n>.mask | 0 | R | zone <n> not masked |
| 1 | R | zone <n> masked | |
| z<n>.tamper | 0 | R | zone <n> not in tamper |
| 1 | R | zone <n> in tamper | |
| z<n>.error | 0 | R | zone <n> not in error |
| 1 | R | zone <n> in error | |
| z<n>.bypass | 0 | R | zone <n> is not bypassed |
| W | unbypass zone <n> | ||
| 1 | R | zone <n> is bypassed | |
| W | bypass zone <n> | ||
| o<n>.desc | <text> | R | description of output <n> |
| o<n> | 0 | R | output <n> is off |
| W | turn off output <n> | ||
| 1 | R | output n <n> is on | |
| W | turn on output <n> | ||
| voltage.low | 0 | R | system voltage is ok |
| 1 | R | system voltage is low | |
| batt.low | 0 | R | battery is ok |
| 1 | R | battery is low | |
| batt.fault | 0 | R | battery is ok |
| 1 | R | battery fault | |
| pstn.fault | 0 | R | pstn is ok |
| 1 | R | pstn fault | |
| credit.low | 0 | R | credit is ok |
| 1 | R | credit is low | |
| system.fault | 0 | R | system is ok |
| 1 | R | system fault | |
| mobile.fault | 0 | R | mobile is ok |
| 1 | R | mobile fault | |
| s<n>.desc | <text> | R | description of scenario <n> |
| s<n> | 1 | W | trigger scenario <n> |
| g<n>.desc | <text> | R | description of gate <n> |
| g<n>.status | <text> | R | raw status of gate <n>, in lower case (enabled, open, open_fd, open_dotl, ...) |
| g<n>.open | 0 | R | gate <n> is closed |
| 1 | R | gate <n> is open | |
| W | open gate <n> (momentary command) | ||
| g<n>.forced | 0 | R | gate <n> not forced open |
| 1 | R | gate <n> forced open | |
| g<n>.dotl | 0 | R | gate <n> not in door open too long state |
| 1 | R | gate <n> in door open too long state | |
| g<n>.byp_dotl | 0 | R | door open too long bypass not active on gate <n> |
| 1 | R | door open too long bypass active on gate <n> | |
| W | bypass the door open too long alarm on gate <n> | ||
| na | R | door open too long bypass not available on gate <n> | |
| u<n>.desc | <text> | R | description of account <n> |
| u<n>.auth | <text> | R | authorization status of account <n>, in lower case (authorized, ...) |
| log0 | <text> | R | last log line generated by the panel; automatically cleared to an empty string after 5 seconds |
The g<n>.open and g<n>.byp_dotl datapoints only accept the value 1 in write: they are momentary commands, the written value is not stored.
Note that g<n>.open reflects the actual state of the gate as reported by the panel, not the command sent to it. When you send the open command, the panel generates a momentary opening and the gate status typically goes back to enabled immediately, so g<n>.open may well stay at 0. It goes to 1 when the gate is really open, for example when it is kept open manually.
The u<n>.desc datapoints are read from the panel configuration, that may not be available when connecting with a USER role login. In that case only u<n>.auth is generated.
User Interface
Section titled “User Interface”Lares4 Object
Section titled “Lares4 Object”The user interface for the Lares4 multi-area intrusion detection system:
The first image shows the list of configured partitions. You can set the alarm for all the partitions, otherwise you can open a popup on a dedicated partition and set the alarm only for that one. The two icons on the top of the page represent in order: partition tamper (at least one partition is in tamper state), partition alarm (at least one partition is in alarm state).
The second image shows the popup associated to a zone; the four icons shown inside the popup represent in order: zone alarm, zone tamper, zone bypassed, zone fault. Inside the popup you can bypass/unbypass the selected zone.
The (lares4) object is listed in the Project Editor’s new object list only when at least one Lares4 I/O Server is defined
Parameters
Section titled “Parameters”- server id: the server ID. Supports Redirect variables
- position: the object's position. Use the pixels or rows and columns coordinates format
Syntax
Section titled “Syntax”(lares4 <server id>; <position>)
E.g.
(lares4 lares; x10y20)
UISET Actions
Section titled “UISET Actions”| ID | Attribute | Set to | |
|---|---|---|---|
| log | value | latest security log lines (as many as specified by the 'logsize' option) | |
| log0 | value | latest security log (it will vanish after 5 seconds) | |
| access.log | value | latest access log lines (as many as specified by the 'logsize' option) | |
| access.log0 | value | latest access log (it will vanish after 5 seconds) | |
| z<n>.tamper | visible | false | zone n not in tampering |
| true | zone n in tampering | ||
| z<n>.bypass | visible | false | zone n not bypassed |
| true | zone n bypassed | ||
| z<n>.alarm | visible | false | zone n not in alarm |
| true | zone n in alarm | ||
| z<n>.error | visible | false | zone n not in error state |
| true | zone n in error state | ||
| z<n>.mask | visible | false | zone n not masked |
| true | zone n masked | ||
Log Files
Section titled “Log Files”If a Ksenia anti-intrusion unit is connected to HSYCO, the security.log file will be written in the same directories as the daily log files.
This file is never overwritten or deleted from HSYCO SERVER.
2018.02.20 16:59:28.516 - lares - 20/02/2018 16:56:36 - Disinserimento - Part 1 - U1
2018.02.20 17:00:24.527 - lares - 20/02/2018 16:57:36 - Inserimento - Part 1 - U1
2018.02.20 17:00:44.318 - lares - 20/02/2018 16:57:57 - Allarme - Zone 1
2018.02.20 17:00:49.241 - lares - 20/02/2018 16:57:58 - Ripristino - Zone 1
2018.02.20 17:00:54.043 - lares - 20/02/2018 16:58:06 - Disinserimento - Part 1 - U1
2018.02.20 17:01:18.905 - lares - 20/02/2018 16:58:29 - Fallita Comunicazione - Leonardo - Vocale GSM
2018.02.20 17:01:29.053 - lares - 20/02/2018 16:58:40 - Fallita Comunicazione - Leonardo - SMS
Other information about the Ksenia driver are stored in the message.log daily file.
Access Logs
Section titled “Access Logs”The driver also retrieves the access control events history from the panel. At start-up the existing history is downloaded from the panel, then new events are received in real time.
The following event types are collected: gate opening, gate forced open, gate open too long, valid code, valid key, invalid code, installer connection and user modification.
Access events are written to the security.log file, marked with the [access] tag, and are displayed in the UI object. The number of lines kept in the history is set by the logsize option.
2026.07.10 09:12:04.318 - lares4 [access] - 10/07/2026 09:12:03 - GATEOPEN - Gate 1 (Hsyco)
Release Notes
Section titled “Release Notes”3.10.1
Section titled “3.10.1”- added support for gates
- added support for access logs
- added support for accounts
- the log0 datapoint now mirrors the last log line displayed in the UI object
- communication with panel now based on asynchronous protocol
- polling discontinued, pollinterval attribute will be ignored
- changed default log size to 50 lines, max 300 lines
- minor bug fixes and optimization
- initial version release
Ksenia is a registered trademark of Ksenia Security s.r.l.