Docs
A device here is anything that can send a packet. These pages cover getting the first one in, deciding how much the platform should demand of it afterwards, and driving the whole thing from your own tools.
Get a device talking
Two ways in, depending on what you have on the bench: firmware you wrote, or a blank board.
- Build an ESP32 email alertTurn a temperature reading into an email alert with a routine.
- Send an ESP32 camera photo by emailUse the XIAO ESP32S3 Sense demo and check the capture and email limits.
- Start with data you can seeSend one reading from your board and find it in Warblet. Then give it a name, a chart, and a routine that makes it useful.
- Set up a devicePlug a board into USB and the page reads it: it keeps firmware that already answers, installs a demo where there is none, and hands the board your Wi-Fi and a credential. Nothing to install.
- Provisioning over USBCHIRP-PROV: a four-line UART protocol your firmware answers, so the portal can push Wi-Fi, a claim code and a signing key down the cable. Reference implementations in MicroPython and Arduino.
Set a board up over USB
The setup page links to each of these from the state that needs it. They are here for the person who came looking first.
- Connect a board over USBData cables, the port chooser, the USB-bridge drivers that make a board invisible, and why fifteen seconds of silence is not a blank board.
- Prepare your demo boardThe things some demos need beside the board: a Thread border router, a relay running on your computer, or MicroPython already installed.
- Connect to a Thread networkA Thread board joins a mesh, not Wi-Fi. What a border router is, where the network dataset comes from, and how to tell whether the board joined.
- Specs, decoders and raw dataWhat a spec decides for the devices on it, what a decoder adds, and the difference between a device with no decoder and one whose decoder failed.
- Write firmware that supports USB setupInstall your firmware file from the setup card over serial or DFU — and what your firmware has to implement to receive the settings you entered.
- No data yetThe board accepted setup and nothing has arrived. What that does and does not prove, the five checks in order, and how to retry one step.
- Update or reinstall a demoThe running release is not recorded, so nothing here claims a board is out of date. What keeping, installing and reinstalling cost you.
Decide what to demand of it
The level is not a switch you flip and hope. It is a design you declare, and the platform raises enforcement itself on the first message that proves the firmware can meet it.
- Security levelsThe Open → Token → Signed ladder, the separate Encrypted switch, a threat model for each, and how a device climbs without ever going dark.
- OpenHardware id only, no token. The bench level — plus the hardening you can do without leaving it, including verifying your own HMAC inside the decoder.
- TokenOne token per device on every message. Removes every off-path attacker; here is exactly who is left.
- SignedToken plus an HMAC of each payload, on every transport. Integrity on a chip that cannot afford a TLS stack.
- EncryptedThe Enforce TLS switch, per device, at any level: plaintext is refused at the door. HTTPS and MQTTS (8883) are the two TLS listeners; TLS-TCP is planned and has none.
Build on it
For machines
/llms.txt is the whole platform in one file for an LLM: endpoints, wire formats, the error shape and the page list above. Point an agent at it before it starts guessing.