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?
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!
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 
)
The view cards have disappeared, only the main one. Configuration in a file ui-lovelace.yaml
Help 
Same here, Also edit button disappeared.
Before upgrading read the breaking changes, and if you are on Supervisor there is an addon to check for possible problems.
Also check this thread for other issues.
And if your whole house and family depends on HA then dont jump blindly on new releases …
Dude
I have been a user since 0.17. I have seen this break so many times when major updates happen. I completely appreciate the work that goes in this but I sometimes feel they rush releases. My frustrations come out in my reposnses because I rely on Home Automation too much and it stresses me when it’s down. It’s my fault. I will turn off watchtower because I cannot control my environment with it turned on and surprising me with an update. I need a production and testing server though but my point is I shouldn’t really.
Anyway …
are you using custom header? if so remove till its been updated
0.110 contains this new integration ? (The blog article don’t mention it…)
i could be wrong but i think it now uses openzwave 1,6