What's a big release without a little release right after it, to fix a bug we should have caught? This is that release. It fixes the tire card, makes vehicle collection recover on its own, and tidies up the logs.
Thank you to @Rolled, who sent #116, the fix that keeps a vehicle collecting after a bad start.
Fixes
- No more "Invalid Sensor" on a parked vehicle. Once a vehicle parks and its wheel sensors go quiet, Rivian marks every tire reading "not valid". Riviamigo stored that as a failed sensor, so the Health tire card showed "Unavailable / Invalid sensor" over perfectly good pressures for most of the day (#117). A "not valid" flag is now ignored unless the vehicle has been driving for at least 10 minutes, long enough for the sensors to wake. A parked vehicle keeps its last measured pressures, and a sensor that stays silent well into a drive is still reported as invalid. Flags already stored by earlier releases are cleared on upgrade.
- Collection restarts itself after a hiccup. If a vehicle's collector stopped early because Postgres or Redis was not ready yet at boot, or during a rolling update, that vehicle collected nothing until you paused and resumed it or restarted the API. It now retries on its own, waiting 5 seconds at first and backing off to 5 minutes. A vehicle you paused stays paused.
Logging
Logs now follow one set of conventions across the API, the restore agent, the maintenance tools, and the browser app.
- Quiet by default.
infoshows lifecycle events and milestones only.debugadds the decision trail (why a trip or charging session started, ended, or was ignored), andtraceadds per-frame detail. SetRUST_LOG=riviamigo_api=debug,infowhen you need to chase a problem. - Failures are no longer swallowed. Errors that used to disappear are now logged once at the right level, and startup problems and panics use the same format as everything else.
- Browser logs use the same levels. Set
rm-log-levelin the browser's local storage to turn the browser's detail up or down.
Passwords, tokens, and other credentials are still never written to logs. The Logging conventions page has the full list of levels and fields.
Upgrading
This release adds one database migration, which runs automatically on startup and takes a moment. Log lines now use sentences instead of dotted event codes, so anything that searches your logs for the old codes needs updating.
Full Changelog: 2026.11.2...2026.11.3