#location ha_run_lock file
1 messages ยท Page 1 of 1 (latest)
The why is simple, you had a running instance targeting that directory.
From now on, everyone will have this file. This file is how the logic determines if something else is also running against the same configuration.
It is not an indicator of 2 instances using the same configuration directory, but at least one.
So the issue(?) would be to move it into .storage.
Indeed, I'm seeing the same .ha_run.lock file in my config directory.
Yea moving it makes sense to me
not really a bug, more of a task / discussion
but at least it is tracked
The fact the lock exists is normal in applications (although we didn't have one)
issue created https://github.com/home-assistant/core/issues/153028
I noticed it because of the Github link in VSCode
I don't think it should be moved. I explained the challanges and reasoning in https://github.com/home-assistant/core/issues/153028