Most of the messages below have an index parameter that can be used to indicate which of several SECO (sensor/control) units on a node originated the event. Set to zero if the node only control one item.

This is a general event of no special type.

A button has been pressed/released.

A mouse movement has occurred.

A node indicates that a condition is in its on state. Heater on, lights on are two examples.

Byte 0 is often used as an index for channels within a module.

A node indicates that a condition is in its off state. Heater off, lights off are two examples.

A node tells the world that it is alive.

A node tells the world that it is terminating.

A node indicates that an open has occurred. This can be a door/window open, a modem line open etc.

A node indicates that a close has occurred. This can be a door/window close, a modem line closure etc.

Heartbeats can be used to indicate that a unit is alive or to send periodic data. This can be sent out at predefined intervals to indicate that the node is alive, however, it does not necessarily mean the node is functioning as it should. It simply states that the node is connected to the network. To check if a node is functioning, other properties such as a measurement event or registry should be used.
This event should be sent as a response to a “Segment Status Heartbeat” (CLASS1.PROTOCOL, Type=1) in order to provide a method of finding out what is connected to the network.
The data bytes from byte 3 and forward can be used to send a descriptive/user friendly name if desired.

Not mandatory but it is recommended that all nodes send this event on regular intervals.

This indicates that the node has a condition that is below a configurable limit.

This indicates that the node has a condition that is above a configurable limit.

This can be used for slow pulse counts. This can be an S0-pulse interface or something similar.

A node indicates that an error occurred.

A node indicates that it has resumed operation.

A node indicates that it has paused.

Reserved for future use.

The system should enter its morning state. This can be a user pressing a button to set his/her house to it's morning state.

The system should enter its day state. This can be a user pressing a button to set his/her house to it's day state.

The system should enter its afternoon state. This can be a user pressing a button to set his/her house to it's afternoon state.

The system should enter its evening state. This can be a user pressing a button to set his/her house to it's evening state.

The system should enter its night state. This can be a user pressing a button to set his/her house to it's night state.

The system should be on a temporary alert. This can be a user locking the door to go out to the waste bin or similar situation. An alarm system should not be activated in this situation.

The system should be on a goodbye alert. This can be a user locking the door to go out for a day’s work or similar situation. All alarm systems should be activated in this situation.

A node indicates that a stop event occurred. This can for example be a motor stopping.

A node indicates that a start event occurred. This can be a motor starting.

A node indicates that a reset occurred. This can be a node doing a warm start.

A node indicates that a reset occurred. This can also be a node doing a warm start.

A node indicates that a sleep event occurred. This can be a node going to its inactive state.

A node indicates that a wakeup event occurred. This can be a node going to it awake state.

A node indicates that the system should enter its dusk state.

A node indicates that the system should enter its dawn state.

A node indicates that its active.

A node indicates that its inactive.

A node indicates that its busy.

A node indicates that its idle.

A steam of information from a node can be reported with this event. This can be a serial RS- 232 channel or som other sequential stream.

This event is used for cards, RFID's, iButtons, GSM phones and other identification devices. The event is generated when the token device is attached/detached to/from the system. Level II has a counterpart to this event that can take more data. CLASS2.INFORMATION Type=1

Depending on the Token device type a number of this event are sent on the segment with frame index increase for each event. The total expected number can be decuced from the type.

A steam of information from a node can be reported with this event. This can be a serial RS- 232 channel or som other sequential stream.

This event can be used as a general confirm event for zoned and stream data.

Response/confirmation from ex. a dimmer control after a dimmer command or some other unit that change a level.

A node indicates that a warning condition occurred.

A node indicates that a state change has occured. Th numerical id for the current state and the state that is about to become active is supplied.

A node optionally indicates that an action has beed triggered by this event.

A node indicates that sunrise is detected/calculated.

A node indicates that sunset is detected/calculated.

This event is used to mark the start of a multiframe data transfer. This can typically be a GPS received which sends a train of events from one GPS record. The index byte can be used to distinguish record between each other.

This event is used to mark the end of a multiframe data transfer. The index byte can be used to distinguish record between each other.

This event is used to tell the system that a pre-set configuration is active. Usually a response from a node after a CLASS1.CONTROL, Type=28 has been received by a node.

This event is used to tell the system that a detection of some kind has occurred.

The first byte is used as an index if a module have several channels or detectors.

This event is used to tell the system that an overflow of some kind has occurred.

The first byte is used as an index if a module have several channels.