Difference between revisions of "Mews"
| Line 51: | Line 51: | ||
== Example == | == Example == | ||
| − | In this example HSYCO is using the following format to | + | In this example HSYCO is using the following format to create a new task: |
| − | + | INIT : { | |
| − | Where " | + | var obj = new Object(); |
| − | and " | + | obj.Name = "Clean room 101"; |
| + | obj.Description = "Start cleaning the room 101 asap"; | ||
| + | obj.DeadlineUtc= "2023-02-06T18:00:00Z"; | ||
| + | obj.DepartmentId = "915fbb82-de35-48a0-9e9b-f4a7eac711bb"; | ||
| + | var jsonString = JSON.stringify(obj); | ||
| + | |||
| + | ioSet("mews.task.new", jsonString); | ||
| + | } | ||
| + | Where "DepartmentId" is the id of the department with the task is assignd to, you can get this id reading the "mews.department" datapoints in HSYCO | ||
| + | and "mews." is the name of the mews I/O Server in HSYCO | ||
== Release Notes == | == Release Notes == | ||
Revision as of 16:27, 10 February 2023
Avigilon Control Center (ACC) 7 is a video management software that can be integrated in HSYCO with a TCP/IP connection. The current release of the I/O Server has been tested with the Avigilon Control Center WebEndpoint
This driver supports only a single connection with an Avigilon Control Server. If you have multiple Avigilon Control Servers it is mandatory to add more I/O servers to HSYCO, one for each Avigilon Control Server. Every I/O server must use a different IP address and TCP/IP port.
Options
- username: Username of the AVIGILON ACC 7 client.
- password: Password of the AVIGILON ACC 7 client.
- userkey: User api key Avigilon developer page.
- usernonce: User api nonce Avigilon developer page.
- pollingtime: Time in milliseconds that hsyco will wait before the next alarm check, leave blank or set it o 0 to use default polling time 300
- usessl: Tells the driver if the webendpoint uses SSL or not, leave blank for true
Datapoints
| ID | Value | R/W | Description |
|---|---|---|---|
| connection | online | R | HSYCO connection socket is open |
| offline | R | HSYCO cannot create the connection socket | |
| <alarmName>.alarm | 0 | R | The alarm is off |
| 1 | R | The alarm is on | |
| <alarmName>.state | active, autoacknowledged, acknowledged | R | get an alarm state |
Example
In this example HSYCO is using the following format to create a new task:
INIT : {
var obj = new Object();
obj.Name = "Clean room 101";
obj.Description = "Start cleaning the room 101 asap";
obj.DeadlineUtc= "2023-02-06T18:00:00Z";
obj.DepartmentId = "915fbb82-de35-48a0-9e9b-f4a7eac711bb";
var jsonString = JSON.stringify(obj);
ioSet("mews.task.new", jsonString);
}
Where "DepartmentId" is the id of the department with the task is assignd to, you can get this id reading the "mews.department" datapoints in HSYCO and "mews." is the name of the mews I/O Server in HSYCO
Release Notes
3.8.0
- initial release
Mews is a registered trademark of Mews Systems
