If the HOA’s router supports UPnP/NAT-PMP/PCP then you might be able to use that to get some ports forwarded.

Is it possible to send the hint from OPNsense itself?

Yes, to me it sounds like you’re already getting a big enough prefix from your ISP (all devices getting a /64), but you’ll have to request a bigger prefix from OPNsense. I believe it should give you the options to do this when you set the IPv6 mode to DHCPv6 on OPNsense, but I can’t say if your ISP router will handle it.

I have also added all Cloudflare IPs in Jellyfin’s known proxies

You should only need to add the IP of the last proxy before reaching Jellyfin, which would be Caddy.

If you can’t get the VPS to work, alternatively there’s Cloudflare but last I checked streaming was a little out of their free terms. With it, you should just have to set your AAAA record and make the cloud orange, that way Cloudflare will proxy it, and IPv4 will work. There’s also Cloudflare tunnels which lets you host websites without port forwarding anything.

Just curious, what parts aren’t open source? At a glance it seems like they’re working on supporting self hosting and I couldn’t find any binaries.

My AMD Laptop has USB 4, which is effectively the same AFAIK.

Sure it let’s you use it asynchronously, but it predates and is not really compatible with JavaScript’s async/Promise API.

Debian testing has ‘updated’ to 5.6.1+really5.4.5-1 anyway, so as long as you’ve updated within the past few days it will have been downgraded to 5.4.5.

In theory PWAs can be configured to run offline, whether they’re doing that I don’t know.

The desktop app looks like it’s electron though.

A lot of external status services just send a HTTP request to a certain url, if it succeeds then it’s up, if it errors or times out then it’s down. They also usually let you check if TCP ports do the usual handshake thing if you aren’t using HTTP.

The response time can also be used to check if a site is running slower than usual too, and if you have a use for it you can usually specify the required response code for success.

Although I wouldn’t be surprised if GitHub has some per-server analytics they can also use to estimate the load, but Instatus would work as described above.

Sometimes these sorts of things are referred to as health checks, if you’re looking for search terms. For example Docker can be set up to poll a container’s web server every few minutes, and mark it as unhealthy it if it stops replying using the HEALTHCHECK instruction in the Dockerfile.

On the ISO keyboards I’ve seen, the enter key has way more than double the surface area than ANSI, so it’s definitely not ‘just rotated 90 degrees’. Also these people probably grew up with ISO and struggle with ANSI, just like you probably grew up with ANSI and struggle with ISO.

I doubt this will be any use, but my Telstra 4G has a public IPv6.

Yeah, I’d avoid the cloud version, but SNMP monitoring on the networked version is nice when you want multiple things to shutdown without relying on a single host.

Cloudflare Tunnels will let you proxy any port, as long as it’s HTTP(S) or SSH, even on free tier.

Also I believe there’s a thing now for proxying other ports anyway on free tier without tunnels, but I haven’t looked too much into it.

Machine Learning

Here’s the actual HACS add-on: https://github.com/richardzone/homeassistant-dht

The one linked before looks to just be a GPIO one, not a DHT one.

That’s what he did, but with a home assistant yellow as the gateway.

The video is about smart devices that are poorly designed and/or rely on cloud infrastructure being dumb. Jeff also wants smart devices that will literally only talk to home assistant, and will still work fine if home assistant is offline (like a light switch will still work if the server is down).

if you want to use different SSID for different VLAN

With newer versions of the controller you can actually use PPSK for a different VLAN per password (same SSID), but at the moment you’d be stuck using WPA2.

my vacuum is defying discovery because of UDP crossing the subnets.

This is likely more to do with broadcast addresses. The vacuum would be broadcasting it’s presence on its own subnet’s broadcast address (x.x.151.255), but homeassistant is only listening on it’s subnet broadcast address (x.x.150.255). As routers don’t usually let broadcasts cross subnets, I don’t think there’s a way for the host or VM to listen for them like this.

You could setup vlans and hopefully VirtualBox supports passing through vlans, so that homeassistant would have multiple interfaces. Or like other people have said, just increase the size of the home assistant subnet so that it’ll overlap with the IoT subnet and the broadcast address would be the same, but some devices might not like responding to a device that’s on a different subnet to them, without a router.