#KNX YAML default_entity_id
candid vessel
The idea was to make yaml entity configuration better for professionals installing HA for their customers. It seems common to use scripts there to generate yaml out of some export files or excel spreadsheets.
harsh iris
I have heard that people did that for Bayesian
candid vessel
To enable them to have a nice installation without having to click around in UI and manually edit every entity - which for knx can be plenty - I'd like to add the default_entity_id option, and as a follow-up unique_id (according to ADR 0010 / 0007)
I don't think it is needed for UI configured entities as those have to be manually created anyway - there's no batch creation
KNX YAML default_entity_id
little lodge
unique_id definitely makes sense, but what exactly is the use case of manually defining each entity_id?
candid vessel
It's a default - it doesn't overwrite, but sets initial.
So when setting up a big yaml you can have nice friendly names (name) while assigning independent entity_ids that may be easier to find for each entity.
For unique_id, we currently generate this from some other config values - which works fine like 99% of the time.... this key shall cover the 1% and also enable safe reconfiguration of those addresses that were used to generate.
What I'm currently not sure about is: shall there be any sort of migration if a user decides to add a unique_id key for an existing entity at some point? Or is it enough to just document that this is a bad idea?
little lodge
It's a default - it doesn't overwrite, but sets initial.
So when setting up a b...
We generally prefer auto generated entity_ids that reflect the name though.
candid vessel
That's the default anyway. It's an optional key. But so is name, so currently some configure their desired entity_ids as name and then change the name in UI 🙃
In this case both, the name and the entity_id, are user generated - as it can't be retrieved from an API or something (protocol integration).
candid vessel
So, any final verdict on this?