My new HA install is going well, but I was confused when scripts.yaml and automations.yaml didn’t seem to update and reflect entries I have made via the GUI, even though it clearly works. After drilling down on the Synology folders and shares, it seems that docker is using one folder to read the configuration file, abut writing to another for the scripts and automations file. I know I’m pretty clever, but how the hell did I manage to do this? I appear to have two config folders - one under the homeassistant user, and the other under docker\homeassistant\config and HA is using both, but for selected files.
The path docker/homeassistant/config is mounted to /config in the docker container settings. This is where the scripts and automations.yaml files appear to be read/written to.
I’m not sure how the hell I managed to get a /homeassistant share as well, but that is the one I’m seeing from my windows laptop. And this is the share the configuration.yaml seems to be read, along with groups.yaml
Hi, Synology uses a GUI to load and maintain docker images. I simply followed the instruction for docker on Synology diskstation install.
Synology NAS
I’ve just been experimenting again - it’s definitely using the configuration.yaml from one, but writing to the scripts and automations.yaml on the other.
Image shows the mount path. This i where it’s read/writing the scripts, but not the configuration file - I know because I removed it and the damn thing still loads.
One thing newbies should note - the scripts and automations folders appear to be overwritten with nice new BLANK files when you delete configuration.yaml and let HA recreate it.
I don’t know how this odd behaviour came about, but I appear to have fixed it, by stopping the container, deleting the errant share with the second lot of config files, restoring everything to the correct share then restarting docker/HA
This seems to have settled it down and it look like everything is writing to where it should.
