Device capabilities
A device can define how future communication with Data Orchestrator will take place by specifying capabilities. Interacting with astarte to set capabilities works as follows:
- A device can send one or more capabilities at a time.
- If a capability is not explicitly set, its default value is used.
- When a device sends a capabilities message, two things can happen. Either the message is valid and the new values override the current ones, or the message was malformed. In this case the following happens:
- the previously stored values remain unchanged;
- the device gets forcefully disconnected.
- Capabilities are preserved in the database, ensuring consistency across sessions.
Capabilities List
The following is a comprehensive list of all capabilities currently implemented. In the possible values column the default value is marked in bold.
| Name | Values | Purpose |
|---|---|---|
purge_properties_compression_format | "zlib", "plaintext" | Set if Data Orchestrator should send the purge properties payload compressed with zlib or in plaintext |