But for the owner community … a question.
Since I back up my PROD then restore that to my new PROD and restore to a new DEV … both restored from the exact same backup.
Both my DEV and my HOME server show connected to Nabu Casa.
???
Did I get a free account? I doubt it.
Different internal IPs, same house. Both show connected.
There is a solution and it works HA OS installing on Intel Atom minipc - #2 by Ellcon
I’m glad two weeks ago I migrated from a docker install on my NAS which is ARM based. If it wasn’t for the problems I had with it not managing my zigbee devices well enough, I’d probably would been looking at replacing it closer to end of year. Sucks that those devices are probably overlooked in stats.
you could check what your NC account says.
however you might have the issue where remote access toggles,
and only the last backup from both devices is saved.
If this is the case, I would consider this a serious issue.
Hi, I have installation on Linux homeassistant 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux - Raspberry Pi 5 Model B Rev 1.0. Why I reveive the depreciation after upgrading to 2025.6.0?
Is it just me or does the section on, “how to migrate”, not actually contain any instructions on how to migrate. Especially for migrating to HA container.
I see on the chart, there are annotations for 1 and 2, but where are those defined?
Migrating to container, suggest that there will be add-ons that need to be migrated. That needs a detailed process about using docker or other tools.
From what I understand, most add-ons can be converted to a docker compose yaml, and installed and updated pretty easily. Not sure about automatic backups though.
It is certainly not going to be as convenient as a built-in UI like Supervisor.
There’s also the loss of a convenient feature of automatically adding a sidebar for some add-ons that have their own UI. Frigate NVR is an extremely popular add-on for home assistant.
Thats a shame.
The Supervised installation method is amazing, offers all functionality while being able to run your own OS. Supervised is literally one of the reasons I chose Home Assistant.
For me, none of the the other available options are viable. I have plenty of Add-ons and one-click updates are also quite helpful, so a normal container wont do.
Also, I run a standardised debian OS image on all VM’s and I have exactly zero intention of installing HA OS.
Is there any change that binning the Supervised Install might be reconsidered?
I understand no longer supporting “core” installations, as it can usually be replaced easily with the simple container.
How does HA OS handle it’s Home Assistant installation under the hood? I expected HA OS to basically just be Supervised with an OS, but I guess that is not the case?
Is there going to be a migration/conversion tool for going from supervised to container?
It’s essentially the same thing already. HA Supervised is already home assistant running as a container. And all of the add-ons are containers already too. So it should be just the supervisor container going away and being deprecated.
For add-ons you will have to
(A) run HAOS or
(B) build your own docker containers or
(C) install the extra software on your OS of choice.
removing supervised is a real problem.
the reason i switch to debian + supervised is because HAOS does NOT let you manually set time.
this is a breaking issue as it REQUIRES internet (NTP server) for that.
no internet, wich can happen often in winter here, and voila, your home automation trigger with massive offset.
and time based trigger in a home automation setup is one if not the main use case.
given that you remove this install method, will you finally introduce a way to manually set time in HAOS should there not be NTP available?
I think I recall a thread where I guided an user to set the time manually.
It was just not all the traditional Linux commands that worked.
Yep, on supervised here and never trust phoning home stuff.
HaOS misses other aspects of operations, backups, central logging, vuln scans, segragate admin/iot/storage network. It’s a black box appliance.
Container makes it may headache to update, handle add-ons etc.
Supervised was the perfect solution, allowing me to manage the environment while HA managed it’s own ecosystem.
Keep using it then.
i’ve asked in another thread quite some time ago, but ultimately it never worked
i spent quite some time reading several threads on it, but to no avail but to go the supervised way
basically all commands resulted in an answer like “command not allowed”, and the only working solution (with HAOS) was either NTP, add a RTC module to RPI or switch hardware to one with RTC
chrony requires NTP, or make the RPI become the network NTP. wich is not the solution, because, well, there is still no way to set time so not only the rpi is out of sync, but now the rest of the devices on the network is as well.
my use case is a fallback when there is a loss of power / internet, power usually get back or i have ways to get it back, and i don’t need accurate time, just it to be accurate to say a minute so that heating schedules etc… are reasonably working
Does gps go down too with the Internet? I’m guessing no.
Buy a USB gps device and run NTP on your LAN. A pi zero would probably do that.
All that hassle just for the triviality of getting the accurate time into HA? OMG 
does not work with HAOS, only supervised.
oops
yup, all i wanted was “just”, like any linux, to set date from a terminal but it’s locked
