this update completely broke my hassio install on ubuntu.
Can’t even restart the containers to ssh or samba in.
I am installed the same way, and had no issues whatsoever. I assume you have tried restarting the Hass.io Home Assistant machine?
Did you read all of the breaking changes to make sure you didn’t have anything that might cause an error after upgrading?
Is the machine still showing on your router as connected to the network?
1 Like
I got ‘configuration errors’ on:
- spotcast
- cast.media_player
Tried both release 109 and 109.1. Reverted to 108.9.
Basically it broke connection to all my google homes and chromecast devices.
The log error was:
Unable to prepare setup for platform cast.media_player: Platform not found (No "module" named 'pychromecast.const')..
1 Like
Have you customized something in your setup? Check out https://github.com/home-assistant/core/issues/34955 and https://github.com/home-assistant/core/issues/34567#issuecomment-618127327.
thanks for the reply, ive never needed to reboot before, but I’ll try that now.
All connected to the network still
Make sure that you update Spotcast to the latest version (released a few days ago).
Spotcast had an older version of pychromecast and it interfered with the more recent one in Home Assistant 0.109 causing Cast devices to become unavailable. If you update Spotcast it should no longer happen.
Ok updated to the latest version of 109.1 without any issue (shooow) . I know from the past they were removing the known_devices.yaml which I use the NMap device tracker to get all the devices on the network. Been working fine for a year now. Went into the file and customized the names and icons on all the devices. After I rebooted from 109.1 upgrade it seemed to dump all knowledge of the devices and rebuilt the known_devices.yaml with just all the MAC address names by appending it to the bottom of the customized list I had. Now my question is do we just get ride of the that file and the use of NMap tracker now? Will HA just detect devices and add them? I noticed it removed all entities starting with “device_tracker.devicename” all except the Life360 ones. All the others are gone from the entities list. Now that is great because it was very cluttered with all that but now it can’t see my smart phone and some other things like it did before. So what I am asking is this supposed to be that way for the future of HA? And if so how do we bring devices in that don’t have integrations into HA like Android Phones, Tablets, etc.?
EDIT
Silly me - spotcast - forgot I’d even installed it. Ignore the dumbo idiot comments I replied with before (quoted below). For some stupid reason I was thinking it was a python library
Thanks for that. I’m using hassos so how can I update spotcast?
Back in the venv days I wouldn’t even have posted here until I’d tried all those sorts of updates!
Turns out it’s not a rename, it’s a domain migration (that’s not mentioned at all in the notes).
Remove it from your sensor config and add it to configuration.yaml as it’s own domain like you have switch, climate or sensor.
I’m having the same problem with mqtt cover with 2 shelly 2.5s on my garage doors. Both covers worked fine before I updated to 109. Now up and down are greyed out and stop is the only clickable button. The entity state of both doors show unknown so I have no idea what the problem is. Everything in the mqtt broker seems fine and the doors work and report their state in the shelly app. Just not in HA.
Not seeing that here 
Hi, I’m having the same mistake with tuya curtain, running in rpi 4.
Same problem here with shelly shutters. Is there a solution yet?
Has anyone actually posted a github issue for the covers problem? If they haven’t, it won’t get fixed. If they have, subscribe to the issue and get updates.
1 Like
No just a standard “hassio” install on a rp3b+. Nothing altered. Vacuum is core of wife approval factor so wont be updating again until this is resolved.
I dont know how to do that. I saw your answer to me yesterday and thought that someone did
That is a shame, poorly thought out IMHO.
I think all I did was tell you to be patient and not to ask the same question at 2 hourly intervals!
1 Like
That’s correct. But I thought (also) that you are part of team which can handle this, and you take a notice
Thanks for your reply! I’m not sure I understand though. Here are my entries in the configuration.yaml. For 109 I did change the name to synology_dsm but nothing works after that. I’m now wondering if Home Assistant will ever get to a stable situation, right now the work doing maintenance after “upgrades” makes me think I just go out and buy a commercial server like the Gira HS4.
- platform: synologydsm
host: 192.168.0.21
port: 5001
username: Synology
password: xxxxxxxxx
name: Lewiston NAS
monitored_conditions:
- cpu_total_load
- cpu_system_load
- cpu_user_load
- memory_size
- memory_real_usage
- memory_cached
- network_up
- network_down
- disk_status
- volume_disk_temp_max
- volume_disk_temp_avg
- disk_temp
- disk_smart_status
- volume_status
- volume_size_total
- volume_size_used
- volume_percentage_used
- disk_exceed_bad_sector_thr
- disk_below_remain_life_thr
Then in UILOVELACE.yaml I use the above sensors like this (just two shown as an example). With 109 I just get entity does not exist.
- type: horizontal-stack
cards:
- type: gauge
name: Max
entity: sensor.lewiston_nas_maximum_disk_temp_volume_1
unit_of_measurement: C
min: 0
max: 50
severity:
yellow: 35
green: 30
red: 40
- type: gauge
name: NVME
entity: sensor.lewiston_nas_temperature_nvme0n1
unit_of_measurement: C
min: 0
max: 50
severity:
yellow: 35
green: 30
red: 40