I was using Home Assistant in a docker container, and moved it over to a VM running in Proxmox. I did a restore of my configuration (which HA counted as a partial backup), and after I did it I’m getting some notifications about “invalid config” for the following entries:
recorder (Show logs)
logbook (Show logs)
history (Show logs)
energy (Show logs)
default_config (Show logs)
Okay, this makes sense to me, the docker had two containers, one for homeassistant and one for postgresql, but the VM is probably using SQL lite. And I think the rest of them are all related back to the recorder not starting correctly. What steps do I need to take to get this up and running again?
Setup the VM to use the SQLite db or enable the postgres db. You’ll need to use the docker or setup another vm for Postgres. Depending on VM you can run postgres in the VM with HA.
It is probably trying to connect to db but cannot. Is frontend available or HA just fails to start?
Front end is available, I may have worded it awkwardly, but I was specifically asking how do I set it back up to use the SQLite db.
The docker I was using was running on TrueNAS, it works great for 99% of use cases but there was one very large flaw with running it on TrueNAS. Anytime you update TrueNAS (scale) it gets rid of anything you added to the base system.
So I wanted to use bluetooth with Home Assistant, but TrueNAS doesn’t include the bluetooth stack, so I had to find the right package, manually download it, install it, and copy the correct firmware for my bluetooth dongle.
Then I had to do it again anytime I wanted to update my TueNAS server. Ditto for Wake-on-lan.
They were minor inconveniences but I decided to cut out the middle man and just make a VM. I have a Proxmox box and I could use that to run a docker container, but there are some add-ons I want that you can’t get through docker containers so now I have an mixed environment that gives me the best of both worlds. For things that I can use with docker containers, I use that (like my mosquitto broker or zigbee2mqtt) and for things that need a full add-on I can do that as well.
You’ll loose all historical db info. I’m sure it can be restored but not sure how to move data from your old db to the new sql db.
You should be able to output Postgres to SQLite file and just put it into config directory and have it picked up by HA. I recommend if you do this you use the same HA version at first run then upgrade HA to ensure any db changes due to version update are performed
Thanks, I had a similar problem with wrong url for recorder and was searching a solution sinces hours !
It was blocking other modules like energy dashboard that miraculously reappeared !