Another awesome update. Shame the WLED integration is borked and it floods the API on the ESP chip forcing it into a reboot loop. Issues raised on WLED and HA Githubs (by those more knowledgeable than me, I just +1 it)
Currently running 108.2 on a NUC7. Tried upgrading to 108.6 today, but it failed. Log entries are as follows:
20-04-18 13:59:57 INFO (MainThread) [supervisor.snapshots] Found 4 snapshot files
20-04-18 13:59:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
20-04-18 13:59:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/mKeRix/hassio-repo repository
20-04-18 13:59:57 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
20-04-18 13:59:57 INFO (MainThread) [supervisor.updater] Fetch update data from https://version.home-assistant.io/stable.json
20-04-18 13:59:58 INFO (MainThread) [supervisor.store] Load add-ons from store: 67 all - 0 new - 0 remove
20-04-18 14:30:04 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.108.6
20-04-18 14:30:04 INFO (SyncWorker_4) [supervisor.docker.interface] Update image homeassistant/qemux86-64-homeassistant:0.108.2 to homeassistant/qemux86-64-homeassistant:0.108.6
20-04-18 14:30:04 INFO (SyncWorker_4) [supervisor.docker.interface] Pull image homeassistant/qemux86-64-homeassistant tag 0.108.6.
20-04-18 14:30:19 ERROR (SyncWorker_4) [supervisor.docker.interface] Canāt install homeassistant/qemux86-64-homeassistant:0.108.6 -> 500 Server Error: Internal Server Error (āGet https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)ā).
20-04-18 14:30:19 WARNING (MainThread) [supervisor.homeassistant] Update Home Assistant image fails
Any suggestions?
Tnx, Brad
Post deleted
Try again. Do you have enough disk space?
A
After update to 108.6 Logger: custom_components.hysen.climate
Source: custom_components/hysen/climate.py:891
First occurred: 13:26:47 (1008 occurrences)
Last logged: 21:58:13
- Failed to get Data from Broadlink Hysen Device:climate.th1,:name ācalculate_crc16ā is not defined
- Failed to get Data from Broadlink Hysen Device:climate.th2,:name ācalculate_crc16ā is not defined
Soā¦ I was using a night theme at night and default theme at day, with automation doing the change with theme selected as: backend-selected.
Now that I updated to 0.108.6, my sidebar background does not turn dark with the themeā¦ and also none of the 3rd party āpanel_iframesā are inheriting the dark theme.
What can I do to make it work as before?
Add this to your theme.
And use the front end reload themes service. No need for a restart.
For the side panel at least. Not sure about the iframes.
Thanks!
This fixed the sidebar, but as I was searching for the fronted.reload_themes service, I noticed that the combox list background also stays white (and panel_iframes still too).
So although this fixes a part of the issue, it seems that the āLovelace themesā breaking change broke a lot more.
So anyone from the developers made that breaking change can please elaborate on what we can do to make our themes work as before?
Thanks.
True, trueā¦ Corona-times unfortunately destroys my spare/HA time. Will see to it when things normalizeā¦ It could be a modbus problem, but it could also be a problem with the Flexit or climate integration (only thing I use modbus for at the moment).
Reverting to 0.107 was not what was asked to be tested.
Yes the believed fix was pushed in 0.108.6ā¦
see here Sidebar Background color Hassio V 108.2
and wait for the cache to be clearedā¦ I was using @tom_l 's solution but was too impatientā¦
I have plenty of disk space. Turns out to be a conflict with AdGuard. Error now says:
Couldnāt start forwarding DNS server, cause: couldnāt listen to UDP socket, cause: listen udp 0.0.0.0:53: bind: address already in use
For what itās worth, I just tested 108.6 on a test system with google calendar and magically it all worked fine.
Tried it on my production system, and all good.
So 108.6 ārestoresā the google_calendar functionality. I suspect by coincidence more than design than anything else - the last change was a breaking change for a bunch of components (#33794).
Thanks! That works tooā¦
But what I wanted to say is that it is not our job to find everything they (HA developers) broke with that change.
They MUST provide a thorough description of what they broke, and what can the theme makers do to update their themes to work as before!
Iāll open a github issue for that if they donāt answer here.
Anyone else seeing problems with AWS SNS? I noticed that my last text I received was on the day before this was released and I upgraded. I donāt see any errors when I execute an automation with an sns notify, but nothing is coming through to my phone now.
Same here!
not sure if this tone of voice is getting you anywhere, anytime soonā¦please go with the flow, seek answers to your questions, and post what you find to help others. Itās what gets this project forward, and makes it even more wonderful than it already is.
3 Likes
Wonderful eh? Breaking everything with every update is not what I call wonderfulā¦
Well if you donāt want to be a tester, donāt use home assistant!