I agree with others, a factory reset / factory default option should be exposed through the web GUI.
When you delete the config folder (or better, just rename it) then reboot, the config folder gets re-saved one last time before the reboot.
“Stop HA service”
ha host stop ? (there are options for shutdown, reboot, no stop though). since there are different types of HA OS install types, a factory reset option would be nice in the gui. (ie in my case of moving to a new home).
thanks
edit; looks like in my case the command to be used via CLI is:
ha core stop
mv config config off
ha host reboot
(hope above helps others - we still need a factory reset option in gui though imo) edit 2- wrong, still has my config in place - still no factory reset
Ring, Nest and Alexa are appliances. Home Assistant is not, and will never be an appliance.
You don’t have to. When you first install Home Assistant- no automations, no configurations, no integrations- make a full backup. Any time you want to start over, restore that backup.
Well, that’s your opinion and luckly we all get one. Lots of people here would disagree with your opinion though, which is why this thread exists.
Why is HA[OS] not an appliance? You install it onto bare metal hardware and it acts like an appliance all with UI etc. Just because you can install other things on the same hardware makes HAOS not an appliance?
No? That’s just a different hardware platform but it’s no more or less an appliance than it (HAOS to be clear) running on an x86_64 platform.
That seems like a very round-about way to achieve a very common[ly available] function of an appliance/device. Do I have to do that with an Android phone? No. Do I need to do that with most operating systems, no? Even MS Windows has a “factory reset” function. You don’t have to open a terminal and start formatting devices to factory reset it.
Is that same functionality on your phone, or your Windows computer, (or probably MacOS – I don’t really know, but would be surprised if that’s not there), or any of the IoT devices in your house so dangerous? In the wrong, hands maybe, but that doesn’t make it any less necessary.
Nobody is suggesting it should be a one-button-click and poof, everything is gone. Just like on any other device that implements a factory reset, the user should be given ample and clear warning and multiple opportunities to abort such a dangerous operation.
But ultimately, for the user that wants it and confirms through the warnings and dialogs, it should be available.
If we are going to ban all dangerous tools, I suppose we should ban all power tools, many kitchen appiances, cars, and everything else that is potentially dangerous.
Not round-about at all. It is the most efficient use of memory, very specific to your hardware and allows you to restore to a known start point. Best of all, it works regardless of your installation method.
Yes it is, given that literally nobody is going to know ahead of time that that is how they are supposed to effect the very standard operation of a factory reset. And then once they have figured that out, it’s too late. They don’t have a factory-fresh installation to do this very silly work-around.
Efficient use of what memory exactly? Surely you are not referring to the tiny amount of memory that the code for such a function would be using. That would be a simply ridiculous reason not to have this feature.
This is what I would support. At the end of the installation, automatically do a full backup to ‘factory_reset.tar’. If that file is wasting space, I mean ‘found’ in the backup folder, then show the Factory Reset option to the system menu. Because there are so many ways to install Home Assistant, this is probably the only way that you could do a “Factory Reset”.
Then stand back as people cry foul- I did a “Factory Reset” and all of my integrations and automations disappeared.
Hell, that’s not a bad idea at all. A backup file taken right after the installation is done or immediately after the onboarding is complete would do the job.
Adding an extra step at onboarding page with something like “Would you like to backup now to be able to factory reset?” is a relatively common step for other software installations. Also, given it’s a fresh install with no integrations and/or addons configured, there’s relatively very little space to waste.
What is $CONFIG? How do I delete everything under $CONFIG on a Generic-x86-64 Home Assistant OS installation?
Please explain it to me like I am a Windows user and know nothing at all about Linux, Docker, etc. What are all of the steps/commands necessary? Where do I execute them from? Do I remotely log in or do it from the CLI that is on the console?
In Home Assistant Operating System, the ha os datadisk wipe command wipes the data disk. The command deletes all user data as well as Home Assistant Core, Supervisor, and any installed add-ons.
The command ha os datadisk wipe marks the data partition (either internal on the eMMC or the SD card, or on an external attached data disk) as to be cleared on the next reboot. The command automatically reboots the system. Upon reboot, the data is cleared. Then the system continues to boot and reinstalls the latest version of all Home Assistant components.
I brought the home assistant to my vacation apartment with my other automation equipment. While it took just 10 seconds to reset the other devices, I spent hours trying to factoryr reset the home assistant. Why can’t we have a reset button that only permits a factory reset if a current backup has been successfully created?
Do I execute that from the ha > prompt on the console? I mean, I know I don’t. How do I get to a place where I run rm -rf * to erase $CONFIG? Even login at the ha > prompt just drops into the / filesystem of something. I surely do not want to rm -rf * there!
As an aside, these are the kind of details that I am saying that are unreasonable for any random user of HAOS to have to know just to effect a factory reset.
were able to reset my HA OS running on my X86-64 NUC. My Zigbee Home Automation has not been working since a power outage and I was looking for a simple way to completely reset the device because I think there might have been a problem with the SQLite database based upon the debug logs.
I would like to say that I think it would be useful to have a factory reset option; if not from the web GUI then at least from the CLI. It’s kind of a pain to reflash the device.