Replies: 1 comment 1 reply
-
You can indeed split the config files! The config library that we use supports various file namings, which are loaded from the config directory in the order that is specified on the linked page. The config options will be merged except for lists. So if you e.g. want a different set of integrations on one instance you'd have to specify the whole list of integrations again. Another note that I wanted to make, which may make your life a bit easier: You can use the ansible setup we provide to manage, upgrade and install room-assistant across many hosts from a single config file. I use it for my own setup as well. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have rolled out my room-assistant very successfully across my house now, so far 9 nodes (1 running on pi4 alongside HA, and 9 running on PI Zeros) - I have another 2 nodes coming and will potentially add a couple more to cover outdoor spaces like the garage, etc.
Its working really well and now I have my Lovelace interface dynamically updating depending on which room the current user is in, its transformational and very cool.
My problem is that config rollout changes is becoming a bit of a pain (mainly needed for new devices). My thinking is that I can script it and SCP/RSH the configs to each node. The challenge is that each local.yml file is slightly different because of the variables per node (instanceName, peerAddresses and integration specifics such as BLE maxDistance).
Is there anyway to break up the local.yml into separate files, so for example addresses/overrides can go in a separate include that is common across all nodes?
Is there a better way to do this?
Thanks... Ben
Beta Was this translation helpful? Give feedback.
All reactions