Invalid config for ‘modbus’ at modbus.yaml, line 21: not a valid value for dictionary value ‘modbus->1->type’, got ‘rtuovertcp’ Invalid config for ‘modbus’ at modbus.yaml, line 21: required key ‘baudrate’ not provided Invalid config for ‘modbus’ at modbus.yaml, line 21: required key ‘bytesize’ not provided Invalid config for ‘modbus’ at modbus.yaml, line 21: required key ‘method’ not provided Invalid config for ‘modbus’ at modbus.yaml, line 21: required key ‘parity’ not provided Invalid config for ‘modbus’ at modbus.yaml, line 21: required key ‘stopbits’ not provided Invalid config for ‘modbus’ at modbus.yaml, line 23: ‘host’ is an invalid option for ‘modbus’, check: modbus->1->host Invalid config for ‘modbus’ at modbus.yaml, line 28: ‘retry_on_empty’ is an invalid option for ‘modbus’, check: modbus->1->retry_on_empty Invalid config for ‘modbus’ at modbus.yaml, line 29: ‘retries’ is an invalid option for ‘modbus’, check: modbus->1->retries
You are trying to update that was around 30 individual updates.
most of us this this in little steps one or 2 at a time.
I suspect you are having more problems that just modbus.
I’d be tempted to try a backup, then load HA new on new media, then restore you old files on it, but the problem is so many other things have changed that you will still have a lot of broken things.
M<aybe look at all the release posts between then and now and look for things you use and mitigate them.
Does the new documentation call for configuration parameters such as the missing baud rate, stop bits, bytesize, method, etc to be specifically inserted in your code that may have been using defaults in the past? They may also have been stored previously in a config file that may have been deleted or overwritten by the updates.
Pretend you are setting this up from scratch - where do you have to specify these things?
Is your yaml structure still correct? Sequence expected, spacing expected? Around line 21 in modbus.yaml is where I would be looking first, and what is accessing that file