8 ms·
I wrote my own smart home software
- nvy 3y agoI too balked at the absurd complexity in the HomeAssistant stack, and it's kinda kept me off the "smart home" train because I refuse to buy into somebody's walled garden. As a result the sum total of smartness in my home is... A little STM32 Blue Pill that reports whether or not the basement door is locked or not. Yay? Edit: oh and the raspberry pi that measures the moisture in the soil of my beloved Norfolk Island Spruce and tells me over IRC when it needs water.
- deleted 3y ago[deleted]
- acidburnNSA 3y agoI got into HomeAssistant in the early days, maybe around 2015. As such, I've stayed with the simpler installation method just make a hass venv and pip install homeassistant into it. This has mostly worked ok for years, and I've raised eyebrows as they've pushed more people to their linux distro, hoping they wouldn't stop supporting the basic installation method. I did finally have to install one docker thing to keep zwave working after support for the (legitimately bad) python-openzwave lib was deprecated.
- Denvercoder9 3y ago> I too balked at the absurd complexity in the HomeAssistant stack You can ditch their whole OS, management and orchestration/containerization stack, and just run it as a Python application in a virtualenv (they call it "Home Assistant Core"). I recommend it, it's much better than trying to keep up with their (mediocre, imo) distribution. Even if you don't want to manually setup a virtualenv, you can run it as a single container.
- prmoustache 3y agoWhat kept me for the smart home train is the lack of need. I am still trying to grasp what it would improve to my life
- LeafItAlone 3y agoI was like that too, for a long time. But for me, it comes down convenience, rather than need. Some examples: 1. I have a smart lock on the front door. Now when friends/family want to visit and I’m not around, I don’t need to hide a key that they then can lose. They just get a code that I can have expire when they leave. 2. I am constantly either too hot or too cold. Being able to change the thermostat from where I am means I don’t have to interrupt whatever I’m doing and walk across the house. 3. Same with lights. I can climb into bed, tell my phone “goodnight”, and it shuts off all lights and locks the door. Again, nothing that is “necessary”, and sometimes I feel lazy because of it, but it results in fewer interruptions. The one use case I use that I can’t really replicate without smart home, is being able to remotely toggle power. Smart outlets mean I can hard reset an unresponsive server, camera, or other device.
- nvy 3y ago>I am still trying to grasp what it would improve to my life I mean yeah, once the novelty wears off of having Siri turn off your lights to impress your boomer neighbours, or whatever, there seems to be no real "killer app" for home automation. However there are a lot of small things I wouldn't mind having: - The aforementioned "hey your tree is too dry" push notifications on my phone - No need to get out of bed to check the downstairs deadbolt(s) - Automatic and/or manually-controlled activation of garden bed hoses with some kind of zigbee solenoid valve or something
- lostlogin 3y ago> Automatic and/or manually-controlled activation of garden bed hoses with some kind of zigbee solenoid valve or something A basic smart plug does this for me. I hooked one up to a cheap solenoid that opens a valve when powered up. It was very inexpensive and had been very reliable. It’s just on a TP-Link Kasa smart plug. It’s also in HA so that if I forget to turn it off, it turns itself off after 10 mins.
- kevstev 3y agoDo you know which solenoid you used? I am not sure if our definitions of cheap are different, but I looked at this about a month ago and the options I found were fairly pricey, but would hopefully be more robust than the rainbird system I had go bust on me after three years.
- georgehotelling 3y ago> I refuse to buy into somebody's walled garden That's actually why I landed on Home Assistant. It's Open Source so I know that if things ever go bad someone will fork it and I won't have invested deeply in a dead-end ecosystem. Getting started for me felt like the first time I learn a new board game. The rules seem incomprehensible and everything is unfamiliar, but that's the price of trying something new. Eventually the concepts started to click and I saw how things fit together. I will say that telling my spouse to install an app with a web GUI was much easier than it would have been to get her on IRC to control the house.
- cptskippy 3y ago> I too balked at the absurd complexity in the HomeAssistant stack I did for the longest time, trying every alternative but I eventually embraced it. The modern docker container OS image runs perfectly fine on an old Raspberry Pi 2B and the modularized container architecture makes it easy to up/down grade parts of the system as needed. Add-Ons (e.g., Z-Wave, Zigbee, TP-Link, etc) are Docker Containers by default so they're easily maintained and upgraded by the core supervisor. It is a lot of complexity that they have been progressively hiding behind a pleasant UI but it still has some rough edges. The complexity is due to the modular ability to support nearly every smart home feature out there.
- sigmonsays 3y agothe current state of all smart home drives me mad. Why does my thermostat have to reach out to a cloud service to change the temperature? Why does any of it operate on remote cloud API calls when it could operate locally?
- katbyte 3y agoI just moved over to HA and so far nothing including presence detection is cloud dependent (35 zigbee devices dozen or so wifi flashed to esphome) It’s been pretty amazing tbh
- adamzegelin 3y ago> Why does any of it operate on remote cloud API calls when it could operate locally? Vendor lock-in, and gives them the ability in the future to hold your devices hostage by requiring you to pay a subscription fee. Various IoT platforms, eg Tyua (which gets rebranded a lot), sell a complete package that is totally cloud oriented. Configure the product behavior online, click order, purchase 10000 controller chips preflashed with firmware implementing said behavior, integrate with devices, slap logo on it, sell. Also, maybe the developers of these products only know how to write cloud enabled software? (slightly joking)
- ianmcgowan 3y agoApart from the not-at-all-paranoid answer of "money", it's probably just easier for them to program - if you're going to have (honestly, required for 99% of users) integrations with cloud services like alexa, google, homekit, HA etc. where you need to provide an end-point, it's just easier to make your own app talk to the same end-point. Which is money too, I suppose.
- manv1 3y agoBecause adding brains and storage to hardware is expensive. And putting simple things on customer prem means less things can go horribly wrong. And people actually like controlling their hardware from out-of-the-home, which makes doing everything locally even more complicated. When you start trying to present end-users with a graph of whatever metric you want, you run into issues with storage, response time, CPU usage, storage, the web front-end, storage, etc. Then you have issues updating all that. And if you want to do something like, say, comparing and benchmarking against other users you can't. Really, only technical people care about this kind of stuff, and they can go ahead and write their own or use HA.
- nevi-me 3y agoNot to sound negative, it reads like the author quickly dismissed HA without a great reason so they could build their solution. There's a lot of home devices beyond ZigBee, with a large community supporting them. Beyond ZigBee, we will see Matter devices also cropping up over time. I do like the idea of being in control of one's automation software. The risk that I've seen though is when one ends up spending more time on building the software than the automation, which can happen when one writes their own integrations from scratch (i.e. not using Z2MQTY, ESPHome, HA, etc). With that all said, I like HA as the central programmable hub, but have come to dislike the proliferation of ecosystems that require add-ons I'm mostly looking at Sonoff devices that tie you to ewelink and phone home in opaque ways. I'm personally probably going to go with Matter for store-purchased and DIY devices. I'm already nearly done with our first DIY devices at home. A light strip for the kitchen, that has some sensors for useful automation. Not rolling my own solution makes it easier for me to build a few devices for friends later.
- theshrike79 3y agoHA is _very_ good for integrating stuff, mostly due to it being the de facto standard for DIY home automation. Basically if something has any kind of API that can be accessed in any way, someone has already made a HA integration for it. On the other hand, it's absolutely crap at doing complex automations. The Web UI gives me heartburn any time I need to make it do anything else than simple "if temperature is over 40 on this, do this" things. The UI does make complex automations _possible_ for non-programmers. But for me, every time I click on the UI or attempt to "program" using the convoluted YAML syntax I keep thinking "this would've been like 5 lines in an actual language...". Thus: I use Node RED for the more complex stuff paired with an external program I made that connects to the HA Mosquitto server and pokes stuff directly when needed.
- katbyte 3y agoYea I kinda wish you could just write code for it. I’d even accept writing it in python as that’s what ya is written in (as I too don’t like python)
- dingledork69 3y ago
- timzaman 3y ago> The biggest problem with HomeAssistant, however, is its really overengineered setup for running on mini computers like the Raspberry Pi, which was my goal. False, i ran mine on rpi for 2 years now with many sensors. Zero issues and not even close to maxing out the pi. > I have a strong aversion to Python due to its horrendous package management history (we use dozens of languages at work, guess which language is the only one that causes build issues all the time?). It’s a nice language, but for things like home automation, having build/dependencies problems is the absolute last thing I need. Not sound reasoning imo, this is mangable if you know what you're doing. Clearly, HA doesnt have any problems related to this version management.
- acidburnNSA 3y agoAgreed, package management is fine. Just make a home assistant virtual environment and you're done. python -m venv /opt/venvs/hass source /opt/venvs/hass/bin/activate pip install homeassistant boom done.
- oynqr 3y agoGreat, now tell me how to maintain it.
- Semaphor 3y ago> I have a strong aversion to Python Me too, I like nothing about the language. Luckily, almost everything you do in HA besides contributing is not done in Python (by default). But I love C#, so just in case there are others, I wanted to mention that you can write all kinds of automations in C# as well with NetDaemon [0]. Including full intellisense. [0]: https://netdaemon.xyz/ https://netdaemon.xyz/
- tmyllymaki 3y agoThanks for showing me this. As another C# dev I know what I'll be adding into my HA stack.. :)
- Semaphor 3y agoIt’s also a great community on discord, very helpful even for beginner questions.
- samldev 3y agoShameless plug, I wrote a Golang library for writing Home Assistant automations called gome-assistant [0]. The API looks sorta similar to this C# one, I only briefly glanced at netdaemon though. [0]: https://github.com/saml-dev/gome-assistant https://github.com/saml-dev/gome-assistant
- Semaphor 3y agoNot a GO-user, but something you might think about stealing from NetDaemon: It has typed entities, so instead of ".EntityIds("binary_sensor.front_door")" you can do something like ".Entities.Sensors.front_door". It obviously requires a script to run after you add/remove any in HA, but IMO it really improves the DX.
- vincnetas 3y agoIf looking for lightweight solution with zigbee (usb dongle) one can also take a look at Zigbee2MQTT [0]. This library is used by HomeAssistant under the hood, but it can be used independently as a standalone app and let one interact with zigbee devices using MQTT json messages. And it supports a lot of devices : "Currently 2971 devices are supported from 379 different vendors" [0] https://www.zigbee2mqtt.io https://www.zigbee2mqtt.io
- dementik 3y agoI think HA is using ZHA under the hood for Zigbee communications.
- babas 3y agoIt can use both. ZHA is included in base HA. Z2M is an optional addon. Z2M has better support for obscure devices in my experience. I Also strongly prefer the management interface in z2m.
- vincnetas 3y agoMy mistake, zigbee2mqtt is one off third party options to add zigbee to HA. But still, quite nice project.
- dementik 3y agoYep, Z2M seems to be very reliable way to handle zigbee devices. Also it feels little more vendor-lock free (considering HA as vendor here).
- deleted 3y ago[deleted]
- ur-whale 3y ago> I have a strong aversion to Python I have had a great experience with HA (unlike with OpenHAB which is a Java-based monstrosity with a data schema that is near impossible to figure out). It's unfortunate that he went and rewrote an entire home management stack just because he dislikes Python. Even worse, the justification for disliking Python, namely: > It’s a nice language, but for things like home automation, having build/dependencies problems is the absolute last thing I need. is absolutely not a problem if you run HA on a tiny dedicated box, because all of that stuff is completely handled (and hidden) by the HA update system. > The biggest problem with HomeAssistant, however, is its really over-engineered setup for running on mini computers like the Raspberry Pi, which was my goal. It may feel over-engineered if you look under HA's skirts (the fleet of docker containers thing), but turns out you almost never need to go deep into HA to get it to do things, and when you actually do, HA is actually pretty open and easy to work with. (just ssh to port 22222 if you really need access to the bare metal system). I would agree that the HA setup is a bit unusual for someone used to just ssh into a linux server: I had the same initial reaction. But turns out it's actually never much of a problem. It's just different. Also, it may look heavy, but it runs absolutely fine on a small raspi-like computer. > Is the best solution we can come up with a bunch of Docker containers running on a custom Linux distro? Why not? It may "feel" big and complicated, but in practice: - it's very well packaged - it's very well maintained - it has support for a *ton* of home automation devices - it runs out of the box on a tiny and cheap SBC (a raspi) without overloading it All you have to do is dedicate a raspi to the problem and be done with it, not really a big problem. And if you really want to run it on a Linux server that is used for other things, and the HA architecture irks you the wrong way: just wrap HA in a native qemu VM and run it on your server along your other stuff.
- deepspace 3y agoThe author's attitude reminds me of one of the best software articles ever, "Cash Cow in the Tar Pit" (https://www.computer.org/csdl/magazine/so/1996/03/s3041/13rRUxly9bK https://www.computer.org/csdl/magazine/so/1996/03/s3041/13rR...). The reason a "legacy" system seems so clunky and over-engineered and hard to modify and has so much corner case handling is: real-world experience and bug-fixes. When you throw that old cow in the tar pit and start developing your shiny new application, you throw all those years of hard-earned experience away with it. By the time your application works as well as the old one, it will be just as ugly. FWIW, I have been running HA in a qemu VM on a NUC for years, and it is one of the most stable pieces of software I use. It supports every device I can throw at it, and the automations, while clunky, are easy to manage, as long as you keep KISS in mind.
- harry8 3y agoesp8266 and esp32 boards from ali plus various parts. Flashed with tasmota or (for the glow electricity meter reader esphome). Temp & humidity sensors, somfy blind controllers, ws2812 strips, relay to infra-red to control hifi receivers. Athom plugs pre-flashed with tasmota to measure power point usage and switch on and off. Athom bulbs pre-flashed with tasmota. Homeassistant works great. Toss in wireguard for remote access with smartphones. It's good fun. It's cheap. It's cloudless. It's better than anything you can buy. Go the DIY! You do tinker a bit, if you hate that aspect of DIY then maybe pass on smarthome stuff. Parts probably paid for themselves in reduced electricity consumption. Once you measure something, behaviour changes etc. I run Homeassitant on a 12 y.o. laptop that also runs mosquitto, has some usb disks plugged into it, runs samba, pi-hole, owntone, wireguard, timecapsule etc. Home assistatant works pretty well and easily, imho. How are you doing it?
- aulin 3y agoAt some point you want your home automation system to do things for you. If you're maintaining your own fragile custom infrastructure you're spending more time on it than it saves you by automating stuff. Sure it's fun and it's a great learning experience, but don't try to make it look like a better solution than a popular, proven, tested and maintained one like Home Assistant.
- hnlmorg 3y agoI built my own smart home set up before Alexa et al came along and later switched to Alexa because my wife and, later kids, took priority. My experiences with commercial smart home solutions is that they require just as much babysitting as anything you build yourself. The only real benefit of commercial solutions is that my wife isn’t afraid to add plugs et al to the smart home infrastructure whereas before it would be entirely down to me. But the cost I pay for that convenience is reduced privacy and potentially insecure hardware connected via WiFi. Honestly, if I was building something out again, I would totally optimise the set up for privacy and security rather than convenience of having a spouse connect new devices.
- z3t4 3y agoBuilding something specialized for only yourself might be faster then bending existing solutions to fit your requirements. And if you do something more advanced it will likely also be cheaper to build it yourself then buying the solution. And the knowledge you gain will be invaluable.
- theshrike79 3y agoObligatory XKCD: https://xkcd.com/1319/ https://xkcd.com/1319/ Also: in some cases it really is faster just to make your own rather than learn the Home Assistant Way Of Doing Things.
- expertentipp 3y agoThere is always that one cronjob to bugfix, web server to restart, port being brute forced by some bots...
- iamflimflam1 3y agoAnyone embarking on a home automation journey. Think very carefully how the non-technical people in your life will cope if you aren’t around - what do they do when things don’t work?
- explorer83 3y agoIn addition to when they don't work. What about when the company stops supporting them or just goes under? The industry never seemed to build long term trust whenever I looked into it.
- expertentipp 3y agoMy acquaintances bought a house from debt closure with a monitoring system. Now they have a one room with idle servers. I'm afraid to visit because they'll ask to "install windows" on every one.
- mrweasel 3y agoPeople probably forget that IoT devices can be pretty expensive to yank out again. I would want to move into a home full of IoT devices configured by someone else, how do you even ensure that everything is reset and disconnected correctly. There was an episode of the Coder Radion podcast a few years back, one of the hosts had moved into an apartment with a few smart home features, it took him forever to reset and reconfigured. He described it as "living in a haunted house".
- scosman 3y agoAgreed. Switches for everything. Should work like you expect. Any automation/control should be optional invisible benefits.
- lelanthran 3y agoCoincidentally, I spent this past weekend looking into this. This space is ripe for a well-funded new entrant to step in, create a decent protocol for home automation and make a killing. The options in this space are awful, with no clear indication of security, competing "standards" that don't cover even the basics of an appliance-like device, and cloud-lockin for almost everything! Nothing is aimed at the average homeowner (No - writing in Python or Lua is not how people want to automate their home). Lets talk about the media-level protocols: WiFi in homes is ubiquitious and cheap, things like Zigbee or LoRa raises the cost and the effort for HA, local RF isn't widely supported by devices (with good reason). How does a homeowner know what to go with? Let's talk about bootstrapping a new device on the HA network: device discovery! Some devices require an internet connection and the homeowner has to have an account on the cloud (Adafruit IO, various proprietary vendors). Some use a fixed mDNS name (Shelly), some require to download the vendors app (used to set network config, credentials, etc), most simply don't do it at all. I even found one or two that require the owner to browse to a particular local IP, because the device starts off in AP mode. Okay, lets say you jumped through the hoops (registered an account on a cloud service, gave the device internet access, used its AP to set it up, or it set itself up doing mDNS query for _mqtt._tcp.local, or whatever). Next problem: authentication of the device on the network. Some devices just don't support it, some support it using AES with pre-shared keys, some support it with basic HTTP auth over TLS, some use mqtt with TLS, some offer mqtt, but in plaintext only, with encryption being over HTTPS (reverses the pub/sub model horrifically), many support x509 certs loaded onto the device (the worst option for an appliance!), some (using CoIoT) have support for DTLS (But need a valid x509 cert) ... Problems aren't over yet. So, you go with something ... and then find out that your controller is not compatible with one device. Maybe you need a Zigbee bridge because everything else is WiFi. Maybe that device requires x509 cert over WiFi, while everything else is using auth credentials. Maybe it's hardwired to use vendor's cloud and the rest of your network is using Home Assistant. Maybe it's using ESPHome and everything else is using CoIoT. That's fine, you think, I'll just use Home Assistant, which has integrations for everything on the planet, to "bridge" the different protocols. But now you're stuck with Home Assistant as a controller, which has limited automation facilities. Honestly, what homeowners want is to buy a device and plug it in, and have a nice interface for devices which allow the homeowner to specify what happens on any event. That's it. No messing about with Python, Containers, Lua, mDNS sniffers, accounts on public internet clouds, renewing x509 certificates, etc. Plug it in, use username+password to access the Home Automation network, that's it. From a technical PoV, I can see a mechanism to get it done this way.
- antigravity42 3y agoThe amount of skeptical people in this thread is astonishing, it is natural to questions pile of complexity even if it is well established. In an unlikely event it goes south, author will have much easier time debugging his simple setup then waiting for reply from a home assistant forum (even though they are lovely people and nothing against HA).
- gorgoiler 3y agoIf I put smart stuff into my home — color bulbs, switches, sensors — then I’d probably be changing about 40 bulbs and 40 switches. Throw in the HVAC and some other things and we can round it up to 64 different inputs and outputs. That’s equivalent to half a keyboard and an 8x8 pixel screen. I couldn’t agree more with this article.
- rcarmo 3y agoInteresting piece. My home automation solution is based on Homebridge, zigbee2mqtt and just enough Node-RED for charting and doing a bit of glue (virtual devices, custom integrations, etc.) and I’m very happy with it, but I was looking at Mako server the other day. I found it refreshing, but the licensing is just weird — parts of it mention that the web content hosted by the server is also covered by it, and I’m not sure if that is a tenable approach.
- sp0ck 3y agoAll smart home is great to you and you family until author maintain it. What happend when you have to leave for a month or for some reason unable to maintaint it ? My experience is that beyond some stack complexity level simple power outage render open source solutions to the point my intervention was required. Additionally this software is full of bugs due to how it is developed. I had situation when I was on a business trip and one of my hall light went strobe mode :) Turns out there was a bug and race condition was triggered because someone activate PIR sensor the same micosecond previous action was turning light off (NodeRed) Wife went crazy, called me to turn this madness off :) Home is smart when users can handle it without you in any daily scenarios. Otherwise it is just our fun/hobby not real solid solution :)
- jaclaz 3y agoThank you for sharing your experience, without any personal experience I always thought that the issue with these is essentially that of "maintenance", in a ideal/perfect setup, there should be something like a by-pass switch to allow manual operation of the lights/devices, but I don't think this is possible at all without modifying heavily the electric circuitry of the house.
- sp0ck 3y agoManual fallback is must have. Unfortunatelly not all solutions are design that way. It is my No. 1 option I check.
- mrweasel 3y agoThat's really what keeps me off smart homes in general, I don't want to fiddle with it. I do see some of the value, but mostly I don't see it as proving enough benefits to justify that added complexity. My dad likes to dabble with smart home devices, and some of it is really good, and some is just junk. For three months he could adjust heating, because a server in Norway was down, and apparently not monitored. I recently bought a new house, and while a lot of modernization is required, I'll still be excluding all IoT and smart home devices/features, and I've given up on wireless for most things as well, there will be a plethora of ethernet jacks.
- 01100011 3y agoI ran a HA system for a couple years at my last place. It was great when it worked, but I found it to be fragile, overly complicated, and not well engineered. I'm biased I guess, as I have mostly worked on embedded software and devices that need to be reliable. It's great if you like 'shake and bake' style open source projects that barely work and have a lot of time to tinker with them. I prefer my home automation to work 99.9% of the time and not require large, periodic time investments. HA, out of the box, also seems to burn up solid state storage due to the absurd amount of logging. HA looks sexy though, and I think that entices folks. It's nice to have a star-trek style dashboard running on a tablet or whatever. That's not really appealing to me though. I like my automation to have beautiful software, be well tested and reliable, and disappear into the background of my life. Being a SW guy at my day job, I really don't want to play SW engineer on the nights and weekends.
- aulin 3y agoSo what's this beautiful, tested and reliable alternative to Home Assistant? did you ever find it? Guess baking your own like OP did is out of the way as per your last sentence.
- theshrike79 3y agoIf Apple Home, Google Home and Alexa aren't enough for you (or you want a fully self-hosted option) you don't really have many options. Home Assistant is the big one, biggest community, most integrations, you can pay for their cloud stuff to get easy integrations to the big corps above. They also have a dedicated device they sell you can use to run HA. Domoticz is a bit of an odd bird, I never figured out what was their value propositon OpenHAB is the one I'd pick if I had to install a system for someone else than myself. It's not exactly easy to configure (the object/entity structure is a bit weird IMO), but it has a pretty decent amount of integrations and it's rock solid German engineering made with boring old Java. If you want control, my suggestion is to use HA only for the integrations and do all of the brains somewhere else. Either a self-made program that pokes HA using its API or directly via MQTT or Node RED.
- 3y ago
- rkwasny 3y agoMy take is to use https://www.zigbee2mqtt.io https://www.zigbee2mqtt.io - having a queue makes it very simple to add/test automations.
- tga 3y agoMy "HA" setup is really driven by Zigbee2MQTT -- most of my lights, devices (light switches, washer, dryer) and sensors (temperature, motion, doors/windows, water leaks) are all random Zigbee devices that Zigbee2MQTT does a wonderful job talking to, without any need for vendor software or services. https://www.zigbee2mqtt.io/ https://www.zigbee2mqtt.io/ I happen to use Node-RED for automation -- this is the easiest part to replace, it could just as well be Mako, pyscript, AppDaemon, NetDaemon, or plain Python scripts talking to the MQTT server. What I can't easily replace from HA is the nice UI, both over the web and as an app (same thing really). I guess Mako makes it possible to hack together a web interface, but it's a lot of work for a poor result when compared to what you get with HA (or OpenHab) out of the box. I would love to find a simpler, MQTT driven "HMI" app for both web and mobile, completely disconnected from the logic behind.
- herbst 3y agoI have a small ruby app running on my home server that keeps the zigbee2mqtt stream open, its fairly simple but provides the main functionality of the smarts in my home. If I get a new device I just hack my own bridge and link it in. My point is a smart home doesn't have to be complex and can be fun to do yourself.
- ep1cman 3y agozigbee2mqtt has its own webUI with a dashboard that seems fairly competent at controlling the devices. https://www.zigbee2mqtt.io/guide/configuration/frontend.html https://www.zigbee2mqtt.io/guide/configuration/frontend.html
- tga 3y agoThe Zigbee2MQTT web UI might be useful for debugging, but a mixed list is hardly a good way of interacting with home devices.
- lynx23 3y agoThe "framework effect" seems to be a thing these days, not only with SPAs using the newest JS framework. When I stumbled across an HN article describing a CLI app for the OpenAI API, I thought that is just what I was waiting for. Unfortunately, when I tried it, it didn't work for me. After a debugging session, I found a bug in the openai python package which led to my key not being used if I have ~/.netrc exists. Pretty much a demonstration of the "framework effect". The simplest things, read CLI tools, become buggy in subtle ways because you inherit every bug deep down in the dependency chain. I ended up implementing my own OpenAI API CLI client in just a few lines of shell. Much easier to review, and almost impossible to have subtle hidden bugs. https://github.com/mlang/openai-kiss https://github.com/mlang/openai-kiss
- lloydatkinson 3y agoIt's UI is very much "programmer art".
- xmdx 3y agoI feel like the initial learning of getting Home Assistant up and running is worth it over creating your own software. Especially in the long run. That and the other recommended way of setup that wasn't mentioned is to install the OS without messing with any containers. Pretty straight forward. Any problem you have there's probably a solution out there because the community is so large and that is worth it's weight in gold imo. It used to be quite fragile but these days it's gotten a lot better. Still a lot of learning to do, someone with no experience in yaml or understanding under lying tech will struggle at first. They are pushing for UI setup for most things now so it's only a matter of time before it's far more accessible.
- varjag 3y agoHow long is the long run though? I've spent a few weeks setting up HA in 2017 only to watch it degrade by a series of busywork redesigns with each consequent update. Rules, app interaction, UI all were broken at some point: often in multiple ways. Devices that worked previously fell offline, and some of the drivers not popular enough to get a keep up rewrite simply disappeared.
- silversmith 3y agoMy philosophy with HA is not to touch it too much. I update only when there is some feature I absolutely need to have. And even when there is a new feature, give it a month or two to mature before using. I run a specific docker tag with auto-updates disabled. The instance is not internet accessible, so less care needed for security patches. When there is an exciting new feature, I apply that excitement to the busywork necessary for HA updates, and power through. Furthermore, I use the built-in UI only for administration purposes. Run a custom react app that talks to HA via websocket/rest APIs. Those are pretty stable in my experience. Same with YAML configured automations. Sounds like a lot of work, but I feel that it's offset by someone else writing the integrations with 3rd party services. When I want to control my new robot vacuum cleaner from my custom dashboard, all I have to provide is the UI. Someone else has figured out how to talk with the vac APIs, how to authenticate requests, and what to do to avoid getting rate-limited by the 3rd party service. I have to deal with only the HA quirks, not every 3rd party service quirk.
- icoder 3y agoMy base stack is comparable. I have all sorts of Zigbee devices on an RPI + RaspBee, and Shelly devices behind my wall switches. However, I use Node-RED on top of that. Many things are available as plugin (MQTT, Deconz, daylight, database, web UI, etc) It contains some custom script-nodes, to achieve a 'state' in between inputs and outputs. Now I can just add and change stuff by clicking around in Node-RED. To me it's a nice combo of 'off the shelf' and maintaining full flexibility.
- _dain_ 3y agoThis is the first "smart home" thing that actually seems interesting to me. It's still kinda nuts how much arcane bureaucracy is needed simply to make two computers in the same room talk to each other, and nobody else. Why can't I just control the brightness of my living room lights as easily as my laptop backlight, without the packets taking a detour through Langley?
- bborud 3y agoI can understand why people do this. After having tried out various offerings written in Python, PHP, Node and whatnot I'm tired of things that almost work. That is, they work well enough to convince me to try them, but not well enough for making me want to continue running them.
- michaelmior 3y ago> The biggest problem with HomeAssistant, however, is its really overengineered setup for running on mini computers like the Raspberry Pi, which was my goal. Some might call it overengineered, but it works great. Flash an SD card with Home Assistant, pop it in and you'll be ready to go with minimal configuration. I've had HA running on an RPi4 for years with very few issues.
- omneity 3y agoJust like I try to avoid self-hosting monitoring and devops stuff, I wouldn’t feel comfortable relying on something I have to maintain for home automation. Unless you don’t care if one day your self written home automation system stops working, and if you don’t happen to be in the mood then it will remain broken for months/forever. Mako looks like a nifty piece of tech on the other hand. I wish there was some sort of similar application server for JS (deno comes close but Mako looks much more complete)
- pmlnr 3y agoI tried Home Assistant multiple times, always went back to Domoticz. It allows simple, but quite powerful scripting though actual lua instead of overcomplicated, weird YAML files, eats significantly less resources, and is rock solid. Some tasks HA knows is rather complicated to execute in Domoticz, but definitely doable. There is mosquitto for MQTT and Zigbee2MQTT on the same node, the whole consumption is < 300MB.
- Izkata 3y agoHeh, skimming over the comments it looks like no one has the same setup I settled on: Home Assistant as just a simple API. Home Assistant was pretty simple to install and connect to devices (I'm currently all Z-Wave), but I didn't really care for its built-in rules. But it provides a REST API to interact with everything connected to it, instead of having to fiddle with configuration files. So I have one system that makes sure the remote Home Assistant process is running, that provides a simplified API for everything else (mapping simple labels to the Home Assistant Z-Wave identifiers and handling the REST request for me), and a second one for actually controlling it with whatever rules I came up with. I've found it to be pretty stable overall.
- shannongreen 3y agoI've always been fascinated by the dissonance between what some people insist they need from an off the shelf system (bulletproof with a dedicated security team because Security is Hard, rock solid reliability because I depend on it 24/7) and what they will accept in a DIY solution (completely unsecured un-audited software with no tests and something broken every other day).
- ay 3y agoI started with a similar path a few years ago - IKEA smart home gear. The controller went away fairly quickly. I stayed for a long time on raspberry pi + Zigbee stick from DeConz + Apple home integration using homebridge.io. Deconz felt a bit bloated/buggy, so I switched to using a cheap USB stick from aliexpress, and using zigbee2mqtt, which turned out to be a pretty good combination. Unfortunately Apple decided (while I was on a business trip) that Apple TV 3 was no longer good enough as a home hub, so all of my soft switches stopped working... As a result in a couple of days I wrote a quick MVP replacement in Rust, which has been working very nice for me, and the "user" (significant other) feedback was that it is now much more reliable and responsive. Putting it here in case anyone finds it useful. https://github.com/ayourtch/homegui https://github.com/ayourtch/homegui
- rootusrootus 3y agoI've thought about it. My automation needs are straightforward, and occasionally Home Assistant ships an update that makes me work to get things back up and running. A few weeks ago it caused my zigbee configuration to completely lose all devices any time HA restarted. That was aggravating, having to go around to each one and relearn them, only to see them forgotten again. Ended up rolling back, and then pinned the version at the previous release. No more problems, and I probably won't enable updates again. I need it to just work.
- ErneX 3y agoI chose to do everything in node-red + mqtt and it’s been fun.
- magic_hamster 3y agoEvery time I think of home automation I almost go for it, but upon second thought I realize this means adding an entire tech stack that I will have to maintain to what's basically a couple of switches. Having my windows, lights or thermostat break on updates is something I don't need.
- jackdh 3y agoTo provide another point of view, I've had a simple light & fan connected to Google Home for the last couple of years. Since connecting it to Google from their own app's I've not needed to go back / update them since.
- andiareso 3y agoHome assistant is too involved to set up… Proceeds to code a basic display that will need endless support. Home assistant can run on a pi and is actually decently lightweight. Just because behind the scenes it uses containers doesn’t make it complex and difficult to maintain. My home assistant hasn’t needed and babysitting and is my least involved support project. Upgrades are stable and one-click and you can use as little or as much of its functionality as you want without the sacrifice for performance.
- noidesto 3y agoMy thoughts exactly.
- CommanderData 3y agoCan echo this too, I was afraid my smart home would become a fulltime job. Home assistant has been one of the least problematic thing to support when doing upgrades. It's a great project.
- cptskippy 3y ago> Home assistant can run on a pi and is actually decently lightweight. I've been running Home Assistant on a Raspberry Pi 2B for years with no complaints. It takes about 7 minutes to compile the firmware for a single ESPHome device which is a long time but it's hands off so it has no impact on me.
- PaulHoule 3y agoI did similar stuff with Python and asyncio.
- jollyllama 3y agoIt's too bad that the author is getting dragged in these replies. They decided to avoid a dependency on docker among other things, and more power to them. The author could create a system that's stable for 20 years, with no updates. Docker will almost certainly force you to update, it probably even has to reach external servers and will brick past a certain point if you don't update it. I don't know for sure, but I wouldn't be suprised. The author will almost certainly have less of their own maintenance to do since they are not beholdent to updates from dependencies than if they had gone with the more "well-supported" solution. As long as they document it properly, it could work well for decades. Probably for longer than home assistant will be supported.
- 0xdeadbeefbabe 3y agoMaybe I missed it, but what is so great about a smart home? Seems like a burglar alarm would be more interesting.
- hcfman 3y agoNice that you should say that :) I also wrote a home automation system. Well... actually, it's a kinda burglar alarm except it's focus is alerting way ahead of actually getting inside. I added home automation bits (minimal) just so one can elicit a real world response, but I do use it for minimal home automation (Lights, heating control and letting the chickens in and out). I have yet to announce on on hacker news and so because I still have to write a bunch of documentation. It uses the latest state of the art computer vision triggering, currently yolov7 and I'm about to release support for yolov6. It's multimodel, so you can double check it's result with more than one model, even for specific parts of an image. The architecture diagam and installation instructions are here: https://github.com/hcfman/sbts-install https://github.com/hcfman/sbts-install I actually, started writing this in 2008 and most of the current state in terms of the user interface were finished in 2012 but I only released it into open source last year really. In 2019 I add support for yolov3 and have been adding models even since. It's written in Java and installs in just two commands on nvidia jetsons at the moment (Not in containers). The inference framework is a simple websocket based wrapper around other models so it's easy to add new models and that's written in python. Well I finish the new release to introduce yolov6 and support for the seeed studios platforms I'll make an announcement on hacker news, note I still have a lot of work to do on documentation.
- hcfman 3y agoOh, one or two more details pertainent to some of the comments above. It has a builtin GUI around a certificate manager, so you can generate, import and use TLS inside your intranet between devices. It doesn't use a domain specific language, rather just a simple web gui around a state machine. IMHO you can't pretty much do what you need with a state machine and anything that can't be done like this can be handled easily via the generic rest interface and if you need notifications it supports web socket based notifying of events. This make's it easy to add new rules on the fly from your phone if you want. It make's it easy to add new pages of buttons to control the state from your phone and generates nice video alerts with multi-camera views of the trigger event. And it's totally undiscovered. You can be the first early adopters! :)
- philwelch 3y agoI’m kind of surprised that all of the top comments on this are some variation of, “it would be easier to just use Home Assistant”. I would understand that reaction on a site called “Sensible Smart Home Consumer News”, but hackers build software and you’d expect Hacker News to have some respect for that. I’m not saying writing your own software is always the most cost and time effective solution, and I would push back against it in a work setting if it was inappropriate, but from a hacker ethos perspective, writing your own smart home software for your own house is cool and deserving of respect rather than denigration.
- hcfman 3y agoVery nice reply, totally true.
- daill 3y agoI‘m wondering that no one mentions fhem. I’m completely satisfied with running it joining self-built, Homematic IP, HUE, Max!, Shellie’s and SaaS stuff with Echo integration. But besides that good job writing something in this size on your own! Hopefully you‘re able to maintain it!
- Havoc 3y agoConsidered building my own too but then sanity prevailed and realized that the development effort and device support that has been put into HA/ESPHome is not something worth duplicating. Still very tempted to write my own presence detection code though since that’s a little fuzzy and case specific. That would still use HA for the heavy lifting on sensor inputs etc
- asveikau 3y agoRegarding home assistant: > Is the best solution we can come up with a bunch of Docker containers running on a custom Linux distro? It's really not that bad when you consider that HassOS has an updater. You don't need to reason about any sort of docker config if you don't want to. A lot of users have no idea what docker is and still get by. It's pretty appliance-like. Additionally, I run hassos in a VM, and that takes away even more of the 'managing a linux distro' aspect. A few years in I did want the control to manage a docker container myself for frigate. I keep that alongside the hassos VM and no issues. So you can even mix and match if you like.
- blacklion 3y agoProblem is not with smart home software, but hardware. Ok, we now have "smart" lightbulbs. And even thermostats. Great stuff! I think, it is possible to have "smart" curtains. But I have simple example: now I'm living in country, when price for electricity changes every hour. I can extract this price programmatically without problems. Suppose, I want to wash my clothes when electricity is the cheapest, but no longer than 24 hours. No problem, algorithm is simple: calculate average price over, say, week (possible), look at state of washing machine, and if machine is prepared and ready (power-on, standby, program selected, door closed) and price is small enough (or there is a 23 hours passed from washing machine readiness), give machine command to start. I can imagine (and implement) Very smart algorithm when to start washing. But it needs washing machine, which can be polled for status and started remotely (but prepared locally, as software doesn't know did you want to wash color, white or black clothes, for example). Is here any such machine on the market? Nope... Same with microwaves, dishwashers, stoves, anything.
- blacklion 3y agoTBH, here are washing machines with WiFi. With proprietary, mobile-only, cloud-only applications. Maybe, it is possible to hack these protocols. Maybe. Maybe, cloud will be up and running in 10 years (typical age of washing machine in my life, after which it requires replacement due to failure of one of the main aggregates). Maybe. And, maybe, you country will not block this cloud and cloud will not block you country. Maybe. So much for smart home.