The developer of those integrations need to adjust the classnames.
https://developers.home-assistant.io/blog/2020/05/14/entity-class-names
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.
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.
Click the 3 dots in the top right corner
It needs to be updated by its developer to work with 0.110
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
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.
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?
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 ?
Something is wrong for me, it installs, but I can’t access to the interface. Verified version 0.110 from the command line. No strange errors in log.
I restarted after some minutes the raspberry and I have again version 0.109.6.
The same for me
Pretty ungrateful way of filing issues. Apparently you have no clue how much work they put in every update. Ease out before you come here. And before you do, bring log files with you.
Thank you in advance.
If like me, you are using Font-awesome icons by include html files in extra_html_url of frontend configuration, you have to update it.
All information can be found here : https://developers.home-assistant.io/blog/2020/05/09/custom-iconsets
You can’t use html file anymore. You have to use a .js file (include it in extra_module_url instead of extra_html_url)
Here is an extract of my js file :
var icons = {
"500px": [448, 512, [], "f26e", "M103.3 344.3c-6.5-14.2-6.9-18.3 7.4-23.1 25.6-8 8 9.2 43.2 49.2h.3v-93.9c1.2-50.2 44-92.2 97.7-92.2 53.9 0 97.7 43.5 97.7 96.8 0 63.4-60.8 113.2-128.5 93.3-10.5-4.2-2.1-31.7 8.5-28.6 53 0 89.4-10.1 89.4-64.4 0-61-77.1-89.6-116.9-44.6-23.5 26.4-17.6 42.1-17.6 157.6 50.7 31 118.3 22 160.4-20.1 24.8-24.8 38.5-58 38.5-93 0-35.2-13.8-68.2-38.8-93.3-24.8-24.8-57.8-38.5-93.3-38.5s-68.8 13.8-93.5 38.5c-.3.3-16 16.5-21.2 23.9l-.5.6c-3.3 4.7-6.3 9.1-20.1 6.1-6.9-1.7-14.3-5.8-14.3-11.8V20c0-5 3.9-10.5 10.5-10.5h241.3c8.3 0 8.3 11.6 8.3 15.1 0 3.9 0 15.1-8.3 15.1H130.3v132.9h.3c104.2-109.8 282.8-36 282.8 108.9 0 178.1-244.8 220.3-310.1 62.8zm63.3-260.8c-.5 4.2 4.6 24.5 14.6 20.6C306 56.6 384 144.5 390.6 144.5c4.8 0 22.8-15.3 14.3-22.8-93.2-89-234.5-57-238.3-38.2zM393 414.7C283 524.6 94 475.5 61 310.5c0-12.2-30.4-7.4-28.9 3.3 24 173.4 246 256.9 381.6 121.3 6.9-7.8-12.6-28.4-20.7-20.4zM213.6 306.6c0 4 4.3 7.3 5.5 8.5 3 3 6.1 4.4 8.5 4.4 3.8 0 2.6.2 22.3-19.5 19.6 19.3 19.1 19.5 22.3 19.5 5.4 0 18.5-10.4 10.7-18.2L265.6 284l18.2-18.2c6.3-6.8-10.1-21.8-16.2-15.7L249.7 268c-18.6-18.8-18.4-19.5-21.5-19.5-5 0-18 11.7-12.4 17.3L234 284c-18.1 17.9-20.4 19.2-20.4 22.6z"],
... YOUR OTHER ICONS ...
};
async function getIcon(name) {
var svgDef = icons[name]
var primaryPath = svgDef[4];
return {
path: primaryPath,
viewBox: "0 0 " + svgDef[0] + " " + svgDef[1]
};
}
window.customIconsets = window.customIconsets || {};
window.customIconsets["fab"] = getIcon;
Very sadly, duotone icons does not work anymore, because getIcon function expect only one path
Not sure if you got an answer to this but I got the same error. Do you have “retry” in your switch yaml? That’s what the error is saying is now an invalid option. Once I removed it mine came right back.