This is becoming a bad joke, machine totally unresponsive after this update, full hard reboot twice and still no response after 30 mins.
How do releases like this get out into the world ?
It’s no longer practical to rely on HA for services in my network… so after 2 years, I’m out.
Because they don’t brick machines as you have stated. If they did, then thousands of people would be posting about, which they are not.
What machine?
You have provided no information about your machine, or HA installation type, or troubleshooting steps you have taken other than ripping out the power cord. How do you expect any sort of advice or help to resolve your problem when you give no information.
If you’ve been using it for 2 years, then you know HA works. It would most likely be a configuration issue on your end with breaking changes, a hardware issue - but hard to know as you haven’t stated what your hardware is, or possibly even environmental - your network config.
same here. wont start after update to 0.118.5 from 1.???(dont remember the beta number
on rasp pi 4 4 gb
log so far:
2020-12-05 23:38:50 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-12-05 23:38:50 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for garbage_collection which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-12-05 23:38:50 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for fontawesome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-12-05 23:38:50 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for simpleicons which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2020-12-05 23:39:01 WARNING (MainThread) [homeassistant.setup] Setup of recorder is taking over 10 seconds.
2020-12-05 23:39:50 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: recorder
2020-12-05 23:40:06 WARNING (Recorder) [homeassistant.components.recorder.migration] Database is about to upgrade. Schema version: 10
2020-12-05 23:40:06 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=68 from 2020-12-05 18:23:38.783643)
2020-12-05 23:40:07 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/singleton.py”, line 42, in async_wrapped
result = await func(hass)
File “/usr/src/homeassistant/homeassistant/helpers/entity_registry.py”, line 527, in async_get_registry
await reg.async_load()
File “/usr/src/homeassistant/homeassistant/helpers/entity_registry.py”, line 432, in async_load
entities[entity[“entity_id”]] = RegistryEntry(
File “”, line 20, in init
__attr_validator_disabled_by(self, __attr_disabled_by, self.disabled_by)
File “/usr/local/lib/python3.8/site-packages/attr/validators.py”, line 228, in call
raise ValueError(
ValueError: ‘disabled_by’ must be in (‘hass’, ‘user’, ‘integration’, ‘config_entry’, None) (got ‘device’)
2020-12-05 23:40:16 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.
2020-12-05 23:40:17 WARNING (MainThread) [homeassistant.setup] Setup of person is taking over 10 seconds.
2020-12-05 23:40:18 WARNING (MainThread) [homeassistant.setup] Setup of cloud is taking over 10 seconds.
2020-12-05 23:41:06 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio, cloud, person
2020-12-05 23:42:06 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio, cloud, person
2020-12-05 23:43:06 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio, cloud, person
2020-12-05 23:44:06 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio, cloud, person
2020-12-05 23:45:06 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: hassio, cloud, person
2020-12-05 23:45:06 ERROR (MainThread) [homeassistant.setup] Setup of hassio is taking longer than 300 seconds. Startup will proceed without waiting any longer
2020-12-05 23:45:07 ERROR (MainThread) [homeassistant.setup] Setup of person is taking longer than 300 seconds. Startup will proceed without waiting any longer
2020-12-05 23:45:07 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of onboarding. Setup failed for dependencies: person
2020-12-05 23:45:07 ERROR (MainThread) [homeassistant.setup] Setup failed for onboarding: Could not set up all dependencies.
2020-12-05 23:45:07 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of frontend. Setup failed for dependencies: onboarding
2020-12-05 23:45:07 ERROR (MainThread) [homeassistant.setup] Setup failed for frontend: Could not set up all dependencies.
2020-12-05 23:45:08 ERROR (MainThread) [homeassistant.setup] Setup of cloud is taking longer than 300 seconds. Startup will proceed without waiting any longer
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of hacs. Setup failed for dependencies: frontend
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for hacs: Could not set up all dependencies.
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of fontawesome. Setup failed for dependencies: frontend
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for fontawesome: Could not set up all dependencies.
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of map. Setup failed for dependencies: frontend
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for map: Could not set up all dependencies.
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of logbook. Setup failed for dependencies: frontend
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for logbook: Could not set up all dependencies.
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of simpleicons. Setup failed for dependencies: frontend
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for simpleicons: Could not set up all dependencies.
2020-12-05 23:45:09 ERROR (SyncWorker_3) [homeassistant.util.yaml.loader] could not determine a constructor for the tag ‘!input’
in “/config/blueprints/automation/homeassistant/motion_light.yaml”, line 35, column 14
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.config] Invalid config for [automation]: Failed to load blueprint: could not determine a constructor for the tag ‘!input’
in “/config/blueprints/automation/homeassistant/motion_light.yaml”, line 35, column 14 (See /config/configuration.yaml, line 10).
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of mobile_app. Setup failed for dependencies: person
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for mobile_app: Could not set up all dependencies.
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.config] Unknown error calling automation config validator
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config.py”, line 765, in async_process_component_config
return await config_validator.async_validate_config( # type: ignore
File “/usr/src/homeassistant/homeassistant/components/automation/config.py”, line 77, in async_validate_config
await asyncio.gather(
File “/usr/src/homeassistant/homeassistant/components/automation/config.py”, line 59, in _try_async_validate_config_item
config = await async_validate_config_item(hass, config, full_config)
File “/usr/src/homeassistant/homeassistant/components/automation/config.py”, line 35, in async_validate_config_item
return await blueprints.async_inputs_from_config(config)
File “/usr/src/homeassistant/homeassistant/components/blueprint/models.py”, line 230, in async_inputs_from_config
inputs.validate()
File “/usr/src/homeassistant/homeassistant/components/blueprint/models.py”, line 107, in validate
missing = self.blueprint.placeholders - set(self.inputs)
AttributeError: ‘NoneType’ object has no attribute ‘placeholders’
2020-12-05 23:45:09 ERROR (MainThread) [homeassistant.setup] Setup failed for automation: Invalid config.
2020-12-05 23:45:19 WARNING (MainThread) [homeassistant.setup] Setup of zone is taking over 10 seconds.
2020-12-05 23:45:19 WARNING (MainThread) [homeassistant.components.scene] Setup of scene platform homeassistant is taking over 10 seconds.
2020-12-05 23:45:19 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform openhardwaremonitor is taking over 10 seconds.
2020-12-05 23:45:19 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform local_ip is taking over 10 seconds.
2020-12-05 23:45:19 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform garbage_collection is taking over 10 seconds.
2020-12-05 23:45:19 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform coronavirus is taking over 10 seconds.
2020-12-05 23:45:21 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform smartthings is taking over 10 seconds.
2020-12-05 23:45:21 WARNING (MainThread) [homeassistant.components.cover] Setup of cover platform smartthings is taking over 10 seconds.
2020-12-05 23:45:21 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform smartthings is taking over 10 seconds.
2020-12-05 23:45:21 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform smartthings is taking over 10 seconds.
2020-12-05 23:45:38 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform updater is taking over 10 seconds.
2020-12-05 23:45:39 WARNING (MainThread) [homeassistant.components.calendar] Setup of calendar platform google is taking over 10 seconds.
2020-12-05 23:45:39 WARNING (MainThread) [homeassistant.components.binary_sensor] Setup of binary_sensor platform rpi_power is taking over 10 seconds.
2020-12-05 23:45:39 WARNING (MainThread) [homeassistant.components.light] Setup of light platform flux_led is taking over 10 seconds.
2020-12-05 23:45:40 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform yamaha is taking over 10 seconds.
2020-12-05 23:45:40 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform openweathermap is taking over 10 seconds.
2020-12-05 23:45:40 WARNING (MainThread) [homeassistant.components.light] Setup of light platform smartthings is taking over 10 seconds.
2020-12-05 23:45:40 WARNING (MainThread) [homeassistant.components.weather] Setup of weather platform openweathermap is taking over 10 seconds.
2020-12-05 23:45:40 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform speedtestdotnet is taking over 10 seconds.
2020-12-05 23:45:41 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform samsungtv is taking over 10 seconds.
2020-12-05 23:45:41 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform samsungtv is taking over 10 seconds.
2020-12-05 23:45:41 WARNING (MainThread) [homeassistant.components.weather] Setup of weather platform met is taking over 10 seconds.
2020-12-05 23:45:41 WARNING (MainThread) [homeassistant.components.switch] Setup of switch platform tuya is taking over 10 seconds.
2020-12-05 23:45:41 WARNING (MainThread) [homeassistant.components.light] Setup of light platform tuya is taking over 10 seconds.
2020-12-05 23:45:42 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up upnp platform for sensor
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 199, in _async_setup_platform
await asyncio.shield(task)
File “/usr/src/homeassistant/homeassistant/components/upnp/sensor.py”, line 93, in async_setup_entry
device: Device = hass.data[DOMAIN][DOMAIN_DEVICES][udn]
KeyError: ‘uuid:6a76e133-9f8a-4616-9b17-55f5ca2116ea’
2020-12-05 23:45:42 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up upnp platform for sensor
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 199, in _async_setup_platform
await asyncio.shield(task)
File “/usr/src/homeassistant/homeassistant/components/upnp/sensor.py”, line 93, in async_setup_entry
device: Device = hass.data[DOMAIN][DOMAIN_DEVICES][udn]
KeyError: ‘uuid:5d4b047a-acd9-4600-9e29-63e909352a19’
2020-12-05 23:45:42 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up upnp platform for sensor
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 199, in _async_setup_platform
await asyncio.shield(task)
File “/usr/src/homeassistant/homeassistant/components/upnp/sensor.py”, line 93, in async_setup_entry
device: Device = hass.data[DOMAIN][DOMAIN_DEVICES][udn]
KeyError: ‘uuid:4748f7b5-45ce-4257-a9e6-ce6bc47a37c2’
2020-12-05 23:45:52 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform upnp is taking over 10 seconds.
2020-12-05 23:46:08 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: cast, zone, scene
2020-12-05 23:47:08 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: cast, zone, scene
2020-12-05 23:48:08 WARNING (MainThread) [homeassistant.bootstrap] Waiting on integrations to complete setup: cast, zone, scene
Could be related to this new diagnostic that monitors the system’s “health”. Basically it’s a ‘sanity check’ to ensure that all the infrastructure needed to support Home Assistant (docker, app-armor, network-manager, etc) is all present, functional, and up-to-date.
I’m running Supervised on Ubuntu so, naturally, that’s an ‘unsupported’ instance (because only the Debian distro is supported). However, recently it’s reporting that it’s also ‘unhealthy’. It indicates ‘Supervisor is not privileged’ and the linked troubleshooting page suggests I re-run the installation script (not ready to do that yet). The log also complains that Network Manager is the wrong version. It wants a minimum of version 1.14 yet Ubuntu reports 1.10 is the latest version (for Ubuntu). 
The cherry on top is that for the first time ever, Home Assistant crashed. We arrived home to a dark house. No browser access to Home Assistant. Logged in to the server and instructed it to perform a reboot. Home Assistant eventually started although it took longer than normal. Now I see the ‘unhealthy’ diagnosis and I’m not sure how to go about making it healthy.
All this to say, you’re not alone. I’ve also been using it for 2 years and this is the first time it fell on its azz, hard.
I didn’t post any details because I don’t want any help.
After two years I’ve lost count of how many times I’ve had to rebuild/restore the system after janky updates and now I’m just sick of it.
I’ve come to be overly reliant on it, and keeping it up to date has just become too much like hard work. So time to cut the cord and move on.
Move on to?
Just for info.
I’m still on 0.115, I was hoping to upgrade but I think I’ll wait a bit
I’m the opposite. Give me dev build or give me death. I’m pissed if something doesn’t break every time I pull down a new image. I get so bored with it otherwise.
Your experience is in an overwhelming minority of the 1% of 1% of users. It’s almost certainly not the fault of a “janky” update and more than likely to do with your system/config/hardware. I’ve updated 2 of my 3 systems to 0.118.5 today and have no issues.
After looking at some of your other recent posts, you had config issues which you ended up correcting and then had a working system. Why did you update if you had a fully functioning system? Just because?
There are HA users that are still on versions back in the 0.70.x’s, and even older, that have fully functioning and working systems. You don’t have to update.
After looking at some of your other recent posts, it seems you are using a Pi3 with an SD card, correct me if I’m wrong. You may have SD card wearing issues and it needs to be replaced, or you may have poor quality SD cards that are failing. It could be that you are having memory issues with the 1gb of the Pi3 and you should look at updating to some better hardware as a Pi3 is no longer the recommended entry level hardware.
However, if you are done and just want to bin 2 years of work with HA, there is no need to inform everyone, you can just stop using it and move on.
I am new to HA and just learning No problems, when updating to 0.118.5.
@kanga_who - I am very impressed with your helpful responses and the time you have spent on someone who has (almost) left the community!
But I’ve been working in IT for 35 years so i can say your last point (SD card) goes very well with the symptoms @tescophil describes
So, let me address a couple of things.
Only a few weeks ago I had to completely rebuild my ha instance after another JANKEY release introduced a bug into to the templates processor that caused the system to lock up at a very early stare in the boot process, so no logs or errors were generated. I bought a new class 10 Ultra ScanDisk SD card and rebuilt the system, so highly unlikely to be the SD card.
As for upgrading better hardware, are you kidding me ? I average 6% CPU usage and memory usage is under 50%. I should be downgrading to a much less powerful host. A Pi3B+ can perform 1.5 million times more operations per second than the computer NASA built to put man on the moon, but I now need more power than this to turn my lights on and off ?
Suggesting that is OK not to keep your software up to date, especially on a system that in many users configurations are directly accessable on the internet is just foolish
I’m assuming you are referring to the widely discussed (before hand) changes that were being made to templates? If not, please correct me. Changes to templates don’t require you to “completely rebuild my ha instance”, they require you to amend your templates.
That means nothing. The card may be a dud, corrupted flash, who knows, you may have even purchased a fake/copy. Don’t assume the card isn’t at fault when that is almost always the most likely point of failure on a Pi build.
I was to know this how? You posted no system information. Memory usage can spike and cause freezes and HA to stop, I experienced this exact issue myself some time ago while still using a Pi3 in my business. With no config changes whatsoever, I moved to an old Dell USFF machine, restored my snapshot and haven’t had an issue since. Don’t write off the possibility that it’s not the Pi3 unless you have tried something else to rule it out.
Foolish how? Unless you have dozens of ports opened up to the internet and don’t use SSL, then yes, you would be right, that would be foolish.
You assume wrong, I refer to the bug introduced I to 0.117.0
If you have no privacy or security concerns using old software to interact with the internet in general then I’m happy for you. Ignorance is bliss…
Great! Template Issue resolved then.
What’s the next issue you need to fix according to your logs?
Oh, I do. I do my best to secure my network by other means and not rely on HA software to do it for me 
I’ll add my data point into this thread.
I’m running Home Assistant OS (version 5.5) on an RPi4 using, and booting from, an SSD. I have a ZWave network (about 30 nodes) using an Aeotec Gen5+ USB Stick (purchased explicitly because it works directly with the RPi4). I’m using the QT OpenZwave Beta with the add-on Mosquitto MQTT broker.
Yesterday, the Supervisor informed me that an update (0.118.5) to the Home Assistant Core was available, so I installed it.
A couple of hours later, the Home Assistant Control Panel disappeared from my browser, and it informed me that the HA IP address was unreachable.
The ozw-admin application for Windows, which I use to monitor the OpenZwave beta had also closed, and when I re-started it, it could not connect to the OpenZwave beta.
I power cycled the RPi4, and when HA eventually came back up, the ozw-admin application connected to the OpenZwave beta - but the network was showing as completely empty of devices, not even the USB stick was showing.
I restarted the OpenZwave beta, but it made no difference.
I then rebooted HA, and once everything was back up and running, the Zwave network was back, but all my node names, set in the ozw-admin tool had gone.
Rather than re-do all the network names, and run the risk that the whole HA system would fail again, I restored a snapshot of the entire system to roll back to 0.118.4.
The system is now back up and running (using 0.118.4), but in future I’ll be extremely cautious about installing updates as soon as they are released. This is my production system, and I don’t want to run risks with it.
If I can also contribute.
HA running on Rpi4 8Gb boot SSD.
I have a lot of different devices Sonoff, Tuya, Yeelight, WiZ, Tado, HUE, nodemcu, various sensors, Google Home and several others. I updated to version 0.118.5 and everything works perfectly including the fixed google tts.
I can’t or don’t want complain to me.This project is amazing.
So you opened a topic just to rant about HA. Just keep it for yourself and move on, what’s the goal of your topic, to make others believe HA is bad because you had a bad experience?
I use HA for around 4 years now and never had any update that “bricked” my system. From time to time there was a breaking change that was not mentioned in the release notes as probably no one who has been testing it had this specific setup/config which caused the breaking change, but then just downgrade to the previous version, post an issue on github and wait for it to get resolved. Also what are you expecting from a free open-source beta product? That everything just works always and that the devs can test every of the 100 million possible combinations of setups and configs that people may have before they release it? Then we’d get a new version once every 100 years.
In addition as Kanga already said, no one forces you to update your system.
Are your running your system on RPI and a sd-card? I had same issues for month, but realized soon, that the sd-card is the real problem. these devices have a really short wear-off, so i urge you to use a ssd instead of sd-card.
i´ve done so a year ago, since then there were no more problems. just my 2c´s
greez
In those two years you did not learn how to create snapshots and back them up / restore them ?
I’m around for almost a year now, and had numerous updates, and most of them work flawless.
Some of them break something minor, but get fixed again in next release.
Occasionally it is my own fault as I use some unsupported custom config, which I need to fix myself.
One of the first things I learned is too take a snapshot and back it up.
I restored a previous version once (can’t even remember what was wrong exactly, but I was in a rush and had no time to figure out what was wrong). So I installed HA from scratch (took me 10-15 minutes), uploaded a snapshot and was back in the air again within 30 minutes with very little effort…
For me that is nothing to get ‘sick off’…
Now I made it even easier for myself; I run it on a HyperV virtual machine, of which I made a backup every now and then…so I can be back on track within 10-15 all together 
But yeah, as said, you don’t need to update it all the time…especially when you are not so comfortable doing it… and when you do…read the release notes and be prepared!!
After looking at some of your other recent posts, it seems you are using a Pi3 with an SD card, correct me if I’m wrong. You may have SD card wearing issues and it needs to be replaced, or you may have poor quality SD cards that are failing.
Having struggled with that same path, I can comment: why in earth does someone want to torture himself like that?
Spent 4 different sd cards from various brands etc, looked deeper into logging etc than was sensible, tried to figure out what processes were writing to sd card.
Then I just bought usb3 nvme ssd enclosure (~10€) and 32gb ssd (25€, don’t even want to know how much more I could have got with current prices). And suddenly empty feeling because that solved all my issues and it was possible to store sensor data over reboots etc.
Edit: proper sd cards built for continuous writing costed like 80-150€ in comparision.
Yeah, the cost of SSDs these days are so cheap there is no reason to persist with SD cards, but, why should @tescophil update anything when it is 1.5M times better that what was used by NASA to land on the moon 