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.

Reminds me of The Truman Show.

I believe 5.6.0 was in Debian testing for almost a month too.

Nah, it’s designed for device manufacturers to preload but anyone can install it.

Here’s the free device manufacturer version: https://apps.microsoft.com/detail/9n4wgh0z6vhq

That’s not really your code, more so you haven’t setup a .gitignore to not commit not your code.

And I really should get used to how debian works with su.

I only know because installing sudo is usually the very first thing I do whenever I have to install it haha.

I might be wrong, but I believe Debian ships without sudo, only su by default (or at least if you configure a root password in the setup).

I’ve run kill -9 and similar heaps before, but weirdly this comment reminded me of this: https://youtu.be/Fow7iUaKrq4

I think the i and h would the the same height as the T though, so I kinda doubt it’s Timothy.

Nah, apparently it’s completely valid to end IPv6 addresses with a 0. And I haven’t done much research, but it seems IPv6 really doesn’t have network addresses the way IPv4 does.

Also you can ping them and they reply.

It’s only a mercury rectifier, totally safe (compared to the radioactive stuff) but looks really cool.

Guess that switch wasn’t too keen on trying to split the packets evenly.

Yeah probably, I was just using one of those cheap 2x 10G + 4x 2.5G switches that ServeTheHome recently did a video on, so I would not be surprised if that was the bottle neck here.

I could maybe try buying a few more SFP+ transceivers and using my more trustworthy switches, but that seems too expensive for a project like this.

Alright, so testing with iperf3 to a 10G host:

• Single Direction - 7.06 Gbps RX (2.35, 2.35, 1.25, 1.11 Gbps individually), 9.4 Gbps TX (All 2.35 Gbps)
• Bidirectionally - 8 Gbps Total, 1.538 Gbps RX & 6.55 Gbps TX (315/1220, 232/2080, 256/1520, 735/1730 Mbps individually)

4x USB NICs on the laptop, 1x Solarflare SFN5122F NIC on the desktop, there were 2 10G switches in between which may have affected the speeds slightly.

Also I can get 4.6 Gbps total (2.3/2.3) bidirectionally on one interface, so I would have expected ~16 Gbps with 4, so that’s interesting I guess? My desktop can do 18.6 Gbps total (9.55/9.11) to my server so idk.

Edit: I was using 1500 MTU, I don’t feel like testing again with jumbo frames.

I don’t know if I’ll remember, but I’ll be able to try this in a few days, I have the same laptop, 2x 2.5G USB NICs + another 2 already in the mail, and also a 10G network.

If you’re wondering, my intention for ordering them definitely wasn’t for this, but more just for places around the house I can plug into, without having the framework NIC hanging off my laptop.

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

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.

I thought it was a weird peace sign at first.