It seems to be solved on my end by removing and readding the ring cameras, a couple of times. I followed the migration guide for the entities without yaml,but it seems that there was some sort of cache or something.
Super speedy!!! Cheers!
One thing on Firefox, all my icons have disappeared!
edit
Had my Firefox set to ‘Always use private browsing mode’ - once I unticked that setting the icons returned.
On the same machine using Chromium everything is good though
Has this happened for anyone else?
1 Like
Great release. Thank you! The memory use is also a lot lower. Perfect!
Someone beat me to it 
1 Like
Same for Lutron Caseta.
Now none of the lights work as they did before configured via yaml.
there is now an internal / external url setting, to iprove for example camera streams for google assistant…
but how does this work? i tought google assistant will need a public url? how can google use the internal url instead?
PS/ i am using nabucasa expose to google assistant
My Wyze Pan&Scan does not work properly with homekit. While the cam work great in lovelace, in the Home-App I only see the still images which are updates regularly. But when I tap the cam to see the live stream in the Home App, it does not work. What am I doing wrong?
Config:
ffmpeg:
- ffmpeg_bin: /usr/bin/ffmpeg
camera:
- platform: ffmpeg
name: Wohnzimmer
input: -rtsp_transport tcp -i rtsp://user:[email protected]/live
extra_arguments: -pred 1 -q:v 15 -r 15 -vf scale=960:540
Is the Manual MQTT alarm going to be updated to use the arming state rather than pending?
Right now i am using that to allow me to disarm the alarm from a button rather than entering a code by sending the disarm MQTT command. I only use the keypad on the wall mounted tablet. Is it possible to do that with the standard manual alarm?
Regarding the “external_url”, that needs to be a parameter of the “homeassistant:” integration, not the “http:” integration anymore. Same applies to “internal_url”
i have a black bar below now on every lovelace page
what is that ?
Icon size issue on picture element card.
- elements:
- entity: binary_sensor.rorelsesensor_esp_vardagsrum
style:
'--iron-icon-height': 60px
'--iron-icon-width': 60px
left: 14%
top: 50%
type: state-icon
The icon size (height and width) is not honored - the icon becomes tiny.
Is it “just me” or have I made a booboo somewhere?
Still happening for me. Maybe it related to my YiHome HackV4 Cameras which are working fine in HA when you open them however i am getting constant restart notifications at least every 15-30 minutes with no real log entries to help me pin point.
Use this instead:
'--mdc-icon-size': 60px
2 Likes
I tried reinstalling HACS and that did not work for me.
What I did was clean the browser cache to get rid of this issue. I tried using an “inkognito” window first and that worked like a charm!
After cleaning out the browser cache all was good!
Does the black bar become a giant HACS icon if you continue scrolling down? Is so, update HACS.
My HACS is updated to latest version 24.5
i dont see a icon, just a big horizontal black bar,
YAAAJ! Takk! Worked great!
Where can I read up on the new icon changes? Did not catch this one in the “breaking changes”.
Dont wanna miss any new cool options and features
i have now configured my urls like below, but why am i still seing this error? allthough i commented out the base_url in the http : section???
homeassistant:
internal_url: !secret internal_url
external_url: !secret external_url
2020-05-20 20:25:16 WARNING (SyncWorker_2) [homeassistant.components.http] Detected use of deprecated `base_url` property, use `homeassistant.helpers.network.get_url` method instead. Please report issue for http using this method at homeassistant/components/http/__init__.py, line 136: for frame in reversed(extract_stack()):
You still have base_url:, under http: somewhere
Try an inkognito tab/window in your browser. If there isnt any HACS gigantic icon no more - then clean out the browser cache. That did it for me.
1 Like