Exosite provides the requirement functionality to not only enable your devices with IoT connectivity but to support OEMs through the device lifecycle.
An Internet connected device (Contact us for local wireless sensors connected to a gateway)
Typically the hardware is one of the following:
A computer device (typically an industrial Linux computer / gateway)
An embedded microcontroller based device running C or an embedded OS
Deploy a new IoT Connector using the one of the Templates found in the Exchange IoT Marketplace. Typical starting points:
ExoSense™️ Standard Connector Template - Includes the required API Resources needed for ExoSense
Connector-as-a-Service Template (for PDaaS) - Includes Product as a Service services and feature set
Using the IoT Connector Management area, set the required API protocol, authentication settings, and get the device API Endpoint.
Your device will need to talk to the Exosite Device API using your specific IoT Connector endpoint. Examples and references are provided and are a good place to start.
Key developer notes:
Understand Provisioning, Authentication, and device identities.
If you are using a device that runs Linux, we recommend looking at ExoEdge, a python client application that is set up to work with ExoSense and talk over the Exosite Device API protocols.