Mastodawn

So I read this like, fourteen hours ago, and I started to reply that no, I can’t; Orbi Pro 6 will only allow a port to carry one VLAN–which you have to assign–unless it’s a Orbi satellite or my Orbi router-turned-AP. Devices won’t. I tested this a lot.

But. I hadn’t tested my switches, at least since I got these specific ones. Apparently, my Netgear switches also get the full trunk, because they’re all smart managed. So I set up the VLANs in the switches, assigned them to ports, and moved Yellow onto the appropriate port. I also had to turn off mDNS sharing between VLAN1 and VLAN20/VLAN30 very quickly because mDNS nightmare but–yeah, that worked.

Thank you. I hadn’t even thought about it because it failed (badly) with my other switches, but here we are. Running discovery tests now with the IoT VLAN to see if everything is still reachable and do some fine-tuning.

Seperis Dec 13

Home Assistant and VLANs/Other Networks

https://lemmy.world/post/40161950

Home Assistant and VLANs/Other Networks - Lemmy.World

So I moved a few months ago, and only just now had time between work and school to set up my smart home again. Which turned out to be a sort-of blessing, since HA did some updates and the one for sensor and binary sensor templates dramatically screwed me as I template a lot. It also gave me the opportunity to upgrade my Yellow’s Pi module, and I found (though haven’t installed) an internal z-wave module for it, which I’ll do when I’m off for Christmas and New Year. However, since I am starting fresh, I thought I’d ask around on best practices. So I use the Orbi Pro 6 which has three primary and one guest SSID, and I have it behind a Google router in its DMZ because we have Google Fiber here. Which also turned into an advantage because I wanted to a.) do full IoT isolation and also b.) have someplace to put my singleboard computers and my servers that’s safer but still have internet access plus c.) avoid wifi congestion (three VLANs plus the primary router’s wifi takes care of that nicely). On the Orbi: VLAN1 is primary and where I keep my singleboard computers, my servers, two TVs, X-Box, Switches, and my laptop. VLAN2 is for IoT hubs, cameras, Roomba, etc. VLAN3 is strictly lightbulbs, which sounds ridic but when I did a wifi analysis they really really super really take up a lot of wifi bandwidth, I’ve been slowly replacing with Hue and other zigbee, but it’s in progress. I may move the cameras there as well. What I need to figure out is the best way to connect everything to Home Assistant. What I was doing was attaching Yellow to VLAN1 by ethernet and VLAN2, VLAN3, and the primary SSID by wifi. On the Orbi router is an mDNS gateway page so I set it to connect my VLANs so they can exchange some data. But now I have some time to design, and also, I can run multiple instances of HA on one of my servers. I had been doing that anyway to test any chances and test and run Add-ons that I wrote myself, just not a permanent one (again, test instance; I murdered it a lot and spun up a new one when things got weird). So for anyone who deals with multiple SSIDs or VLANs (or just has an opinion): keep Yellow as is or go with the multiple instances and use Remote Home Assistant (which I used with my test instance and it worked very well) to send entities in the VLANs back to Yellow? Anyone?

Show thread

Seperis Oct 12, 2024

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.

Show thread

Seperis Oct 10, 2024

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.

Show thread

Seperis Oct 9, 2024

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.

Show thread

Seperis Oct 9, 2024

It’s not reliable on thread/matter.

Show thread

Seperis Oct 9, 2024

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.

Seperis Oct 9, 2024

Home-Assistant Compatible Hub Needed

https://lemmy.world/post/20656172

Home-Assistant Compatible Hub Needed - Lemmy.World

My SmartThings Hub is (slowly) starting to error out more and more. I’m doing a soft reset monthly to keep everything up ( I did a hard reset about a year ago when I moved), which works, but I think it’s time I start learning a new hub, preferably one not discontinued. My original plan was to put everything in Home Assistant when this time came, but a.) I really like it as my home coordinator with my custom scripts and addons and I don’t want to mess with what is working right now and b.) while I’m getting the hang of running zigbee on there, zwave is in progress and thread…not really working most of the time. So. I need to buy a general all-protocol hub; any recommendations that are fully compatible with Home Assistant? One with custom scripting would be a huge plus; I miss doing that in SmartThings.

Seperis Jul 19, 2024

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.

Seperis Jul 19, 2024

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.)

Get access to HAOS itself as root: developers.home-assistant.io/docs/…/debugging. Verify you can login successfully.

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.

Debugging the Home Assistant Operating System | Home Assistant Developer Docs

This section is not for end users. End users should use the [SSH app (formerly known as an add-on)] to SSH into Home Assistant. This is for developers of Home Assistant. Do not ask for support if you are using these options.