Connecting Zephyr Devices at Scale Using Open Source Solutions
summary
Zephyr’s CoAP + LwM2M clients pair with open-source servers like Eclipse Leshan, Californium to manage devices; one deployer runs millions. Two architectures compare: LTE‑M/NB‑IoT vs Matter/Thread. Specifics: DTLS for security, UDP NAT timeouts (30s–3min) force device-initiated pulls, CoAP blockwise transfers make megabyte firmware slow, so systems send a URL and the device fetches firmware. A tracker project drops LwM2M for a proprietary protocol to save battery.
AI-written summary · about
chapters (10)
- 0:00Introduction to CoAP
- 1:04CoAP architecture overview
- 3:44Demonstrating CoAP mechanics
- 8:14Blockwise transfer features
- 10:09Security in CoAP
- 11:09Challenges with NAT and UDP
- 18:09Lightweight M2M standard
- 20:45Deploying CoAP at scale
- 28:15Getting started and tooling
- 31:40Q&A on CoAP deployments
related talks
26mTo Boldly go Where Linux Cannot with Zephyr and Eclipse IoT
30mZephyr ❤️ Internet: How Zephyr Speeds Implementation for New IoT Devices
34mZephyr LPWAN Connectivity Options and When to Choose Them
10mLightning Talk: From Ideas to 3 Firmwares Powering Railway-Infrastructure Monitoring...
39mZephyr Project: Unlocking IoT Innovation with an Open Source RTOS
50mZephyr Project: An RTOS to Change the Face of IoT
20mZephyr Network Subsystem Status and Overview
32mAT-based Modem Support in the Zephyr Project: Present and Future