Breaking change for modbus. And i’m a little confused. Before it was easily in different points.
For sensors i had sensor: !include_dir_merge_list sensor/
And than inside i would make for example
modbus_vsr_alarms.yaml
modbus_vsr_temp.yaml
and so on. But now when everything should go inside the modbus config i really don’t understand how to split files.
@janiversen can you shed some light onto this?
Can somebody enlight is this a new formatting schema for all the integrations or just the modbus one?
You can do the same thing, it’s just indented now under modbus. This actually gives you the ability to granulate your configuration even more because you can separate modbus sensors from other platform integrations.
Ultimately, this will be the ending configuration for all yaml style configurations. It’s only available on a few integrations at the moment.
Thank you for the insight.
So now everything should be moved to let’s say modbus or sensors/modbus directory so it won’t break reading other integrations sensor.yaml files and than the include statement shall be used?
Is there a discussion somewhere to understand the logic behind the switch to new yaml style?
No clue where the discussion was had. But I’d wager it was for easy configuration of 2 modbuses with multiple sensors
Don’t see any point here as you could use a slave address to combine as many modbuses as you want.
- name: vsr500_time_year
slave: 1
register: 6000
register_type: holding
unit_of_measurement: Y
count: 1
data_type: uint
Ok, but the change was made. Getting upset with it now is fruitless
I have pm’ed @janiversen on github to take a look at this thread. This is actually a big question for the development of HA. Lets say that he sees it as perfect organization of things in his mind. But we are all different. For me it’s just another half an hour spent on breaking change just because someone thinks different and sees it will help to organize something, somewhere. No offense here. If there is logic beneath - than i should change the configuration.yaml
configurations with hubs are moving this direction, platforms are going away. I already said this above. I’m not sure what else can be said.
@petro Well a lot can be said. Just think about it. You have an army of enthusiasts who are already in there (How many installations?). Lets say more than 60% are already in the HA from OH and etc. More that a mln i believe. But you want to attract even more with the simplicity of configuration. That’s fine. But a breaking change because the yaml doesn’t look that nice. So 1mln spends 10 minutes and that’s 19 years of human life just spent on one breaking change, Think about it
This is a hobby for myself. I don’t mind breaking changes when there’s benefits to a configuration change. You’re making assumptions on why the change was made. Do you really need a reason why it was changed? If so, then maybe this isn’t the software for you. I can assure you, this won’t be the first breaking change you come across. I can also assure you, there was a reason for the change.
Was this the change that implemented it,
If so it was implemented March
And was in the April release and documented as breaking change for modbus and that old way was going away in a few releases