@marcokreeft87 I can see something similar, on local network all is fine, but accessing thru nabu casa there are no standings…
local:
nabu casa:
Hope this helps with tracing the issue.
If you need my help with hunting, just beep me 
Dont know bro. I dont have that issue so I cant locate the issue. Do you see any errors in the network or console tab of developer tools in the browser?
Nope, it looks just clean… 
I kinda fixed mine. I removed flags from driver standing and I noticed it helped. Then I turned on flags again and cards keep working. I don’t know why it helped.
I think it’s NAT related, when i use homeassistant.local i don’t get the standings, when i use the ip adres 192.168.X.X it works.
Interesting.
Here LAN works fine on IP and on .local
It’s just external access thru nabu casa that does not.
Tested a bit more and logging out and in again fixed it for me on the .local url.
Even a hard restart does not help with nabu 
Good advice Johan!
Logging out and in HA again fixed the missing standings issue for me permanently.
Thanks 
Woke up today and all is ok again… don’t ask me how
sleep is always restorative in IT
1 Like
Could be a lot of things. But probably cache or something like that 
Good that it is resolved. Have a great season everyone! The first race was a good one!
4 Likes
If anyone still using the other F1 formula one card (Formula One Card - #91 by marcokreeft87) then you can revive it by updating the API address to Jolpi API like this:
rest:
- scan_interval: 86400
resource_template: https://api.jolpi.ca/ergast/f1/current/driverStandings.json
sensor:
- name: "F1 Drivers"
json_attributes_path: "$.MRData"
value_template: "OK"
json_attributes:
- "total"
- "StandingsTable"
- scan_interval: 86400
resource_template: https://api.jolpi.ca/ergast/f1/current/constructorStandings.json
sensor:
- name: "F1 Constructors"
json_attributes_path: "$.MRData"
value_template: "OK"
json_attributes:
- "total"
- "StandingsTable"
template:
- trigger:
- platform: time_pattern
minutes: 0
sensor:
- name: f1_nextrace_in_days
state: >
{% set b = states.sensor.f1_nextrace.attributes.race_start %}
{% set c = now() %}
{% set d = as_timestamp(b)- as_timestamp(c) %}
{% set e = d / 60 / 60 %}
{% set f = e / 24 %}
{% set da = ( f ) |int %}
{% set h = (( e ) - ((f)|int*24)) | int %}
{% set m = ((e%1) *60 ) | int %}
{{da}}
- trigger:
- platform: time_pattern
minutes: 0
sensor:
- name: f1_nextrace_timer
state: >
{% set b = states.sensor.f1_nextrace.attributes.race_start %}
{% set c = now() %}
{% set d = as_timestamp(b)- as_timestamp(c) %}
{% set e = d / 60 / 60 %}
{% set f = e / 24 %}
{% set da = ( f ) |int %}
{% set h = (( e ) - ((f)|int*24)) | int %}
{% set m = ((e%1) *60 ) | int %}
{{h}}
##############3
## See link for information : https://community.home-assistant.io/t/formula-one-card/476902/91
## See comment 88
#############
sensor:
- platform: rest
scan_interval: 86400
resource_template: https://api.jolpi.ca/ergast/f1/{{ now().strftime('%Y') }}.json
name: "F1 Schedule"
json_attributes_path: "$.MRData"
value_template: "OK"
json_attributes:
- "total"
- "RaceTable"
You must also add the new driver photos to the folder in your HA: www/formula1/driver2023 folder. get them from here F1 Drivers 2025 - Verstappen, Hamilton, Leclerc and more
1 Like
Am I correct that Sprint Qualifying is not included in hide_racedatetimes?
About the Results card, does this always show automaticly the latest race?
And does sombody know how i can hide the selector with card mod?
Correct, that data isnt returned from the API unfortunately
Yes, and I dont know xD
Sorry, I am an idiot xD I now get what you mean. There is a new version underway
2 Likes
Is there a possibility in card_type: next_race to arrange FP1 thru GP based on date time? At the moment Qualifying and Print race are out of sync.
Nope its not currently. I will fix that for you 
1 Like