Riviamigo 2026.07.0

This is the first public release of Riviamigo.

I built Riviamigo because I wanted a self-hosted place for my Rivian data that felt direct and useful without depending on a hosted service. This release brings the current development version into main as the first release candidate.

I will not repeat the full feature list here. The README has the project overview, and the Wiki covers installation, configuration, security, backups, and day-to-day use.

I know there's going to be bugs, and apologize ahead of time, but just submit a issue and I'll get to it as quick as I can (and like I mention below, always looking for contributors or if you really love it a maintainer).

The biggest testing gap

The biggest gap in my testing is that I do not have direct access to an R1S or R2S. Testing for those models has been done with fixtures and demo data. Because of that, vehicle images may be positioned a little incorrectly, and model-specific sensors may be missing, named differently, or mapped incorrectly.

If you use an R1S or R2S and notice something that does not look right, please open an issue with details and screenshots if possible. Before sharing anything, please remove VINs, names, exact locations, and any other private information.

Contributions and feedback

Contributions are welcome, especially model-specific testing and fixtures, sensor corrections, documentation improvements, and mobile fixes. The contributing guide explains the project workflow. You can also open an issue first if you want to discuss a larger change before working on it.

Thanks to everyone whose Rivian API research, integrations, testing, and feedback helped make this possible.