Which theme did you use?
Might be that the theme is setting entities or something like that. You might want to avoid that theme than…
Yuki still for RB and Liam still on Redbull is that a api thing or cache? (card_type: driver_standings). Last results card is showing it correctly.
That might be wrong in the API than (I’m not maintaining the API). I’m sure it will be corrected soon.
1 Like
First of all, I just want to say a big thank you to the creator(s) of the FormulaOne Card, it’s a beautifully designed and super useful card for displaying race info and standings in the Home Assistant dashboard. Amazing work!
I wanted to share something that might be useful for those who are looking to take things a step further in terms of automations, scripts, or external integrations related to F1.
I’ve recently created a custom integration called F1 Sensor, which pulls data from the same, Jolpica-F1 API, and provides sensors instead.
This integration doesn’t have a visual component like the FormulaOne Card, it’s intended for use cases where you want to create automation, send TTS messages, trigger scenes based on upcoming races, or even display race info on external hardware (I’m using it on an e-ink display)
If that sounds interesting, feel free to check it out
Again, huge props to the FormulaOne Card project, it’s a perfect match for visual dashboards, and my integration is meant to complement it for folks who want to dig deeper on the automation side.
12 Likes
Nice, lets see if we can make my card work together with your integration 
2 Likes
Stimo, the link on your github to their ko-fi is not correct, it should (now?) be https://ko-fi.com/jolpicaf1
Thanks for pointing that out, I’ve updated the README file 
@Stimo You integration is only showing the current season stats right?
@marcokreeft87 Yes, that’s correct! My initial intention with the integration was to provide actionable sensors, suitable for triggering automations or easily using data in other environments, like displaying info on an e-ink display alongside your card.
I haven’t really seen a practical use case for historical data within a sensor, as it would mostly add unnecessary complexity and data overload in attributes. But I’m definitely open to suggestions if you see any improvements or additional use cases!
Also, a small teaser: I’m working on an update that will soon add current weather and race-day forecasts, so stay tuned if that is of any interest
1 Like
Nice! Github is building as we speak a new release that uses your integration (optionally ofcourse) for driver_standings,constructor_standings and schedule cards
1 Like
Version 1.12 is out now! It adds the feature to use the integration of @Stimo for the driver_standings,constructor_standings and schedule cards
2 Likes
wow… that was quick all. 
1 Like
Thats the benefit of clean coding
2 Likes
That sounds cool, I made my own cards with your sensors, and they look great. Will there also be a sensor that gives the race result
I’ve thought about adding a sensor for race results, but I’m not sure if it adds enough value. Importing all historical results (going back to 1950) isn’t practical, and even storing a whole season’s data might overload Home Assistant without clear benefits.
However, I could possibly add a sensor with the latest race results. Would that be useful? If so, how would you envision using it? Let me know!
I also think it would be very taxing if you go back from 1950 :P, I would be happy if you could see the race results of the current season. Its use should be the same as the standings so I can make a card that can show the full result
I’ll look into whether I can include current season race results in a smart and clean way. It would become a pretty big sensor (this is the data for the first 4 with many attributes, and the last thing I want is to clutter things up unnecessarily. Maybe I could add an option in the setup, allowing users to choose exactly which sensors they’d like to activate.
Thanks for the suggestion! I’ll keep you posted! 
Okay great thanks. Do what you want, everything is a bonus.
My card does this all tho
I agree, the FormulaOne Card probably handles this best already, given it’s a lot of data for a single sensor.
@Braakie, but feel free to open a discussion on the GitHub page for F1 Sensor, and we can explore it further from there!
1 Like