You are correct. Your list is in a different order than mine and I missed icon in yours… Anyway other than wind_bearing I don’t see that you are missing anything. and you have said you added that. I assume you restarted HA after adding it ?
I’m still stuck on the fact that the error you mention can’t be presented in the version you say you have.
Let’s start from scratch…
What version on HA are you using ?
Can you post a screen shot of the error you are getting
Post any messages in the log pertaining to the card
Post any messages in the log pertaining to DarkSky when you restart HA
That error indicates that you are exceeding the maximum number of API calls so Dark Sky won’t let you connect.
According to the Dark Sky site you get 1000 API calls per day for free.
I specify my update interval as: minutes: 5 yours looks like: ‘00:30:00’. You said it worked before an update. Maybe the Darksky platform can no longer take update intervals in that format so it is updating to fast? I don’t know… but try changing that to minutes: 30 instead and see if it helps. You will need to wait a day for your count to reset.
You restarted HA after adding the card and Dark Sky Config
You cleared the browser cache
You Refreshed the UI
Something else to try (although it shouldn’t be needed anymore) is to increase the version number for the card in ui-lovelace. You currently list it as 7.1 try changing it to 7.2 or 8 or something larger to make sure lovelace knows it’s a new version.
What version of HA are you using? You mentioned you are using YAML mode so I assume you are using .84. Are you sure that you have YAML mode turned on?
Hi Mark! I’m stucked, maybe you could help to find the solution. I use an RPi 3 with 0.84.6., i never used this card before.
The card can’t be loaded, I see only the white field. Both of my errors are js file related:
Under Chrome I got this error message: 143:79 Uncaught TypeError: Cannot read property ‘state’ of undefined.
And under Firefox I got this: 143:41 TypeError: hass.states[daily.templow] is undefined.
This is line 143: ` ${Math.round(hass.states[daily.templow].state)}${getUnit(‘temperature’)}
As I know every needed sensors are included in sensors.yaml and all the values are readable except`sensor.dark_sky_temperature_1, sensor.dark_sky_temperature_2, sensor.dark_sky_temperature_3 and sensor.dark_sky_temperature_4, they values are unknown.
I tried to readd every sensor, cleared the cache, increased the “v” value, rebooted multiple times and now I don’t know what else to try.
If you remove that line you will not get low temperatures for daily blocks.
It would be better to correct the issue by determining which daily low temp was causing the issue. Most likely it was cause by a change made in the darksky platform a few versions ago where the 0th day forecast needed to be called out specifically. Some folks fixed it by passing in overnight_low_1 thru 5 instead of 0 thru 4. You can also just add 0 to the forecast in dark sky config and make sure the first low temp gets overnight_low_0 assigned. It has been discussed multiple times in these threads. A link to one discussion is here
Make sure to look through all the information in the link I provided, especially the info on Forecast day 0. I believe that is the issue in your original post.