Create a Device Profile in TTS with Class C enabled; set the MAC version and regional parameters appropriate for your hardware and region
Register the device under this profile; confirm the device joins via OTAA and TTS shows it as Class C activated (the device continuously listens on the second receive window frequency)
Send a Class C downlink via the TTS console or API: POST to the device's downlink queue endpoint with the payload, fPort, and confirmed: false (Class C downlinks do not require confirmation from the network server side)
For confirmed uplinks, configure the device firmware to set the confirmed flag on uplink frames; TTS will send a downlink acknowledgment in the next RX1 or RX2 window
Monitor the TTS live data view to verify downlinks are scheduled and delivered; check for 'no downlink path available' errors which indicate the device has not been heard recently
Tune the RX2 frequency and data rate in the device profile to match the device's Class C receive window configuration
Known gotchas
Class C devices consume significantly more power because they keep the radio receiver open continuously; confirm the device's power budget supports Class C operation before deploying to battery-powered hardware
The network server can only send Class C downlinks when it knows the device is reachable; if the device has not sent an uplink recently, the gateway path may be unknown and the downlink will be queued until the next uplink
Confirmed uplink ACKs consume downlink airtime and contribute to gateway duty cycle limits; avoid confirmed uplinks at high data rates or in dense deployments
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp