I found the problem.
After upgrading to 0.108.1, the HDMI_CEC stopped working and Home assistant core even doesn’t start.
So I commented the following lines on the configuration.yaml and the upgrade worked.
hdmi_cec:
devices:
TV: 0.0.0.0
Pi 4: 1.1.0.0Is it just me, or did the Resources tab disappear from /config/lovelace/dashboards as of this version?
Same … I suspect it has to do with the string length of the packet (using the broadlink.send service). The ones that work for me are shorter than the non-functional one.
IIRC that statement was about core support. Not for individual integrations
Me too! And I tried to reinstall but still the same…
modbus does not work after updating to 0.108.1
I just could get HACS back downgrading 
That’s not very nice
After update not able to log in or get ui anymore
dont understand ? what do we have to move ? from where ?
Sound logic to me!
It would be nice to fix that.
My command strings for Broadlink are very long indeed
Is it possible to shorten de command somehow? to make it run?
on off example:
switches:
tv_aan_uit:
friendly_name: "TV aan-uit"
command_on: "JgCwBJOVEzcSOBM2EhMTEhITEhMTEhI4EzYTNxMSEhMTEhMSEhMSExI4EhMSEhITEhMSExITEzcSExM3EjcSOBI4EjgTNxIABgaVlBM3EjgSOBITEhISExITExITNxM3EjcUERMSEhMSExITEhMTNxITExISExMSEhMSEhI4EhMTNxI4EjcTNxI4EzcSAAYIk5QTNxM3EjgSExMSEhMSExITEjcSOBM3EhMTEhMSExISExISEzcTEhMSExITEhMSExISNxMSEzcSOBM3EjgTNhM3EgAGB5WUEzcTNhM3ExISExITExITEhI4EjcTNxITExISExITExISExI3ExITEhMSEhMSExITEzcTEhI3EzcTNxI4EjgSNxMABgaUlRM3EjcTNxITExISExMSExISOBM2EzcTEhMSEhMTEhMSEhMSOBMSEhITEhMSExISExI4ExISOBI3EzcTNxI4EzYUAAYIkpQTNxM3EzYTEhMSExISExMSEzcTNxM2ExISExMSEhMSExMSEjgTEhITExISEhITEhMSOBMSEjgSOBI3EjgTNxM3EwAGB5OUEzcTNxM3EhMTEhITExISEhI4EjgTNxMSEhMSExITEhITEhM3ExITEhITEhMTEhMSEjcSExM3EzcTNxM2EzcSOBMABgaVlBM2EzcSOBITExITEhMSEhMTNhM3EzcTEhMSExITEhITExISNxITEhMSExITEhMSExM3ExITNhI4EzcTNxI3EzcSAAYHlJQSEBEQEBEREBEwEREQEREQERAQEREQEBEREBEQERAQERGTEhAREBARERAREBEQERAQERAREBEQEREQEDESMBIwETESMBIwEjASMBIAB8KVlBEQEBEREBAREDIQEREQEBEQERAREBEREBARERAQEREQEZMSEBEQEBEQERAREBEQERAREBEQEREQEBERMRAxETERMhAxETERMRExEQAHw5SUERAREBEQERASMBEQEg8REBEQEg8SDxIPEg8REBIPEg8SkxEQEg8REBIPERASDxIPEg8SDxIPEg8SDxIwEjARMRExETERMRExETERAAfDlJQREBIPEg8SDxIwEg8SDxIPEg8SDxIPEg8SDxIPEg8SDxKTERAREBIPEg8REBEQERAREBEQEg8REBEQEjARMRAyEDIRMRAyETEQMhAAB8SUlBEQERAREBEQEjASDxIPERASDxIPERAREBEQEg8SDxEQEZQREBEQERAREBEQERAREBEQERASDxEQEg8SMBExETEQMhAyETEQMhExEAAHxJSUEg8SDxEQEg8SMBIPERASDxIPEg8REBIPEg8SDxIPEg8SkxIPERAREBIPERAREBIPERASDxEQEg8SDxIwEjASMBExETEQMw8yETERAAfFk5MSDxIPEg8SDxIwEg8SDxIPEg8SDxIPEg8SDxIPEg8SDxKTEg8SDxIQERAREBEPEg8SDxIPEg8SEBEQETASMBIwEjASMBIwEjASMBIAB8KVlBEQEBEQERAREDIQERAREBEQERAREBEQERAREBEQERAREJUQERAREBEQERAREBEQERAREBEQERAREBEQMhAyEDIQMhAyEDIRMRAyEAANBQAAAAAAAAAA"
command_off: "JgCwBJOVEzcSOBM2EhMTEhITEhMTEhI4EzYTNxMSEhMTEhMSEhMSExI4EhMSEhITEhMSExITEzcSExM3EjcSOBI4EjgTNxIABgaVlBM3EjgSOBITEhISExITExITNxM3EjcUERMSEhMSExITEhMTNxITExISExMSEhMSEhI4EhMTNxI4EjcTNxI4EzcSAAYIk5QTNxM3EjgSExMSEhMSExITEjcSOBM3EhMTEhMSExISExISEzcTEhMSExITEhMSExISNxMSEzcSOBM3EjgTNhM3EgAGB5WUEzcTNhM3ExISExITExITEhI4EjcTNxITExISExITExISExI3ExITEhMSEhMSExITEzcTEhI3EzcTNxI4EjgSNxMABgaUlRM3EjcTNxITExISExMSExISOBM2EzcTEhMSEhMTEhMSEhMSOBMSEhITEhMSExISExI4ExISOBI3EzcTNxI4EzYUAAYIkpQTNxM3EzYTEhMSExISExMSEzcTNxM2ExISExMSEhMSExMSEjgTEhITExISEhITEhMSOBMSEjgSOBI3EjgTNxM3EwAGB5OUEzcTNxM3EhMTEhITExISEhI4EjgTNxMSEhMSExITEhITEhM3ExITEhITEhMTEhMSEjcSExM3EzcTNxM2EzcSOBMABgaVlBM2EzcSOBITExITEhMSEhMTNhM3EzcTEhMSExITEhITExISNxITEhMSExITEhMSExM3ExITNhI4EzcTNxI3EzcSAAYHlJQSEBEQEBEREBEwEREQEREQERAQEREQEBEREBEQERAQERGTEhAREBARERAREBEQERAQERAREBEQEREQEDESMBIwETESMBIwEjASMBIAB8KVlBEQEBEREBAREDIQEREQEBEQERAREBEREBARERAQEREQEZMSEBEQEBEQERAREBEQERAREBEQEREQEBERMRAxETERMhAxETERMRExEQAHw5SUERAREBEQERASMBEQEg8REBEQEg8SDxIPEg8REBIPEg8SkxEQEg8REBIPERASDxIPEg8SDxIPEg8SDxIwEjARMRExETERMRExETERAAfDlJQREBIPEg8SDxIwEg8SDxIPEg8SDxIPEg8SDxIPEg8SDxKTERAREBIPEg8REBEQERAREBEQEg8REBEQEjARMRAyEDIRMRAyETEQMhAAB8SUlBEQERAREBEQEjASDxIPERASDxIPERAREBEQEg8SDxEQEZQREBEQERAREBEQERAREBEQERASDxEQEg8SMBExETEQMhAyETEQMhExEAAHxJSUEg8SDxEQEg8SMBIPERASDxIPEg8REBIPEg8SDxIPEg8SkxIPERAREBIPERAREBIPERASDxEQEg8SDxIwEjASMBExETEQMw8yETERAAfFk5MSDxIPEg8SDxIwEg8SDxIPEg8SDxIPEg8SDxIPEg8SDxKTEg8SDxIQERAREBEPEg8SDxIPEg8SEBEQETASMBIwEjASMBIwEjASMBIAB8KVlBEQEBEQERAREDIQERAREBEQERAREBEQERAREBEQERAREJUQERAREBEQERAREBEQERAREBEQERAREBEQMhAyEDIQMhAyEDIRMRAyEAANBQAAAAAAAAAA"
the custom_components folder in your config directory should not have any stray files…all files must be in their respective folder…if you have any stray files delete those and then restart HA.
I think a citation is needed to figure out what was actually promised; I would be really surprised if it was feature parity for configuration.yaml.
Anyway, the UI has improved so much lately – for both users and developers – that it is reasonable to revisit this alleged promise.
Agreed, the GUI is so much better than it used to be and it’s so easy to add devices that are on your network now. For the “average” person this is a far better experience. What are people looking for when they want to set up a device with YAML that they can’t do today? Honest question.
people want to get what they ask, not what UI editor generates. and it’s two very different things.
You’ll probably get a variety of opinions. In my case, I manage most everything in YAML yet don’t mind using “config flow” to setup an integration. It’s convenient and reduces the chance of misconfiguration. Plus, I don’t have to restart Home Assistant to activate the integration (and related entities).
On the other hand, I would dislike having to manage automations and scripts via their respective UI-based editors (as they are currently implemented). The automation editor is adequate for simple tasks but is unable to handle complex automations. In addition, it stores the automation in a format that makes it miserable for humans to read (sorts everything alphabetically, collapses multi-line templates using newline characters, replaces double-quotes with dual single-quotes, and not only does not support YAML comments it removes any that may exist). So if you share an automation generated by the editor, the recipient sees something that looks like a transporter failure.
What are people looking for when they want to set up a device with YAML that they can’t do today? Honest question.
They want to store their configuration in a managed version control system.
The ability to rectify issues without having to delve into the risky area of editing the registry.
Documented YAML was/is easy.
UNDOCUMENTED JSON, not so much.
I have a problem with an onvif camera,after the update the static image doesn’t refresh. It seems that HA gets an updated image after reboot and never changes it. Can anyone help me?