Inputs

Only one match (one row) is enough for the driver to handle the event. For input event, there are a lot of variations for different vendors. Each Response can contain more than one Source and more than one Data inputs (i.e., 2 rows in the table has two datasets, which means that both will have to correspond to the information in the response).

In the Management Client there are two events:

  • Driver events: “Input Rising event” and “Input Falling event”.

  • Rule events: “Input Activated” and “Input Deactivated”.

Topic

Source 1

Data 1

Key

Data 2

Name

Value

Name

Value

Name

Value

Name

Value

DigitalInput

InputToken

(inputToken)

LogicalState

(negation)

DigitalInput

DigitalInputToken

(inputToken)

LogicalState

(negation)

DigitalInput

Index

(input)

Level

(negation)

VivoDigitalInput

Index

(input)

Level

(negation)

IO/Change/Port

 *read the note

port

(input)

flank

(negation)

Token

(inputNumber)

flank

(negation)

IO/State/Port

app

io

state

(negation)

port

(input)

AlarmIn

AlarmInToken

(inputToken)

State

(negation)

BinaryInput

BinaryInputToken

(inputToken)

State

(negation)

UserAlarm

AlarmID

(inputNumber)

LogicalState

(negation)

IO/Port

port

(inputNumber)

state

(negation)

IO/Port

port

(input)

state

(negation)

DigitalInput

DigitalInputToken

(inputToken)

State

(negation)

AuxIn

Token

(inputToken)

Value

(negation)

Trigger/Relay

RelayInputToken

(inputToken)

LogicalState

(negation)

The ONVIF driver checks the data value for any of the predefined negative values and depending on the result triggers “Rising” or “Falling” event. If the Data field is missing the event will still be triggered but may not be turned off. In this case there is only “Rising” event, without a “Falling” event.

An empty “Name” in “Source” is a problem for multi-input devices, but it is still possible for single input devices. This is not good practice.