Perfect… 
Reolink is a custom component not dwveloped by the core team, the dev of this component may need to update it (maybe a simple HACS upgrade is also enough) in order to work with the new version. This has nothing to do with the stability of HA, if you use a custom comoponent, you need to be aware that it may break at anytime. This is out of control of the core dev team. You even get a warning in your logs with custom components like
You are using a custom integration for XYZ 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.
Can you name some examples of breaking changes (not of custom components,that’s out of scope) that were not documented?
Also… have you tried restarting HA again. I do find often that immediately after an update to core, HA needs 2 restarts… one the automatic one and then another one before the errors disappear. The component may need to update something after the core update but it starts too fast and hence an error but a second update will fix it.
@Burningstone
My issue was with the custom component reolink_dev which I upgraded at the same time before upgrading hassio. It switched from using config file to using cameras as integration. This is not a hassio issue. Sorry for this.
regarding breaking changes: One major issue was with hass os 4.8
https://community.home-assistant.io/t/hassos-4-8-upgrade-breaks-my-install
Another issue happened a few months ago, I don’t find it now. But there have been some changes not marked as breaking changes.
Even if breaking changes are documented: They are in every update and actions are required nearly every time.
I compare hassio to fhem, which is running in parallel because I still have some Homematic devices integrated via fhem and I don’t know how to integrate them into hassio directly. hassio and fhem are connected via mqtt. In fhem never any upgrade did break anything. It is possible to upgrade and all keeps working fine. That’s why I would like to see a bit more priority for stability using existing configurations over breaking changes also in hassio. I understand that is very hard to be up to date with new devices and to avoid breaking changes. But it is a very big contrast compared to fhem.
In general, I am very happy with hassio: It was easy to setup, it looks good, configuration gets easier with nearly each release.
I don’t use Home Assistant OS, but there seem to be lots of issues with it in the past. However this is separate from Home Assistant Core, the actual software.
First of all, it’s not called hass.io anymore since more than 12 months.
I don’t think that’s a good comparison. FHEM had the last update around a year ago (which is like a century in smart home time xD) and it doesn’t even come close to the 1700+ integrations that Home Assistant provides.
Also, often breaking changes can’t be avoided without making the relevant integration useless. When a manufacturer changes their API or changes the way one needs to authenticate, the integration becomes useless and will not continue to work without the breaking change.
Recently lots of breaking changes have been due to integrations moving from YAML config to UI config to make it more accessible to the masses (good or bad idea, decide for yourself), this is something that can’t be done in one release (remember 1700+ integrations) and will take some time until it is finished.
In addition, I use Home Assistant since version 0.3x, so I lived through quite some releases and breaking changes and it never took me more than 30 mins to adjust my config (and I have a quite “complex” system with more than 100 physical devices) for the breaking changes, most of the time I was done in less than a minute.
2 Likes
Do you have entries in configuaration.yaml for reolink-dev? If so comment them out and set up from the integrations page.
After upgrading to 2021.1.4 from 2021.1.3 I noticed that the snapshots size are way smaller.
Before the size was around 400 MB. and now is only 50 MB.
The db its around 127 MB and hasn’t changed.
Also the snapshot is taken very fast, like 30 seconds, before took around 2 minutes.
Has anybody experienced the same?
(I havent removed addons or custom components).
Edit:
Looks like before the snapshot included addon backups but now it doesnt (only folders):
LOOK in the snapshots and compare them.
Hi there
First of all, many thanks to all dev that are working hard on our domotic engine i love !!
Since the last update 2021 1 4 i have an issue with mediaplayer :
"Logger: homeassistant.helpers.entity
Source: components/openhome/media_player.py:86
First occurred: 17 janvier 2021 à 10:34:08 (31810 occurrences)
Last logged: 10:01:41
Update for media_player.salle_cinema_2 fails
Update for media_player.petit_salon fails
Update for media_player.openhome_b428fbf5_f245_47a9_0000_00002cc24022 fails
Update for media_player.openhome_b428fbf5_f245_47a9_0000_0000713460ff fails"
Didn’t change anything, just update the OS and boum get these … am i alone ??
I just got a notification that Supervision version 2021.1.5 is available. I see the release notes on Github, but not here.
There is no release notes (except on GitHub) for the supervisor (supervisor != core)
Sorry not release notes but code diff. Oh duh. Thanks @makai supervisor != core. I should have thought before I typed.
This latest update is saturating the use of one of four of my core cpu processors (25% = 100% of 1 of 4).
What happend to the 2021.1.5? Was available and dissapeared.
today it has been released it has been version 2021.01.5 of the supervisor
You’re mixing up the core version (2021.1.4) with the Supervisor version (2021.01.5)
Not really surprising since the naming convention is horrible to keep things sorted.
I think with all of the confusion around this we’ve been seeing I think it would be a big benefit to nip this in the bud now to prevent the type of confusion and pain we had with the naming/re-naming of Hassio/HAOS.
Just add either supervisor_<version> to the supervisor or core_<version> to the core software. easy-peasy. No more confusion.
1 Like
The supervisor 2021.01.5 seems unstable, I’ve never had problems with the deconz like this before. I’ve now had two breakdowns in the deconz in two days. Deconz looses serial communication it seems.
Axis integration stopped working for me after the update yesterday, anyone else affected?
Edit: Forget about it, deleting and adding it again seems to have fixed the issue.
It is possible but I was pretty sure that I saw that info from binary_sensor.updater. Not sure now. Never mind, anyway thank You. And maybe there should be an option for auto update supervisor?