OP
OP
pogiant
Member
- First Name
- Anton
- Joined
- Mar 22, 2023
- Threads
- 1
- Messages
- 11
- Reaction score
- 7
- Location
- Austin, TX
- Vehicles
- Rivian R1S
- Occupation
- Platform Engineer
- Thread starter
- #16
▎ Rivolt doesn't poll on a fixed cadence — it holds a persistent WebSocket subscription to Rivian's gateway (the same vehicleState stream the official mobile app uses) and gets pushed a new sample every time the vehicle reports a state change. In practice that's a frame every ~3–5 seconds while you're driving or charging, and effectively nothing while parked because the vehicle goes to sleep to save battery.
▎ There's no separate "bulk upload over WiFi" path — Rivian doesn't expose one — but you don't really need it, since the live stream already captures everything as it happens (no LTE backhaul, no missed samples when you pull into the garage). Rivolt stores everything locally in Postgres so the long-term trend view is fully retained without depending on Rivian for history.
▎ Connect+ is not required. It only gates the entertainment features (in-car Spotify/Apple Music/browser). The mobile-app data API that Rivolt uses runs over Rivian's standard cellular link that ships with every R1, so the integration works on the base plan.
▎ There's no separate "bulk upload over WiFi" path — Rivian doesn't expose one — but you don't really need it, since the live stream already captures everything as it happens (no LTE backhaul, no missed samples when you pull into the garage). Rivolt stores everything locally in Postgres so the long-term trend view is fully retained without depending on Rivian for history.
▎ Connect+ is not required. It only gates the entertainment features (in-car Spotify/Apple Music/browser). The mobile-app data API that Rivolt uses runs over Rivian's standard cellular link that ships with every R1, so the integration works on the base plan.
Sponsored
