Update failed for me … RASPI 3B+ Hassio 64bit from last build
Returned in 0.109.6
What error did you get ?
1 Like
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.
9 Likes
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 
2 Likes
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.
I just changed that to test about 5 mins ago, and updated my PR on Github.
The docs have not been updated before the 0.110.0 update has been pushed out, and no breaking change for that config entry is listed that I can see.
PR submitted to adjust docs.
Before update I have 3 columns, but after update only 2 columns in my lovelace view… Any way to get 3 columns back?
3 Likes
I just wanted to say that I upgraded to this version and I am really loving how this project is coming along. All of these little things like the calendar being redone and the user friendliness in the UI is greatly appreciated!
6 Likes
http and alarm_control_panel (manual) both broken for me even after following new docs and taking into account breaking changes.
Those are issues with custom components, please report them to those authors.
My ONVIF camera is not longer working!
Before video was working but PTZ-mode was not. Now nothing is working anymore!
These messages can be found in the log:
2020-05-20 14:05:53 WARNING (MainThread) [homeassistant.components.onvif] Couldn't get device 'Rundum' date/time. Error: None
2020-05-20 14:05:55 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'Rundum', but will retry later. Error: None
2020-05-20 14:05:55 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 5 seconds.
2020-05-20 14:06:07 WARNING (MainThread) [homeassistant.components.onvif] Couldn't get device 'Rundum' date/time. Error: None
2020-05-20 14:06:12 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'Rundum', but will retry later. Error: None
2020-05-20 14:06:12 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 10 seconds.
2020-05-20 14:06:24 WARNING (MainThread) [homeassistant.components.onvif] Couldn't get device 'Rundum' date/time. Error: None
2020-05-20 14:06:26 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'Rundum', but will retry later. Error: None
2020-05-20 14:06:26 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 20 seconds.
2020-05-20 14:06:48 WARNING (MainThread) [homeassistant.components.onvif] Couldn't get device 'Rundum' date/time. Error: None
2020-05-20 14:06:50 WARNING (MainThread) [homeassistant.components.onvif] Couldn't connect to camera 'Rundum', but will retry later. Error: None
2020-05-20 14:06:50 WARNING (MainThread) [homeassistant.config_entries] Config entry for onvif not ready yet. Retrying in 40 seconds.
Before I used this entries in configuration.yaml:
ffmpeg:
camera:
- platform: onvif
host: 192.168.178.32
port: 5000
username: <Username>
password: <Password>
rtsp_transport: udp
extra_arguments: -rtsp_flags none -rtsp_transport udp -q:v 2
name: Rundum
Now I set the name to “Rundum”, host to “192.168.178.32”, port to “5000”, username to the same username, password to the same password, extra options to: “-rtsp_flags none -rtsp_transport udp -q:v 2” and transport to “udp”.
But it doesn’t work!
Might have nothing to do with 110, but since I wanted to use openzwave (beta) I uninstalled zwave2mqtt add-on but the left menu item is not going away. Any hint?
Invalid config for [alarm_control_panel.manual]: [arming_time] is an invalid option for [alarm_control_panel.manual]. Check: alarm_control_panel.manual->triggered->arming_time. (See ?, line ?).
Invalid config for [http]: [external_url] is an invalid option for [http]. Check: http->http->external_url. (See /config/configuration.yaml, line 4).
Have or haven’t these functions been updated correctly?
For the new Tuya integration from the yaml … I’m clicking the integration for Tuya but not getting any action or result. I have tried with the exisiting Tuya yaml code in config (username etc) and with that deleted. Same thing. No install of the integration.
This update looks great, thank you devs for all of your hard work! I’m particularly excited about the not condition, it’s a small thing but it will allow me to convert a few automatons with template conditions to the automation editor.
Can someone please elaborate on what the benefits of the new openzwave platform are or will be? I’m using the current z-wave integration, so I’ll probably migrate once there’s an easy path and a compelling reason to do so (e.g. When it is indeed deprecated in a year 
)
1 Like
The view cards have disappeared, only the main one. Configuration in a file ui-lovelace.yaml
Help 