I’ve used Brultech in a house before. It’s not very user friendly to setup having to download some different firmware flashing tools and configure everything in a brittle web UI that only allows one browser tab at once. But it does have Ethernet, comes with a variety of different CT clamps. The donut style CT clamps are very compact making it easy to fit them into a electrical box. Don’t use the built-in one, use the HACS integration. The different sizes make me think that the Brultech is probably more accurate than the Emporia with only a single size.

I ended up going with Emporia Vue2 for my own house given the complexity and my house layout not really permitting the Brultech’s install.

Containers can provide SBoMs too and in comparison to HA OS, which is what the comment was referring to, container and core give you better control over the application allowing for more security mechanisms. Comparing container vs core for security is interesting cause container gives you some security features for free like seccomp, cap drops, namespacing, etc. which you don’t get for free with core.

I find the claim that core is more secure than a container because it has an SBoM as dubious, but maybe you’re talking generally about containers vs distro package managers, which is a different point, but SBoM isn’t the only thing that makes some secure/stable.

Nope. Docker and Home Assistant OS will be the only supported installation strategies

Its not difficult for technical people like you or me, but my friend who just wants to watch their favorite show on my Plex on their TV won’t know how to traffic engineer the traffic over a Tailscale network to my network. My mom won’t be installing Tailscale on her laptop and phone.

With Plex, you’re getting the easy ability to grant access to users. You get a single pane that can search across multiple Plex instances, and NAT traversal/port forwarding. Jellyfin makes you figure that out yourself.

There’s no guarantee bugs get fixed in a newer version, but there’s a higher chance of a software feature working if it’s been out for awhile with a few patch releases than it is for a brand new feature to work day one on a YYYY.MM.0 release. Home Assistant generally holds new features for those YYYY.MM.0, but patches get backported.

update 2.1.3 once update 2.1.4 becomes available

I wouldn’t use that policy because what if 2.1.4 includes a fix for an issue in 2.1.3?

My update policy is wait until a month comes put, then update to the newest previous month’s version. Patches for bugs go into mainline and are backported so this minimizes bugs in the new features.

Oh that would be nice. I would use that to just go into the database and fix all my broken music metadata which I can’t see to fix any other way.

https://www.recompile.se/mandos

You’re right. Unfortunately, open-source has proven time and time again to be unsustainable and burn maintainers out

That’s a good reason for people to take the money they would have spent buying a proprietary solution and instead donate that money to an open source project. For me it’s not always about the cost, but what I get out of it. I’d rather the money go to the community and better it.

Its only everything from other instances and communities that the current instance subscribes to. It doesn’t subscribe to the full pipe of everything.

What’s likely happening is people in aggregate generally subscribe to the most popular communities and those communities have the most upvoted posts.