Here’s the link to my post that has all the working code. No need to add stuff from the thread. Just copy/paste into the relevant parts in your HA config. Replace the .js and .css files with my versions (you can save your old versions with different names if you want).
Updated my original post with my latest code which makes it easy to swap out the hardcoded language elements like the day names, feels like, today and forecast. Now they are set in ui-lovelace.yaml so it should eliminate any .js editing.
If you’re already using my code, make sure you look through the whole post. There’s changes to both the .css and .js files.
i can’t imagine why that would work unless you’ve edited or are using a different .js file than the one I posted. The .js file is looking for this.config.entity_feelstemp on line 103. Changing it to entity_apparent_temperature should throw an error.
Im using the js file you linked to in post 182. I do not know what is going on. When I tried with entity_feelstemp it keep giving me an error and would not load the lovaelace panel. Changed to to entity_apparent_temperature in the love lace ui and it worked.
well, i’m happy it’s working, but you definitely aren’t using my .js file. maybe it’s a cache issue? or you have several different dark-sky-weather.js files and are pointing to the wrong one? regardless, if it’s working and you’re happy then no issue.
and as @Mariusthvdb says in the post below it doesn’t really matter what you call it as long as it’s the same in both places. Which is why you’re getting the error when you try to use the code from ui-lovelace call (entity_feelstemp) with a .js file that is looking for entity_apparent_temperature.
Okay well I don’t know what is going on. If i use my desktop I have to have entity_apparent_temperature but my phone want entity_feelslike. I have never had this component until today.
or clear your cache and reload the page.
either your phone or your computer is correct, and the other one is working off a cached version. changing the version numbering should force them both to reload the page.
What version of Firefox are you using? The Lovelace page has a note about older versions not working right.
Otherwise, I don’t know enough about js / css to know what might cause the issue. As far as I can tell I’m not using any css tags or formatting that aren’t supported by Firefox.
Try and install the basic version of this card (the top post in the thread), and see if that works with Firefox. If that one works, then it’s definitely an issue with my code, and can be more easily tracked down.
I was using an ESR version (60.0) and upgraded to last Quantum version (63.0.3) before posting as I saw that comment. Both versions make the same effect.
This weekend I’ll try to make some changes and I’ll come back with the results.
From my side, don’t worry. I’ll use chrome from now on.
Just a heads up for non-developers (like me) using chrome. If you have trouble getting the card or more importantly new edits to show, sometimes a cache reset isn’t enough. Even changing the version number in the string seems to stick sometimes for some reason. Other than using incognito mode in Chrome i have found out that deleting “Hosted app data” and “Content settings” along with “Cached images and files” is what you are looking for to delete in “Clear browsing data”. That won’t touch cookies and saved passwords (that was a pain for me)
Thanks @jusdwy, you edited in exactly what i wanted
i find that turning on chrome developer tools (F12 or ctrl-shift-i) and then right clicking the page refresh button (empty cache and hard reload) works everytime.
Hey there, i was at version 0.79.3 and my weather card was working fine, i then upgraded to 0.83.3 and since then i have an issue with it :
local/custom_ui/dark-sky-weather-card.js:145:85 Uncaught TypeError: Cannot read property ‘state’ of undefined
which refers to : <br><span class="lowTemp">${Math.round(hass.states[daily.templow].state)}${getUnit('temperature')}</span>