Well without looking at the logs you’re just guessing.
There I can find no indication of a problem with lovelace.
1.110.1 is out 
1 0.110.1 is out 
2 Likes
Any changes in ‘picture-elements’? Get ‘hass is undefined’ after update to 0.110 …
Yep, that’s the solution - remove ‘retry’. It’s no longer a valid config.
The docs weren’t updated before 0.110.0 and no breaking change was listed. I submitted a PR last night to amend the docs which was approved about an hr ago.
1 Like
I just can not get my Unifi G3 Micro camera to work with Homekit. I get still image in HomeKit but stream doesn’t work. I have tried all possible things but I always get No Response error.
It works great in lovelace.
Any suggestions? Thanks!
Ok the new Squeezebox integration seems to be working far better than the old one for me, no more error messages in my log when powering off players at the mains.
I’m still unable to ‘discover’ new players that are powered on after HAC is started up, but I haven’t really experiemented with the service calls yet.
Try Tileboard GUI, even works on an iPad 2nd Gen!
Ok thanks @thoughton, this did put me in de right direction. I was still using the old method where i used he “old” fashion way, for securing homeassistant with https. I was still using the build in http component in home-assistant core for providing secure https acces. (https is activated when certificates are mapped within the http component). The new way is to use a proxy (Nginx or caddy) to provide the SSL acces to the running instance of home assistance core. When setting this up, now i understand the use case of internal and external adress and that the internal is not using https.
I now also under stand the usecase for internal and external acces within the companion app for IOS.
With this setup google TTS is working without any problems in both use case (internal and external adress).
I think that the people who are having problems with google TTS in the update, also use the build-in https from homeassistant core!, moving to nginx solves this
2 Likes
Sorry, I do not install 0.110
20-05-20 20:11:18 INFO (MainThread) [supervisor.store] Load add-ons from store: 68 all - 0 new - 0 remove
20-05-20 20:43:41 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.110.0
20-05-20 20:43:41 INFO (SyncWorker_18) [supervisor.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.109.6 to homeassistant/raspberrypi3-homeassistant:0.110.0
20-05-20 20:43:41 INFO (SyncWorker_18) [supervisor.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.110.0.
20-05-20 20:55:25 ERROR (SyncWorker_18) [supervisor.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.110.0 -> 404 Client Error: Not Found (“no such image: homeassistant/raspberrypi3-homeassistant:0.110.0: No such image: homeassistant/raspberrypi3-homeassistant:0.110.0”).
20-05-20 20:55:25 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
20-05-20 21:11:15 INFO (MainThread) [supervisor.host.info] Update local host information
20-05-20 21:11:15 INFO (MainThread) [supervisor.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
This can be caused by the lack of available storage space.
Спасибо! Буду чистить
Got his error once yesterday and again an hour ago. Anyone else seeing this or know how to troubleshoot?
I just noticed that you and @eximo84 are also getting this error. My HA instance is not crashing or restarting though. Did you find a solution? See my post above.
With base_url now deprecated, how do I continue to use Duckdns?
I had this under http in config.yaml.
Any help please?
Setup the internal_url and external_url refer to the patch notes in the post.
Oh, I like the new calendar look, but it’s an american calendar look, americans thinks that the week starts on sundays, and a big part of the world thinks it starts on mondays, so please add a setting to determine the first day of the week.
1 Like
In my case it seems it got, if not fixed, at least less frequent when I manually removed the ring integration ad re-added. And also had to remove auto-stream from all my mmjpeg cameras.
