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.
This profile is meant to be used only as a demonstration and R&D specification with Thingsee based devices. Any commercial deployment or development must use its own profile.
This specification is only for development and shouldn’t be used by the clients.
Carbon Dioxide level info (24100) Returns the latest measurement value.
{ "carbonDioxide" : Number, "status" : Number } carbonDioxide is Carbon Dioxide (CO2) level as parts per million (ppm). status returns status information of the measurement.
ThingseeANG can measure angular position of arm attached to sensor.
Angular position info (18100) { "angle" : 89 } angle is angular position in degrees (0° to 360°).
Temperature info (18101) { "temp" : 59 } temperature is degrees Celsius.
Occupancy info data (2100) { "state" : Number } state is current occupancy state. Value ‘0’ means sensor area is not occupied Value ‘1’ means area is occupied.
This profile may be used as is, or be used as a basis, by all profiles to implement some generic functions that are typically required by all applications regardless of their actual use cases.