#HASSOS died after a Core upgrade
1 messages · Page 1 of 1 (latest)
eg. is there any way to enable dev SSH through the boot drive? I use WSL and I cba to update Windows just so that I can mount the ext4 disk.
I didn't expect for things to go that horribly. Especially when I want nearly ALL of the functionality in my house to rely on this thing. I DID NOT CUSTOMIZE ANYTHING PRIOR TO THE UPDATE. I just created an account.
You can connect a keyboard and monitor
Also, this is a good opportunity to check that you're actually backing it up
there's no HDMI output
https://developers.home-assistant.io/docs/operating-system/debugging/ may be an option here for you
i havent enabled any ssh
this is explicitly saying "get into the ssh addon and import your authorized keys"
Did you ... I don't know ... read the page I linked?
"use the CLI"
Woot, they over-complicated it 
Alternatively, the file will be imported from the USB when the Home Assistant OS device is rebooted
what USB
Did you stop reading before you got to the bit I just posted?
Use a USB drive formatted with FAT, ext4, or NTFS and name it CONFIG (case sensitive)
there's no explanation for the usb part
they stopped at "things to do"... but dont bother to explain how this is accomplished
can you confirm if its just auto mounting?
if you know that is
Alternatively, the file will be imported from the USB when the Home Assistant OS device is rebooted
Not auto-mounted, but automatically used
Just read that paragraph and follow it
I dunno it made sense to me
i wanted to understand what it's doing rather than just throwing random commands at the problem
They're fine, if you don't stop immediately you hit an issue. They kind of assume you keep reading.
perhaps im not the intended audience since i would honestly prefer to manage the OS myself
It imports a SSH key to the device and allows you to SSH to the device
Just by having a USB plugged in whilst it restarts
But yeah if you want more control then just go docker container install
Good chance to upgrade given this has happened
i heard that the addons compat sucks then
You don't need add ons
but i notiecd that addons dont even cover integrations
ie. theyre just a glorified docker-compose
so its kinda pointless
Correct. That's why you don't need add ons. You can just spin up your own container
They're easy if you want an appliance (HAOS)
either way ill at least try to debug this before quitting
Otherwise just use docker compose files and run container install along with any other containers you want
bricking after the first update on a completely unconfigured system is horrible
it just sat there for a couple weeks not running anything
hmmm im using an external SSD connected to a unipi neuron
maybe the 24V->5V converter is underpowered
(not that it's documented...)
Interesting choice of device for HA
But undervoltage/ low power can affect a pi badly
ssd is a wd red in a cheap-ish asmedia case
my intention today was to spend a couple hours writing an addon for the unipi sdk (which is only available as a raspbian image...)
aaaaand my anticipated issue happened
i can't boot it with a usb drive as i already boot from one
USB hub doesn't work?
it's stuck in a boot loop trying to start off the CONFIG drive
yep sounds like the end of my adventure with HAOS too
hopefully its just a bug there and not a 5v supply issue
Can always make integrations using any install method (if that's what you wanted) or add ons on any OS
ok thanks for help anyways folks, wrote some suggestions on how to clarify the docs, they indeed make sense after running into a wall following the guide 🙂
ill now spend some time reinstalling HA on stock Raspbian with sw components that I'm certain are reliable
Don’t know what your use cases are, but don’t expect Bluetooth to work well if you do that.