this post was submitted on 20 Apr 2024
668 points (99.0% liked)
Technology
59589 readers
3376 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I had it briefly up and running and can only say... it's a bear, at least if you are trying to use it as a drop-in replacement with existing hardware. I'm sure I'll go back and sort it out at some point, but it left me just feeling tired and frustrated even when I had it doing most of what I wanted.
If you were thoughtful about hardware from the ground up, maybe it would be more straightforward, but I tried getting it running on just an old workstation with ubuntu installed on it that I use for very basic stuff like syncthing and it was just painful. Mix of Kasa/Wyze/Philips devices that are just what I've somehow collected over time.
It would be nice to see better first-class add-on support. I found myself needing to SSH into a VM to get stuff into it, and even then it was twitchy in all the wrong ways. Would also be nice to see better support for the containerized version, because that's so much easier to distribute and execute compared to a VM. Next time I'll probably just try to do it all with docker and see if it hurts less, since I don't think any addons I was using were critical to begin with.
That said, if you're doing HA, get a dedicated piece of hardware for it. I suspect it vastly simplifies things.
It's not really a "bear", but it IS highly configurable down to the tiniest detail, so requires a certain level of technical expertise. Definitely not for a novice, but that's what Amazon, Apple, and Google try to cover. I will say there are other options out there that are great for offline home automation, but HA is the most competent and complete.
I'd argue it's a bear and I still use it. YAML is just fucking awful and I'm glad they've been hiding it more and more over the years but it's still there. Zwave is still wildly confusing compared to something like a Hubitat which is just plug and play (guess who has to just rebuild his Zwave stuff from scratch). It's also insanely organized where add ons are different than integrations, and are hidden in different menus, as are system functions and just... It's a mess from UX POV. It's also a nightmare to try to interact with the codebase or documentation or even ask questions, much less make a suggestion. As an aside to address the point of the article, I have absolutely zero worry that they will ever forget about power users, because I, and many other power users who have interacted with Paulus on boards before agree he is kind of an asshole who absolutely does not understand why anyone would want to do anything different than how he imagines it - including documentation or UX or whatever. Home Assistant is totally safe for power users.
Now of course I'm not trying to say it's bad, just that it is kind of a bear even for the tech savvy. You can't beat HA for being able to interface with absolutely anything. There's almost always already an integration written. It can do anything, and if you're persistent enough you can kludge together a solution that works in exactly the way you need. You might even be able to hide all the kludge from your spouse. It's also all free, because Paulus and a hundred other devs contribute their time for free and they're amazing for it. Absolutely awesome for power users. But being simple or easy just isn't one of its many, many pros.
First off:
If you can't grasp YAML, you're in trouble in the future. It's been around for decades at this point, and it's a helluva lot more readable than JSON, which is the currently most transmitted format over the wire on the planet.
YAML is also used by all the big configuration languages out there, Infrastructure as code frameworks, and even novice stuff like Square space.
Second: ZWave is a protocol. HA supports that as well. Had nothing to do with HA as a platform, they just support it. You have no idea what you're talking about. Example: I run Zigbee for everything on my HA. I could switch everything to ZWave tomorrow if I wanted.
This is a "you" problem, not the rest of the world.
Maybe for you, but definitely not for everyone. I can use it if I have to, but I find it very annoying to deal with significant whitespace.
YAML might be more readable than JSON, but it's absolutely not easier to work with, either to write from scratch or troubleshoot. And honestly, for my purposes that doesn't even make it easier to read. It's easier to read if I'm showing it to my wife because there are fewer semicolons. As soon as you want to do anything with the information you've read, it's garbage. YAML sucks, and I'll just link to a much better rant than I can ever come up with: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
Second off, if you'd been using Zwave in Home Assistant for many years, you'd know they've changed their integration (no wait! It's an add-on now! No wait, it's also an integration still too!) multiple times, including breaking changes. That's what I'm talking about. Of course I know Zwave is a protocol - it's a protocol that Hubitat supports better. They also support Zigbee better (yes I use both). Admittedly part of that is built in hardware, but also it's a better UI, a consistent UI, and not just... changing how things work so old hardware doesn't work anymore.
I dunno man, we can disagree on HA's choices but maybe make sure you even know what you're talking about before being a dick for no reason. Then again, you opened with being a dick about me being the problem because I "can't grasp YAML" when I said I don't like it so I don't even know why I'm engaging. Just piss off.
I bought a dedicated mini PC for it, and if you just manage it using proxmox it's pretty straightforward (if you already know how to do Linux things and paste the right commands from the tutorial in there).
There's still stuff I need to fix to make it the only smart home controller, right now I have a ton of different stuff (switchbot, meross, Google home and HA).
I installed it in a VM that's running Unraid. It was pretty simple to set up that way. The hardest part was figuring out how to pass through the USB controller to the VM. Side note: if you're building a home server, you should look into getting an extra PCI USB controller so you can dedicate them to different VMs if needed (or leave one for the host to use).
For routing to the open Internet, there's a handy addon in HA to connect to Cloudflare Tunnel. It works great. The only catch is you need a domain name registered with Cloudflare. Of course, not needed if you only want to control it from LAN-connected devices.
If you don’t want to deal with remote access hosting (which can be pretty involved), their cloud service Nabu Casa is $5 and this is exactly the functionality it provides - they don’t host your instance (you still need somewhere to run it locally, like a Pi or one of their devices) but it tunnels your instance out to their managed hosting and you can access it from any Internet connection.
That was the point that hit my limit, now that you mention it -- getting it to show up on a duckdns address on the https public internet. Not being able to make that work after fiddling with all kinds of contradictory guides nor with 2 or 3 completely different reverse proxy tools just left me mad. Especially since a regular ngix reverse proxy manager container works fine on the same computer, but for some reason was just refusing to connect to HA (SSL issues, I think).
Having HA just working locally didn't really make it a replacement for the big tech solutions that already work fairly smoothly. I'm sure I'll go back to get it the way I want one day, but the learning curve on any selfhosting is still pretty rough.
Yeah I had the traefik reverse proxy set up for a while until it updated to 2.x and all my configs broke. At that point I gave up and just paid for the nabu casa URL.
Addons are just docker containers at the end of the day so as long as you know how to spin up a docker container, you're not adding much. And as long as you know how to spin up a docker container I don't think you'd have much issue getting the dockerized version working.