I feel like I’ve created some sort of down spiral since yesterday. I had a few weird errors that popped up yesterday. I didn’t quite understand how they came about, but I decided (because I’m a noob) to just restore my backup from 2 days ago.
I let it “restore” all night, from a 285mb backup. I’m running my system on a Rpi4 SD card, and have never had any serious issues. Been running for about 6 months so far. This morning, I realized I was still not able to connect to HA. I could see that the Rpi was still connected to my router though. In what was either genius or pure self-destruction, I turned the Rpi off, then on again. HA booted up, with few small issues (like Smartthings integration not connecting, which I’ve read is common after a restore.) I removed and reconnected the integration. Things were good.
Then upon restart (since smartthings hadn’t fully loaded yet), I got a few configuration errors with my automations. I made sure all of my smartthings devices reloaded, restarted, then everything seemed to work, again!
Doing a little bit of tinkering and changing some of my media player automations, I also updated HACS, and restarted without any issue. I went to perform a full backup, and this is where my troubles began again. The backup failed. I checked around, and saw the following:
Error loading /config/configuration.yaml: unacceptable character #x0000: special characters are not allowedin “/config/automations.yaml”, position 0
My automations all still show up on the tab, but when I opened file editor on my phone, the automations.yaml appeared blank. So I went back to my computer, and this time I tried to run Studio Code Server, which gave me the following error:
Failed to start add-on
Can’t create container from addon_a0d7b954_vscode: 409 Client Error for http+docker://localhost/v1.42/containers/create?name=addon_a0d7b954_vscode: Conflict (“Conflict. The container name “/addon_a0d7b954_vscode” is already in use by container “87eeae6e7c1f18705974269c4ec2631bc4704d260d1d03f8774a218d196af0cc”. You have to remove (or rename) that container to be able to reuse that name.”)
Similarly, File Editor returns with:
Failed to start add-on
Can’t create container from addon_core_configurator: 409 Client Error for http+docker://localhost/v1.42/containers/create?name=addon_core_configurator: Conflict (“Conflict. The container name “/addon_core_configurator” is already in use by container “e26eaa4d1c0e10e6744aa293f0e79453994118857cbcc8cd734968a67230a395”. You have to remove (or rename) that container to be able to reuse that name.”)
At this point, I’m way beyond my depth. If the worst that happens is that I have to redo my automations, that will suck, but it would beat redoing everything.
I’m sure there is lots more info I need to provide for anyone to help, and I’m happy to provide anything else I can (I might need told how to find some things)