Available tsmEv Values

Event Id valueNameDescription
0No eventEvent data is not applicable or is unknown.
1ReservedReserved
2ReservedReserved
3ReservedReserved
4ReservedReserved
5ReservedReserved
6ReservedReserved
7State change eventis used for events that happen as result of change of state.
8Key eventis used for reactive events, for example, sensor triggered events or key presses on human interface.
9Threshold eventis used for events that happen as result of exceeding configured threshold.
10Timed eventis used for streaming event that is send using defined interval. The interval may vary from seconds to hours to days, and it is typically set by the sensor or the gateway device.
11Thing powered ONcan be sent when a thing boots up
12Thing powered OFFcan be sent when a things is being powered off
13Thing controlled reset occuredcan be sent when a thing performed controller reset
14Thing uncontrolled reset occuredcan be sent when a thing performed uncontrolled reset
15Thing firmware updatedcan be sent when a thing has performed firmware update
16Thing software configuration updatedcan be sent when a thing has updated its software configuration data
17Network connectedis used for connected event that is send when a thing connects to gateway device or to another thing (in mesh networks).
18Network disconnectedis used for disconnected event that is send when a thing disconnects from a gateway device or from an another thing (in mesh networks).
19Assistance data requestedis send from a thing to a cloud, when the thing requires additional assistance data from the cloud to perform an operation
20Assistance data responseis send as a reply to an event 19
21Power ON requestedA thing can receive this eventId as a request from cloud to power ON. This is possible to implement only on a devices that have standby functionality with network connections enabled.
22Power OFF requestedA thing can receive this eventId as a request from cloud to power OFF.
23Reset requestedA thing can receive this eventId as a request from cloud to perform power OFF -> power ON reset cycle.
24ReservedReserved
25Firmware update requestedA thing can receive this eventId as a request from cloud to perform firmware update. Firmware update parameters and data may be part of the request or the data may have been received earlier.
26Software configuration update requestedA thing can receive this eventId as a request from cloud to perform software configuration update. This request is only for low-level configuration update. For application level configurations event id 30 should be used.
27Diagnostics requestedA thing can receive this eventId as a request from cloud to enable a group of diagnostics events
28Requested diagnostic eventis used for diagnostic events that have been remotely enabled from cloud
29Error diagnostic eventis used to report critical error events to cloud
30Application profile update requestedThe cloud can send this request to a device to indicate that the device must update its behaviour based on the data received or available in the cloud.
31Application profile update responseThe response for profile update request
32Firmware information requestThe cloud can send this request to ask for firmware information from the device, such as binary version or release version.
33Firmware information responseThe response for firmware information request
34Timed diagnostics eventis used for periodic diagnostic events
35Command requestis used for commands sent to device.
36Command responseis used for command responses sent from device.
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information