That worked thanks
You’re welcome 
Custom-header will need an update in order to work with this new release
2 Likes
Probably missed the cut off to get into the beta testing of 0.110.
Should be in next release
sorry guys but what are thee errors:
2020-05-20 12:08:14 WARNING (MainThread) [homeassistant.components.media_player] MediaPlayerDevice is deprecated, modify BrowserModPlayer to extend MediaPlayerEntity
2020-05-20 12:08:17 WARNING (MainThread) [homeassistant.components.switch] SwitchDevice is deprecated, modify ShellySwitch to extend SwitchEntity
2020-05-20 12:08:17 WARNING (MainThread) [homeassistant.components.switch] SwitchDevice is deprecated, modify ShellyFirmwareUpdate to extend SwitchEntity
2020-05-20 12:08:17 WARNING (MainThread) [homeassistant.components.light] Light is deprecated, modify BrowserModLight to extend LightEntity
I have checked the breaking changes but none of them apply in this case?
We were at 0.109.6, however not sure why that matter as patch releases do not indicate quality of the major release (if that is what you are trying to shoot at).
There is always a log file, the homeassistant.log anything in there?
1 Like
The developer of those integrations need to adjust the classnames.
https://developers.home-assistant.io/blog/2020/05/14/entity-class-names
2 Likes
Issue with Broadlink. Nothing in the release notes I can see other than this, that doesn’t seem related.
Fix connection problems in the Broadlink integration (@felipediel - #34670) (broadlink docs)
2020-05-20 20:58:29 ERROR (MainThread) [homeassistant.components.hassio] Invalid config for [switch.broadlink]: [retry] is an invalid option for [switch.broadlink]. Check: switch.broadlink->retry. (See ?, line ?).
Invalid config for [switch.broadlink]: [retry] is an invalid option for [switch.broadlink]. Check: switch.broadlink->retry. (See ?, line ?).
As soon as I comment out the config in switch.yaml, the error is gone.
Config is as per listed at the time of this post.
Looks like something broke Custom Header. If I have it enabled it shows empty bar at the bottom of the UI instead the header itself.
5 Likes
Maybe I miss something, but how can I add a third-party add-on repository. I don’t see the Add url like described here https://www.home-assistant.io/hassio/installing_third_party_addons/
I would like to add TasmoBackupV1.
1 Like
Click the 3 dots in the top right corner
1 Like
It needs to be updated by its developer to work with 0.110
1 Like
Just upgraded my virtualenv installation based on python 3.8.2 from 0.109.6 to 0.110.0 and got an error during the process, although the new version appears to be working fine. Log below, with a lot of irrelevant lines removed. I’d assume it was present in prior upgrades too, as the pytz and hass-nabucasa versions haven’t changed in this process, but can’t confirm that.
mark@pi:~$ source ~/homeassistant/bin/activate
(homeassistant) mark@pi:~$ pip install -U homeassistant
Collecting homeassistant
Downloading homeassistant-0.110.0-py3-none-any.whl (8.2 MB)
Requirement already satisfied, skipping upgrade: pytz>=2020.1 in ./homeassistant/lib/python3.8/site-packages (from homeassistant) (2020.1)
ERROR: hass-nabucasa 0.34.2 has requirement pytz~=2019.3, but you'll have pytz 2020.1 which is incompatible.
Attempting uninstall: homeassistant
Found existing installation: homeassistant 0.109.6
Uninstalling homeassistant-0.109.6:
Successfully uninstalled homeassistant-0.109.6
Successfully installed cryptography-2.9.2 homeassistant-0.110.0
1 Like
Great to see some movement on ZWave! I am happy to try the beta, but would love instructions for a non-docker installation of the new daemon. I guess I could work it out from the docker-compose file. (My HA installation is manual using a python virtual env on a unix server - I don’t really want to install docker.)
It is a shame the new Zwave brings in qt as a dependency.
2 Likes
I hope someone can give me a clue on how to fix an ongoing issue. Since early January most updates fail to load lovelace if I update from the UI. There are no errors in my log files to share. On this version (.110), I did the following from command line
Ha core stop
ha core update
ha core info (to confirm update)
Then
ha host reboot
Lovelace failed to load
ha host shutdown
lovelace loads correctly. I have no idea on what is going on as there are no error logs. I have asked what I can look for so that I can try and fix this. So far no one has offered me any ideas.
Thanks for looking.
Maybe don’t jump to the newest version after a major update?
2 Likes
If you havn’t done so i suggest logging an issue on github may get more results in fixing it
What would I log?
Try to give a much information as possible, copy your logs showing everything. The dev may ask you to check certain things or do additional logging
That would be the best place to start and at least it is logged
Update failed for me … RASPI 3B+ Hassio 64bit from last build
Returned in 0.109.6
What error did you get ?
1 Like