Sensor Meta¶
event¶
EnOcean SmartStudio provides important information about events that were detected in regard to the sensor status, data transmission or behavior.
There are these types of events:
| Type | Event | Description |
|---|---|---|
| Security | MAC_VALIDATION_ERROR |
A received message could not be authentificated with the included CMAC. This could be an indication for a security attack. |
RLC_REPLAY |
A received message has a lower message sequence counter then the previous. This could e an indication for an replay attack. | |
DEVICE_SEND_NOW_UNSECURE |
A device which was onboarded as secure is now transmitting as non secure. This is an indication of compromision the set security level, possible attack. | |
| Health | FIRST_TIME_SEND |
An onboarded device transmitted for the first time. |
| Processing | EEP_DECODE_ERROR |
The receive message could not be decoded with the specified EEP. This is an indication for an corrupted radio message (if occuring on limited basis) or wrong specified EEP (if occuring pernament). |
EEP_NOT_FOUND_ERROR |
The specified EEP of an device is not known to EnOcean SmartStudio. Please contact our support in such case. |
Example of an Health FIRST_TIME_SEND message is below:
json
{
"sensor": {
"friendlyID": "Multisensor 1",
"id": "04138d23",
"location": "Cloud center",
"eep": "d2-14-41",
"customTag": ""
},
"meta": {
"events": {
"security": [],
"health": [
{
"code": "FIRST_TIME_SEND",
"message": "First time send of device with id=04138d23."
}
],
"transcoding": []
},
"stats": {
"timestamp": "1637770981"
}
}
}
stats¶
The telegrams stats of individual EnOcean devices are posted periodically. This should indicate their operational status and additionally provide operational updates.
Example of an stats message is listed below:
json
{
"sensor": {
"friendlyID": "Multisensor 1",
"id": "04138d23",
"location": "Cloud center",
"eep": "d2-14-41",
"customTag": ""
},
"meta": {
"stats": {
"lastSeen": "1637827538",
"notProcessed": 1,
"succesfullyProcessed": 6,
"totalTelegramCount": 0
}
}
}