Offbeat-IoT
Small devices. Big APIs.
Teach your device one protocol. Connect it to everything else.
A microcontroller connects to Offbeat-IoT over WebSocket with one small JSON protocol. Offbeat-IoT handles OAuth, provider APIs and the integrations — Spotify, Alexa, Google Home and more — so your firmware never has to.
Works with
Each logo links to its request/response reference.
One connection in the middle
Your device speaks Offbeat-IoT. Offbeat-IoT speaks everything else. The device never talks to a provider API directly.
The device sends commands and readings to Offbeat-IoT; Offbeat-IoT delivers provider events and results back on the same connection. No cloud service ever talks to the device directly.
Your firmware stays simple
No per-provider HTTP client, no token storage, no refresh logic. One message on one connection is enough:
{
"spotify.next": ""
}Offbeat-IoT handles
- OAuth authorization
- Token refresh
- HTTPS & TLS to providers
- Provider APIs & payloads
- JSON parsing
The device sends the same shape for Spotify, Todoist, Google Health and the assistants.
What you get
Four things a microcontroller should never have to implement itself.
One protocol
Every capability is a JSON key. Send {"spotify.next":""}, get a result on the same connection.
Cloud integrations
Spotify, Google Calendar, Google Health, Todoist, weather and more, behind the same message shape.
Alexa & Google Home
Expose your device to both assistants with no assistant code in the firmware. State changes sync back automatically.
Monitoring
Devices report readings with the same protocol; Offbeat-IoT exposes them to Prometheus and Grafana.
Supported hardware
Anything that can open a WebSocket and send JSON works. Examples are provided for the common boards.
Wire it once. Reach everything.
Start with the firmware examples, or read the protocol and build your own client.