What the M2M grandpas can teach the IoT kids
summary
Sierra Wireless has been connecting millions of devices since the M2M era and shows concrete operations practices: use MQTT with Eclipse projects like PAHO and Mosquitto, expect cellular quirks (devices syncing en masse at 3:00 a.m. that overload backends), and plan for firmware disasters (one OTA pushed to ~500 devices bricked smart locks). Prioritize reliability with monitoring, network-coverage history, exponential backoff, and a dual-partition OTA with rollback so updates can be aborted remotely without field visits.
AI-written summary · about
chapters (15)
- 0:00M2M and IoT history
- 2:16Defining machine to machine versus IoT
- 3:43Eclipse IoT architecture
- 4:27IoT developer priorities
- 5:11IoT device challenges
- 7:25Debugging connectivity
- 9:56Network coverage tools
- 11:03Avoiding bricking devices
- 12:27Smart lock firmware failure
- 14:19Embracing IoT failure
- 15:45Dual partition updates
- 16:30IoT battery monitoring
- 17:11M2M complexity
- 18:37IoT expectations vs reality
- 19:18Next speaker's IoT apps
related talks
27mIoT is hard, keep hustling
47mLessons and Advances in IoT: Toward 1M Connected Devices
30mConnectivity Forum – João Alves
15mLighweightM2M and its ecosystem
36mConnecting Zephyr Devices at Scale Using Open Source Solutions
13mARM mbed
25mImplementing IoT Architectures with Open Source Software
49mIoT in the service of Man or Man enslaved by IoT?