Thanks! I had my history preference set to ‘Never remember history’. I wonder if one of the speed enhancements in this release requires caching of the md icons.
Use case Internal and external adress???
This is an example of the use case, it also explains why it’s useful:
1 Like
Just had exactly the same error here too Troon. Anyone know if this should this be reported on Github? Not sure how much of an issue it actually is as my install is pretty much vanilla as I started again on 0.109 and have not configured anything other than Hue yet.
Edit, just to repeat the error:
hass-nabucasa 0.34.2 has requirement pytz~=2019.3, but you'll have pytz 2020.1 which is incompatible
Hmm, so removing the http: base_url, and moving it to the config seems like a good idea, but now the Google TTS went out again 
I love the new ‘integrations’ design where it bundles the same integrations into one.
Just an observation to the cool calendar. Week start day is now Sunday and we really miss the week numbers (the 25 mio. of us in Scandinavia) and then the week starts on a Monday.
Yeah, not ideal.
Am I understanding the OpenZWave integration correctly? It uses an instance of OpenZWave to to handle ZWave functionality rather than Home Assistant’s in-house fork?
I was happy running 0.109.6 core, pulled latest image and can’t access frontend since. I tried rolling back to 0.109.6, removed db file, my .storage and everything else is in git so changes to files are rolled back as well. Yet container starts but never opens port 8123. It seems that HA it’s partly working as I see data flowing into influx. The only error in the log is:
2020-05-20 23:56:03 ERROR (SyncWorker_14) [miio.miioprotocol] Unable to discover a device at address 10.0.40.12
2020-05-20 23:56:04 WARNING (MainThread) [homeassistant.components.fan] Platform xiaomi_miio not ready yet. Retrying in 30 seconds.
Tried removing container, redeploying, removing db on and on again, yet can’t make it work. ANything else I can do?
Correct. Finally separated from HA 
Hate to be the boob here but can you please provide some info on how to go about doing that? I don’t have the skill set or knowledge how to do this. Running HA in Docker on a Synology NAS. I would love to be able to create a complete “back-up” so I can roll back to the previous working version. When I tried the 109 upgrade my HA instance wouldn’t come back up but Docker said it was running. I just copied the HA config files I created and did a complete reinstall which may not be best practices.
Quite looking forward to trying the refactored squeezebox integration also, as the old one left a lot to be desired!
currently I believe that because you have ssl in use your local address also needs to be https:// instead of http://
when navigating in a browser you also have to type https:// before your local ip as it defaults to http if you just type the ip 192.168.51.3:8123
1 Like
I also miss a config so weeks start Monday. Most of the world have weeks starting Monday. It is only US, Canada and Australia that use Sunday. ISO also defines weeks as starting Monday.
1 Like
Did you solve this. I’m getting a similar message trying to upgrade one of my addons. I have enough free disk space.
How was HomeKit screenshot showing “3 on • 1 off” for some grouped devices achieved? HomeKit shows me “on” if even 1 of the devices in the group are on…
I had a spontaneous reboot (crash?). Is there any audit trail to mine?
Anyone having trouble with their Bose SoundTouch devices no longer showing up after moving from 109 to 110? I’m not seeing any errors; the entities are just not showing up anymore. Perhaps discovery is no longer working?
Maybe related to the underlying soundtouchlib version bump from the PR here?
I like many had issues with this update with HACS. Whilst trying to fix it, I tried uninstalling HACS, adding as integration, uninstall etc Now I have HACS in integration list, attempting to remove it does nothing and HACS is missing from left menu bar and all my custom components give errors.
I am now trying to do a clean restore of a hassio backup to see if I can fix it
1 Like
ok clear an restore from snapshot did not fix it. my install is currently broken
1 Like