seperis

Oh, I backup religiously since Blue failed right after I moved and backup my backups on my laptop as well. (literally failed; I lost everything and had to run photorec and three other tools to pick out everything I'd done for the previous six months, since that I hadn't copied to a backup on my server because I was prepping to move at the time).

So far, OTBR is the biggest stopping issue since HA runs it but nothing sticks. I admit, moving zwave is my actual biggest dread; zigbees I can do probably in a weekend, but zwave is such hell to unpair and re-pair (thought it makes up for it by sticking forever). That's part of the reason I love Thread and Matter; they're almost as sticky as zwave once they pair, and while pairing them is variable (sometimes fast, sometimes not so much) they repair themselves pretty consistently if the outage is under 24 hours and you can deliberately unpair them fairly easily.

I've been running Home Assistant for roughly five-six years (Pi, then Blue, now Amber and a second instance on my server for network integrations like nmap and netgear), but since my SmartThings hub was taking care of zigbee/zwave, until now I used HA as a coordinator for every smart device ecosystem I was using (Hue, Wyze, Ring, Blink, Alexa, August, Arlo, et al). Sorry that wasn't clear.

While Ive started slowly adding zigbee devices directly, I haven't started with zwave and thread isn't working for me yet (OTBR is running but nothing sticks). And I really don't want to have my hub fail and all my thread/matter devices useless when I don't have anything that can access them.

So far, the OTBR on HA isn't working, but...if it's an age and device issue, it may be migrating the zigbee and zwave over to HA and leave my SmartThings for my OTBR devices will work for now. That may at least buy some time to work out how to make the HA's OTBR work.

It's not reliable on thread/matter.

I use zigbee, zwave, and thread. I've migrated half my contact sensors, a few motion and presence, and two rooms of light bulbs to thread, which HA is...questionable on, hence beginning my search.

The shell integration is why this happened.; I wanted to run the update script as a service so it could be triggered when the Supervisor or Core versions changed so it would automatically symlink my scripts in /usr/local/bin in the ssh_addon container. The shell integration runs in the homeassistant container, so that's when it became complicated.

So it can be done, it just--required a lot of steps and me making a mapping spreadsheet of all the containers. But! Automations and scripts run in the homeassistant container, while when you ssh, you're going into the ssh addon container which should have been obvious and really was once I finished mapping all the containers.

Goal: I need /usr/local/bin in the ssh container so I can run scripts over ssh and access my function library script easily without ./path/to/script.

Summary: ssh into HAOS from the homeassistant container with an HAOS root user (port 22222), run docker exec to get into the ssh addon container, then make your symlinks for /usr/local/bin.

(Note: this is ridiculously complicated and I know there has to be a better way. But this works so I win.)

1. Get access to HAOS itself as root: https://developers.home-assistant.io/docs/operating-system/debugging. Verify you can login successfully.
2. In homeassistant container:

• a. create an .ssh folder (/config/.ssh)
• b. add the authorized_keys file you made for step one.
• c. add the public and private keys you made for step one (should be in the ssh addon container).
• d. set permissions;

chmod 600 /config/.ssh/authorized_keys
chmod 600 /config/.ssh/PRIVATE_KEY
chmod 644 /config/.ssh/PUBLIC_KEY
chmod 700 /config/.ssh

• e. In /config/shell_scripts.yaml or wherever you put your shell scripts, add the script you want to use to update /usr/local/bin: UPDATE_BIN_SCRIPT: /config/shell_scripts/UPDATE_BIN_SCRIPT
• f. Restart HA.
• g. Check it in Developer Tools->Services

I have no idea how consistent the ssh addon container name is usually but it's different on all three of my installs, so insert your container name for SSH_ADDON_CONTAINER_NAME

Steps: login to HAOS, go into the SSH Container, and do the update. This is horribly messy but hey, it works.

UPDATE_BIN_SCRIPT

#!/bin/bash

# OPTIONAL: Update some of the very outdated alpine packages in both homeassistant and the ssh addon (figlet makes cool ascii art of my server
# name).   You'll need to run it twice; once for the homeassistant container, then again in the ssh container.  Assuming you want to update packages,
# anyway
# update homeassistant container packages
apk add coreutils figlet iproute2 iw jq ncurses procps-ng sed util-linux wireless-tools

# ssh into HAOS and access docker container
ssh -i /config/.ssh/PRIVATE_KEY -p 22222 root@HA_IP_ADDRESS << EOF
	docker exec SSH_ADDON_CONTAINER_NAME \
	bash -c \
       'apk add coreutils figlet iproute2 iw jq ncurses procps-ng sed util-linux wireless-tools; \
	if [ ! -h /usr/local/bin/SCRIPT1 ]; then echo "SCRIPT1 does not exist"; \
	ln -s /homeassistant/shell_scripts/SCRIPT1 /usr/local/bin/SCRIPT1; echo "Link created"; \
	else echo "Link exists";fi; \
	if [ ! -h /usr/local/bin/SCRIPT2 ]; then echo "SCRIPT2 does not exist"; \
	ln -s /homeassistant/shell_scripts/SCRIPT2 /usr/local/bin/SCRIPT2; echo "Link created"; \
	else echo "Link exists";fi'
