Hi,
I am about to choose a new Domotic box and was undecided about Home Assistant and Homey. I know Homey has more modules included apart from Zwave.
But what are the usability advantages of the extra cost of Homey against a RasberryPI HA?
Hi,
I am about to choose a new Domotic box and was undecided about Home Assistant and Homey. I know Homey has more modules included apart from Zwave.
But what are the usability advantages of the extra cost of Homey against a RasberryPI HA?
Personal preference comes into play here, but from my own experience:
Advantages of Homey:
Disadvantages of Homey:
Advantages of HA:
Disadvantages of HA:
(Iâm sure I will think of more points to add to each list )
I wont disagree with roberts opinions⌠however.
I donât feel that they perhaps give proper weight to each of the issues, and some of his issues will certainly not be the average users. ie Do you care what language homey is written it?
A better way perhaps would be a direct comparison ie.
Category | Winner | Details |
---|---|---|
Price | HA | |
Hardware | Homey |
MoreHomey wins as it offers an integrated solution which would be very difficult to replicate on a RPi. |
Setup | Homey |
MoreHands down |
Licence | HA | etc. |
However that is not the question you asked, you asked what are the usability advantages vs a RasberryPi (HA).
There are four items that really separate Homey from a HA solution and they are big ones :
Integrated Hardware
Home Automation via Flows
Ease of setup
Ease of use
In return for the above four you will sacrifice fine grain customisation and cheap hardware.
Given that a fair amount of people seem to expect that âWith over 50,000 devices supportedâ means that those are supported out of the box, I donât necessarily see having separate apps for device support is that much of an advantage.
Also, the fact that apps are âcheckedâ by Athom doesnât mean that they will actually work (as a few devs, including myself, have found out). The process of getting integrations merged into HA is much more elaborate IMO, with automated testing, code reviews, and the entire process being public on Github.
In my experience going to the App Store - installing an app the. Then clicking on an icon to add said device Is a lot more useable and an advantage over HA where (a lot of the time) you need to hunt down the documentation, then open up the config and write YAML in order to add it.
I believe that the App Store approach is more useable âŚ
Maybe you disagree, perhaps an example on how I would go about adding my 20 odd xiaomi devices to HA will prove me wrong?
But seriously, have a look at what is required to add my heater - vs installing an app and entering my username/password.
I agree, the device-adding part of Homey is typically a lot easier than HA (unless the device can be auto-discovered, in which case itâs âthereâ in HA without ever having to have added it at all), provided that you can find the right app (with several âIKEAâ, âHueâ and âXiaomiâ apps, that can be confusing).
Perhaps on HA it will work longer than 30 minutes, though
As for adding Xiaomi devices, I use deCONZ for Zigbee on HA. Adding devices is easy enough (web interface), not limited to just Xiaomi devices (I have Xiaomi, IKEA, INNR and Zigbee2Mqtt devices), and they just appear on HA with more supported capabilities than on Homey.
I have both running, but never really got the hang of HA to be honest. It just took me way too long to search through all the documentation to get the Deconz-stick running properly and connecting devices. Never got to the point to actually learning YAML properly enough to understand how to use the events of Xiaomi-buttons to trigger stuff. Donât get me wrong: itâs not even that hard. But Homeyâs flows are just so much easier and more intuitive.
My advice
If you donât mind a bit of coding and a bit of research, go for HA as it offers much better support for devices and is a lot cheaper. It will gave you a lot more possibilities for custom automation as well. If you prefer out-of-the-box support with easy automation and donât mind to select devices based on support: go for Homey as it supports a lot of common devices anyway.
TL;DR
If the supported devices and you donât need overly complex flows or logging: go for Homey. If you need granular custom automations combined with almost limitless support: go for Home Assistant.
To be honest for HA you need more then âa bit of codingâ.
I have tried it multiple times to get all my devices working but after a while I just gave up.
This could say someyhing about me but I have experience in YAML from my salstack experience so thatâs not it.
The documention for HA isnât always complete and you really need it to be if it doesnât work ouf ot the box.
However, the documentation is better for HA then homey for sure.
I have had my homey(pro) for only 2 months now but I had my first flow created within 10 minutes(sun down > lights on).
Would love to see Athom giving the homey a more open nature for better community support.
It looks the disavantages of homey are the same of zipato which i used for 5 years and want now to ditchâŚ
Best to spend a little time with HA then, and if you dont enjoy that, A lot of places offer a 14 days money back trial of homey.
Good Luck!
Disclaimer: I havenât actually tried HA practically.
I think it basically boils down to if you want a kind of finished product then Homey is great. You donât need any programming, everything is configured using a GUI and is very simple to do. The automation is very easy to get into and at the same time very powerful (maybe not coding powerful but still).
If you like to use code and have the time to hunt for documentation, spend the time learning and code your solutions then HA is probably a better choice. Cheaper ofcourse.
Some more subjective points:
In my personal experience, if thereâs too much work every time I want to make some automation then Iâll probably stop doing it because life gets in the way. Thatâs a big reason for me to Homey being preferable to the open source solutions that exist.
You can go deeper though with Homey if you want to, like integrate Homey to NodeRED or even HA or openHAB through MQTT but yeah, then you kinda use both solutions.
Another point is that I never experienced some of the things @robertklep talks about. But I aknowledge that some people have. But for example I donât restart Homey on a regular basis and I havenât had problems with either z-wave or firmware updates. This is between two Homeys also (2018 and pro).
Homey do have its share of bugs though and one should be aware of that.
Edit: The omitted pretty obvious advantage is what others have talked about also with different protocols supported.
I used HA, then moved to Homey. Reason is the same as mentioned above - HA requires hours of reading documentation and writing YAMLs just to do basic things. Itâs very powerful, but time consuming to run. Homey is WYSIWYG - you can setup everything within minutes, without any documentation (well⌠almost).
However, Homey is not perfect: