Cloud Application & Management

As OSS is built for sensor-to-cloud applications, cloud connectivity allows both access to sensor data and management of deployed OSS devices.

Self-Hosted vs Tibbo-Hosted Cloud

OSS' cloud functionality can be self-hosted, meaning you set up and configure your own Azure account, or Tibbo-hosted, meaning your data is stored securely in Tibbo's cloud and all setup is done via the OSS Companion app. Since setup for Tibbo-hosted is virtually instantaneous, it is recommended for most users. However, the option for self-hosting is still available for users who wish to have more control over their data.

Self-Hosted Cloud Configuration

Azure is used for OSS' self-hosted cloud; see Self-Hosted Cloud for instructions.

Tibbo-Hosted Cloud Configuration

Tibbo-hosted cloud is easiest for most users; see Tibbo-Hosted Cloud for instructions.

A tip note icon. White labeling for Tibbo-Hosted Cloud is available for customers wishing to create their own branded version of OSS. Contact Tibbo for more information.

Determining Cloud vs. Close-Range Usage

Some OSS functions require close-range access to the OSS device using NFC and BLE, while others use can use cloud. Firmware upgrades can be performed both close-range and via the cloud. However, initial cloud configuration for each OSS device requires close-range setup. After the device is deployed, "close-range" implies an on-site visit.

Function	Close-Range (On-Site)	Cloud (Self-Hosted or Tibbo-Hosted)
Device Wake Up	✔
Device Configuration	✔
Model No. Setting	✔
Network Configuration	✔
Cloud Configuration	✔
Operation Mode Configuration	✔
Sensor Type Configuration	✔
Special Command Setting	✔
Diagnostics Configuration	✔
Device Reset	✔
Customer ID Retrieval	✔
Customer ID Setting	✔
Custom Data Retrieval	✔
Custom Data Setting	✔
BLE Console Access	✔
NFC Password Setting and Updating	✔
NFC Password Removal	✔	✔
Firmware Upgrading	✔	✔
Device Settings Configuration	✔	✔
Telemetry Access		✔
Device Migration		✔