Thingsee messages are created using open CBOR binary data serialization. This page has a list of all properties that are, at the moment, available for CBOR message content. New properties are added based on need.
There are ways to make any sensor connected and managed through the open API, so that the application & services creators can focus on creating their stuff instead of worrying about the hardware Thingsee Open Device API is a low-level API and message description for IoT device vendors.
Requirements When creating Wirepas sensors the following requirements are expected
the sensor will use minimum of Wirepas 5.0 The sensor will use Wirepas endpoint 21 for the Thingsee messages The sensor will support at least the minimum set of Thingsee Common Messages Optional functionality the sensor may support Thingsee heart-beat mechanism Minimum set of Thingsee Common Messages to be listed here
Thingsee Open Service APIs are included in both Thingsee Operations Cloud and Thingsee Operations Edge. Thingsee Operations Cloud is the master version of the API, and the on-premises version (edge version) implements a subset of the features.
DeploymentGroups are created, managed and assigned through Thingsee Open Services API. The responsibility of the management operations are under customer; this can be done from mobile applications (installer application) or from the customer cloud.
If you decide to use Thingsee Open Services API then these are the sequences and requirements that you should follow. It is not mandatory to follow all these sequences and you are allowed to be more creative than this.
Create client access token [POST /auth/client-token]
Since 2020 Mid release Creates a temporary access token for accessing other APIs Token expires in 15 mins and can be recreated at any point Supports multiple simultaneous tokens Request