Checkin
Those endpoints perform check-in procedures, a'ka firmware verification and setup of RTC based on trusted data.
These two endpoints are wide open and do not need any authorization data.
Phase 1 - Challange
Checkin challange
GET
https://my.ence.do/api/system/checkin
Get a device checkin challenge data.
Response data for successful operation
Name | Type | Description |
---|---|---|
| String | Check-In challenge data generated by HEM |
Phase 2 - Response
Checkin response
POST
https://my.ence.do/api/system/checkin
Process server response for the device check
challenge.
Headers
Name | Type | Description |
---|---|---|
Content-Type* | String | application/json |
Request Body
Name | Type | Description |
---|---|---|
checked* | String | Checkin data sent by backend server |
Response data for successful operation
Name | Type | Description |
---|---|---|
| String | Status of x509 certificate update. |
| String | Info about new firmware version. |
| String | Info about new Manager version (on Encedo PPA only). |
| String | Checkin status - general information. |
Log entries
Event | Result | Source |
---|---|---|
LOG_TYPE_RTC_SET | LOG_RESULT_OK | 200 (if RTC is been updated) |
LOG_TYPE_SHUTDOWN | LOG_RESULT_OK | 200 (if the device shutdown or locked) |
Last updated