Mine are just “unavailable”. Restart HA/reboot server/ power cycle Yeelight bulbs doesn’t change anything. Rolled back to 0.117.6 
1 Like
If those are external URLs, are they whitelisted?
https://www.home-assistant.io/docs/configuration/basic/#allowlist_external_urls
1 Like
Thanks guys, well done!
Went smoothly from .117 to .118
has this been noted already:
last_updated showing invalid date in /developer-tools/state:
If anything should probably Unknown, or None, but Invalid date is kinda awkward?
Is it possible to change the keyboard shortcut for the Quick Bar to something more standardized like Ctrl+Space?
1 Like
Yep, my mistake. Whitelisting urls helps, component work. But still can not figure how to add album cover from spotify to the url. Having spotify url as:
/api/media_player_proxy/media_player.spotify_****?token=****&cache=****
The example given is quite different from how you’re trying to use it.
I would try to adapt their example to your use case.
action:
- service: color_extractor.turn_on
data_template:
color_extract_url: '{{ states.media_player.chromecast.attributes.entity_picture }}'
entity_id: light.shelf_leds
-Example taken from the docs.
Just did this, overwriting the files in my current hacs folder but the issue persists.
and you restarted HA after you updated HACS?
I neither don’t know if formatting the numbers with comma / point according to the language setting was a good idea (#7516). In general yes (of course, I always like new features!!), but now there is a mix all over my visualisation as a lot of cards do not not support this. Before a point was not correct (for Germany), but it was consistent.
Is there any chance to temporary disable this new feature till all cards support it?
By the way --> the native gauge card does neither support it.
Thank you
EDIT: The change is only applicable for the frontend, which means that the backend still only support the old format. Even more I would appreciate on option in the frontend for language specific number format.
2 Likes
What you should do is raise an issue with the custom cards that do not yet support it.
Since format number is related to language, we loose consistency on this. Backend and frontend is now using two different logic to format numbers. And as version 118.0, even in frontend, entities type card is using the format number according to the language (ex: 12,43$ in french), but sensor type card, and maybe other types, are using the old format (so: 12.43$). Also, it will be difficulty to have a consistency with format number if using differents customs card to lovelace… not sure it’s a great idea to format numbers according to language, maybe a separate setting is needed
In frontend, markdown type card is not using the new format number according to language, also sensor type card is not using the new format number according to language. So even if some custom cards are not supporting it yet, there is no consistency between cards in the current core release
Then the issue goes in the home assistant frontend repository, if there is not one there already. https://github.com/home-assistant/frontend/issues
Same for me, page in a constant refresh loop and won’t load.
Under recent blog posts (as I posted earlier) click here
Yeah got it, was just confirming in case one of the devs hadn’t seen the other posts.
0.118.1 build failed anyway…
1 Like
Agree, what an awesome update! I’ve already configured a custom remote control using the grid card and my Broadlink mini. Wow! What a rewarding afternoon! Keep up the great work team!