We originally targeted May 2025 for this release, and later revised that to end of 2025. We’re now a small amount past that second date. The core platform work is complete; what remains is the final device-side items, end-to-end validation, and a staged rollout.
If you missed the previous update on this topic, you can read it here.
| Area | What’s included | State | Notes |
|---|---|---|---|
| V2 base system | Networking, telemetry logging, indexing, network protocol | Complete | Core platform foundation is in place |
| OTA updates (Pi 4) | Secure over-the-air update pipeline + device image for Raspberry Pi 4 | Complete | Enables safe upgrades and controlled rollout |
| Analytics infrastructure | Integration with our modern data collection and warehousing pipeline, enabling near real-time device data delivery to third-party aggregators | Complete | Final verification is part of end-to-end testing |
| MMS backend | Multi-mode scheduling (server-side): timezone-safe scheduling via API (planned schedules + live control) | Complete | Device-side implementation remains |
| MMS protocol | Multi-mode scheduling device/cloud contract: timezone-safe schedule format and command schema | Complete | Ensures compatibility across device + server |
| Window | Focus | Output | Notes / dependencies |
|---|---|---|---|
| 2–4 Jan | Final device-side items + end-to-end validation | Release candidate build | Includes MMS device-side + device controls + full regression |
| w/c 5 Jan | Limited beta (cap 200) + enablement work | Invite-only rollout begins | Assisted early installs; monitoring + rapid fixes |
| w/c 12 Jan | Staged go-live + rollout ramp | Expand rollout to eligible Raspberry Pi 4 devices | Depends on clean beta metrics + partner-side enablement |
| w/c 12–19 Jan | Raspberry Pi 3 support | Pi 3 build added to rollout | Rolls in once buildroot + validation completes |
| Late Jan | Rollout completion | Broader deployment across eligible devices | Controlled ramp with pause/rollback capability |
We’ll keep this page updated if dates move — and we’ll say why. For a release like this, the last stretch is disproportionately about safety, compatibility, and rollout control.