I’m excited to share a new custom component I’ve developed for Home Assistant: Spritmonitor Vehicle Data Integration!
If you use Spritmonitor.de to track your vehicle’s fuel consumption, costs, and service records, this integration is for you. It brings all that valuable data directly into Home Assistant, allowing you to monitor your vehicle’s stats alongside your other smart home devices.
What it does:
This component creates various sensors in Home Assistant for your vehicle data from Spritmonitor, including:
Vehicle Info: Make, model, license plate, tank capacity.
Fuel & Consumption: Total distance, total fuel consumed, average consumption (km/L), and detailed data from your last refueling (date, quantity, total cost in UYU, price per liter, odometer, trip, consumption).
Maintenance Reminders: Next service mileage, date, and any notes.
Estimates: Estimated current fuel level and remaining range.
Spritmonitor Ranking: Your vehicle’s rank and average consumption compared to others on Spritmonitor.
Installation:
The easiest way to install is via HACS (Home Assistant Community Store):
Open HACS → Integrations.
Click the “…” (top right) → “Custom repositories”.
Add https://github.com/matbott/home_assistant_Spritmonitor with category “Integration”.
Search for “Spritmonitor” in HACS and install.
Restart Home Assistant.
Configuration:
After restarting HA, go to “Settings” → “Devices & Services” → “Add Integration”, search for “Spritmonitor”, and enter your Spritmonitor Vehicle ID, Application-ID, and Bearer Token (you’ll need to obtain these from Spritmonitor’s API).
Based on the discussion with spritmonitor.de while im created the Rest Sensor they wish that not everyone request the App-Token individually instead everyone should use the already published one.
@Spritmonitor: Maybe you can reply here how to proceed.
APP_TOKEN Spritmonitor assigned meanwhile an dedicated APP-Token, so you can use it directly. No individual request needed anymore. App-Token: 190e3b1080a39777f369a4e9875df3d7
Hi, thanks for the comment. I’m actually using the public token I found in your post. But during the integration, the startup form requests both the application token and the user-generated one. In any case, I’m waiting for @Spritmonitor response.
Usually you don’t need to contact the Team “spritmonitor.de”, the App-Token is public and the Bearer you can create by your own within your account.
How to:
Log in to your account / (or go to “your account”) → Click on “Change Password” → and below you should see the option “create new token”
This will be your Bearer Token.
Yes, thank you. That’s what I did following your post. The integration currently generates the sensors in Spanish; I’m working on the translations. Regards
Thanks @spritmonitor, I’ve documented the token in the integration readme.
I’d like to let you know that version 1.3.0 is now available with the sensors in English for greater language versatility. I’ll have to see if I have time to dedicate to the translations. I also fixed a next service date sensor that was giving me an error. Regards.
Great, thank you! Perhaps you could also hard code the app token into the script and don’t have the users enter it. I think this would make the configuration even easier and the app token will never change in the future.
Thank you. I implemented a new form where the token is pre-filled, but I allow the option to change it, and a refresh time range of 1 to 24 hours. Thanks for the response. @Spritmonitor
