Add an Axis I/O device to a Site

An Axis I/O device gives a Site inputs, such as a door contact, and outputs, such as a relay for a light or buzzer. After adding one, set up and test its ports in Wire and test Axis inputs and outputs, and switch an output on its own in Switch a Site output from an alarm rule.

Before you start

• Site I/O control must be included in your portal. Kalytera enables it on request. Check under Settings > Portal profile > Enabled features.
• Cloud reaches the device directly, or through a Bridge Agent on a computer in the Site's network, which needs the Bridge Agents feature: see Bridge Agent. You choose between them only once a Bridge Agent is enrolled.
• Adding and configuring a device needs Configure Site control devices and Cloud arming policies, which administrators have. People who switch outputs need Operate Site outputs: see Roles and permissions.

Prepare the Axis device

Cloud takes the ports' setup from the device and checks every reading against it.

1. Give the device a fixed IP address on the Site's network.
2. Create a user account on the device for Cloud only, with a strong password and the rights to read its settings and switch its ports. To change port settings from Cloud later, give it administrator rights.
3. Set each port you will use to Input or Output, with its normal state, open or closed circuit.
4. Set each output to bistable (maintained) mode, or to a pulse of 1 to 65 seconds timed by the device. Cloud cannot use an output in another mode.

To check the ports, open http://<device-address>/axis-cgi/param.cgi?action=list&group=IOPort in a browser signed in to the device. For each port, Direction must read input or output; an input's Input.Trig and an output's Output.Active must read open or closed; and an output's Output.Mode must read bistable, or monostable with an Output.DelayTime of 1 to 65. Port I0 is the device's port 1, I1 its port 2, and so on.

Add the device

1. Open Sites, select the Site's name, and open the Equipment tab. If the Site has other equipment, select I/O devices.
2. Select Add device. The Add a device dialog opens.
3. If it shows Connection, choose Cloud connects directly or Through a Bridge. Through a Bridge, select the Bridge Agent on the device's network under Enrolled Bridge Agent.
4. Enter the device's IP address, and its Port only if the device does not use the usual one.
5. Enter the Device username and Device password of the account you created.
6. For a direct connection, select Test connection. It answers Connected: with the device's model, serial number and HTTPS or HTTP, or says what failed, such as The device refused the username or password.
7. Select Add device.

A device added directly is in service at once: the page says “Device added.” Through a Bridge, it says “Device added. It's in service once its Bridge reaches it.” Until the Bridge's first reading, the device shows Connecting and “Waiting for the device to answer.” Its line then shows Serial: and Firmware: as the device reports them. If the reply was lost, the page says “Creation unconfirmed; the device may have been saved.” Select Refresh devices and check the list before you add it again. A device already in service is refused with “This device is already added.”

Every input and output the device reports then appears as Input 1, Output 2 and so on, numbered as on the device, with Use in Cloud on. Adding a device switches no output, and its inputs raise no alarms until you choose when.

A direct connection

Cloud tries HTTPS first, then HTTP. Without a port, it uses 443 for HTTPS and 80 for HTTP; another port must be 1024 or higher, and not one used for databases or remote administration. It accepts a certificate the device issued itself and remembers it. When the device refuses the username or password, Cloud does not try HTTP.

By default the address must be public, which makes the device reachable from the internet: use HTTPS, a strong device-only password and, if you can, a firewall rule limited to Cloud. A private address works only on a network this server allows; ask Kalytera whether yours is allowed.

Through a Bridge

The address must be a private one on the Site's network. The Bridge uses HTTPS on port 443 and HTTP on any other port, 80 when you leave Port empty. Over HTTPS, the device's certificate must be one the Bridge's computer trusts, so a certificate the device issued itself is refused. On the Site's network, use HTTP, let the device accept it without redirecting to HTTPS, and allow Digest authentication.