I need to manually alter the data base, and have to stop HA for that.
I ssh into the rpi and do a
hassio homeassistant stop
The rpi is working, it takes some time and the command seems to have completed. When I now want to edit the DB I always get the info that the file has been altered by someone else already. And yes, if I open HA in my browser it’s up and running again.
What am i doing wrong? I mean there is STOP, START and RESTART. I assumed STOP would make it stop and keep it stopped?!?
Guess what I tried FIRST?!
Same situation. It just comes back within 1min or two. Pretty pointless to have a STOP button that does the same thing as RESTART.
Available Commands:
info Provides information about the running Supervisor
logs View the log output of the Hass.io Supervisor
options Allows you to set options on the Hass.io Supervisor
reload Reload the Hass.io Supervisor updating information
repair Repair Docker issue automatically using the Supervisor (BETA!)
stats Provides system usage stats of the Hass.io Supervisor
update Updates the Hass.io Supervisor
You can try ha core options --watchdog=false
and then confirm it is false with ha core info
Don’t forget to set it to true afterward.
But alter the database? How much history are you keeping?
Deleting the home-assistant_v2.db and restarting would start a fresh one.
There’s also a sqlite addon for that, or the phpMYAdmin addon for Mariadb
Editing the db might itself cause corruption, however.
Updated to all latest supervisor 209 and latest Home Assistant 0.106.6 on HassOS 3.12, but the problem still remains. I call it a BUG, but maybe some plugin/addon is causing some issues.