EOF

echo "Done"

I am going to feel really stupid when I find out there's a much easier way.

Docker containers are designed to be immutable. The moment they’re stopped and recreated, any changes to them ads thrown out. You’re supposed to add a layer to your Docker image if you want to add command lines and such. That’s why it’ll keep deleting your stuff every time you update.

It took me until I put Home Assistant on my server in a docker container to realize what was going on there. I use docker more now, but it's really, really nothing like this.

Running the script inside Docker should put it in the right place, but I wouldn’t advice doing it that way.

That's what I've been doing manually over regular ssh (not the 22222 port one).

To work around the path issue, maybe consider using hard links rather than soft links?

That's what I think I need to do, but the only 'hard' links--at least according to multiple find -name/find -iname searches on the ssh 22222 port--are all in /mnt/data/docker/overlay2 and /var/lib/docker/overlay2. I get there's a working pattern with the overlays but dear God why.

Alternatively, you could figure out where HAOS stores the Docker config and add a volume definition of your own. You’ll probably be able to put all of your files in /usr/local/bin by adding a line like “- /path/home/host:/usr/local/bin” in the right place. I don’t know where this config is stored, though.

Okay that makes sense. I guess the first step is to get the container structure and volume.

Thanks so much! I'll update if I find the solution or die trying.

Both specific and in general 1.) Nectar mattress. The only mattresses i'd ever bought were from amazon and very on sale. Important Life Advice: whatever you have to do to make i happen, get a good mattress. Even my bed approves and it thinks everything is beneath it, including me.

2.) My bed.

Oh boy, here we go. This goddamn bed.

I bought it roughly twenty years ago and it literally took my entire tax return at my first job and then some to get it and the very first piece of furniture I personally picked out and bought for myself which may explain absolutely nothing about how I ended up like this.

It's fairly straightforward, plain four poster queen bed but so incredibly melodramatic no matter the room I put it in, this thing will dramatically not fit and carry on like it's actually in a castle tower in 1700s Frances waiting for a princess to sleep in it (it did not act like this at the store, okay). It has an unnecessary number of parts (some really could have been consolidated and a couple I'm not sure even have a function other than to add time to assembling it) every piece of it is awkward to move, even the parts that have no reason to be and don't look like they are, and every single piece is ten times heavier than than look or is reasonable, sane, or really should even be possible. The wood is dark and does a very cool dark gleaming thing, and it takes hours to clean and oil it to a soft gleam (so. goddamn. many. parts). Twenty-four hours later it's sitting there dull and dramatically telling everyone who sees it I never clean it and also use substandard wood oil

It takes a very base minimum of two people to even attempt to put it together and you better not have plans for the rest of the day because it doesn't matter how many times you have done this, somehow, you will always get six parts wrong because whoever designed this has another job making complicated puzzle locks that you will never solve and will die mad about it (this person is a sadist). Just looking at it in any given bedroom I live in, it makes me feel I should be wearing something long, white, and flowy while waiting for my angsty vampire lover to visit me in the dead of the night and not taking my night's sleep shorts and a tank top.

This bed is a snobby, judgemental asshole who acts like I didn't buy it at the goddamn Roomstore at ten percent off because it was a floor model.

But. it's a goddamn tank that's been in substandard moving vans and the backs of multiple trucks and dropped down stairs and sometimes forgets to at least look scuffed. It will survive all the wars and still give its occupants a great night's sleep. Those deceptively slim posts are strong enough to joust with a burglar, beat him to death, and then put back and rehang my very melodramatic bed curtains on them (though I'll need a little hysterical strength to hold them up for very long; I am not kidding how stupid heavy those thing are and should not be). I love this bed, it is my soulmate, and it is where I will sleep until I move to a convenient grave. I hope all of you are able to have one of these in your life and if you already do, you have my condolences; but it's ride or die now.

3.) The best headphones I can afford and a budget for potential upgrade/replace every two years (you don't have to use that timeline,but it works for me). Related: Sonos speakers. No, they are not the best in any class but they are good to really good in multiple speaker classes and are affordable--if you budget strictly and buy a piece at a time or watch for amazon sales like it's your job--for normal people.

4.) Kindle may actually be the most important single decision I have made in my life. I like books; I didn't want to use a screen. I did it and a decade and change greater with slowly degrading eyesight I bless the day I decided to try it every day. Currently on an Oasis.

5.) Giving up and budgeting specifically to pay a ridiculous amount of money for my jeans. Sure, the receipts legit horrifies me, but they fit perfectly,, are crazy comfortable, can pretty much survive anything I do to them (and I am hard on my clothes) and some have been with me since before the Obama administration and don't even have a loose thread on them. I have literally every single pair i ever bought and they still look great (and I never add up the cost of them all and what thing I could have bought with that much money, God).