Offbeat-IoT
Teach your device one protocol. Connect it to everything else.
A device connects to Offbeat-IoT with one small, common JSON protocol. Offbeat-IoT talks to the provider APIs, keeps the OAuth tokens and owns the integrations. Your firmware stays small.
The device knows exactly one thing: the Offbeat-IoT JSON protocol. Everything provider-specific happens behind Offbeat-IoT.
spotify.next.The microcontroller does not need to implement OAuth, REST APIs or provider-specific protocols. It only needs to understand the Offbeat-IoT protocol.
Skip the per-provider HTTP client, the token storage and the refresh logic. One message on one connection is enough:
{
"spotify.next": ""
}
Compare that with a hand-written Spotify client: OAuth authorization, token refresh, a TLS REST call and JSON parsing for every provider. On Offbeat-IoT the device sends the same shape for Spotify, Todoist, Google Health and the assistants.
Every command is a key on the JSON message. The provider and the credentials are handled for you.
| Device sends | Offbeat-IoT does |
|---|---|
{"spotify.next": ""} |
Skips to the next track on the connected Spotify account. |
{"tasks.create": "..."} |
Creates a Todoist task. |
{"time": ""} |
Returns the current time for the device location. |
{"setPowerState": "on"} |
Runs the device command and reports the new state to the assistants. |
Offbeat-IoT can expose your device to Alexa and Google Home without any assistant code in the firmware.
The same protocol reaches every connected service. Add an integration once and all your devices can use it.
Full request/response reference: API and integrations docs.
Devices report readings with the same JSON protocol. Offbeat-IoT stores them and exports them as metrics.
Anything that can open a WebSocket and send JSON works. Examples are provided for the common boards.
Working sketches: microcontroller examples.