I consider myself an early adopter for a lot of home automation things. I also consider myself technologically advanced as it relates to electronics. My home has a multitude of smart home “appliances” – ones from Philips, TP Link, Switchbot, Ecobee, and more. I’ve wired up my network with Home Assistant; it works well enough for my needs but moving to a professionally (read: not community) supported equivalent feels like it could be an improvement for the effort I need to put in to maintaining my home setup. My network is segmented – one for my computers and one for my IoT devices; I do this for security, and I think it will become relevant later.
Bottom line up front, Homey has the right intent in mind of supremely easy setup and functionality, but I do not feel that this device is ready for primetime yet. Where I think Homey will work best is for entirely offline home IoT networks, but I don’t see how it could accomplish that given most smart home devices require an initial cloud connection for them to download firmware updates and be configured for the first time.
The thing that drew me to the Homey was that all my disparate devices could be integrated with a single device. All my smart home devices connect to the cloud – mainly for the initial firmware download above, but also because I like them being accessible remotely. The ones that do not (specifically ones on the Z-Wave network) are still connected to Home Assistant for manipulation. On the tin, Homey checks all of these boxes with ease.
Out of the box, you get the device, a charger and a USB cable for it. The instruction manual is sparse, but the setup is basically “plug it in, download the app.” My first attempt with it resulted in a device that would attempt to connect to WiFi, then give up. A factory reset by using the pinhole at the base didn’t resolve the problem, so I needed to perform a several hour-long factory reinstall by using their web application and connecting the device to my laptop.
After the factory reset, I changed from my IoT segmented network to my home computer network. This got me to the point where I was able to begin to configure the device, but it was not the end of my problems.
Most all of my smart devices were added without issue. Homey is based around “apps” that will allow you to connect devices that do not link via infrared, Z-Wave, Zigbee, or Matter. I added integrations for every device type I mentioned earlier and it was _mostly_ fine. For my hue and ecobee devices, it was literally as simple as logging in. My two Z-Wave devices were marked as generic “Z-Wave Device[s]” with no means of interacting with them – this was for an older Schlage smart lock and a Qolsys alarm panel. I was able to add the alarm panel via a Home Assistant integration, but the fact I had to use a competing standard to make things work defeats the value of this appliance significantly.
Even after setup, I had issues with two of the five apps I was utilizing. The Switchbot app was misconfigured, preventing me from being able to log into it, and the TP Link app kept reporting that it was rate limited. Just like before, I was able to work around and “ignore” these problems, but it adds to the frustration of the experience. (Editing note, the TP Link issues seem to have shaken out over writing this review)
After the initial teething, how well did it work? Pretty well. Homey leans more towards automation than observability. Each Homey app publisher selects what data can be represented for their various device; overall I found Home Assistant to have more data available for devices out of the box. For instance, my TP Link integration in Home Assistant tells me the line-level current, voltage, current consumption and overall consumption today. The Homey will provide a hard number and a graph of the usage at a specific moment in time, but there’s no additional data present.
Homey’s strongest offering is automation via flows. If you have basic needs, Homey has a simple “When X and Y, then Z” flow. If you are a more advanced user, there is a drag and drop “blueprint” style flow with conditionals. The first flow I wrote using the advanced flow was “if a window or door is open for more than two minutes, turn off the HVAC.” I have written this flow in other applications, so I understand the general “what” and “how” of what I need to do making this a great test for exercising the capability.
The advanced builder is relatively feature complete, but there is a steep learning curve, and it sometimes requires you to think creatively about your solution depending on how the Homey app is written. For instance, I can start a flow with “when a contact alarm is on” using the community supported app for Home Assistant, but if I want to conditionally check it again to make sure the contact is still on, I need to check for the negative case for if the contact alarm is off as the same check doesn’t exist for an “and” step. The builder also allows you to set variables using existing device states but reusing them as inputs to states seems to be impossible as of this moment (for instance, I want to set my HVAC back to the mode it was at last).
I can see the world of possibilities opened with this script implementation. I’ve been meaning to get a water sensor and tie it to some lights or notifications for “hey you’ve got a leak,” but getting that integration set up using my existing tools is not nearly as trivial as this Homey will make it.
For the people who want to go even further, Homey has an app called HomeyScript that lets you code automation using JavaScript. Much like the advanced builder, it is relatively complete with its own set of challenges. Nothing insurmountable, just sometimes it feels closer to an interview coding challenge than meaningful work. HomeyScripts also cannot be used as standalone flows – they must be integrated into a simple or advanced flow. I would love it if they could be run standalone.
I wanted to love the Homey. Being able to replace Home Assistant with a singly integrated device has huge promise and one that requires next to no effort on my part makes it so much the better. Having a scriptable interface built in to the controller itself alone made me want the Homey. But after several hours of installation and having difficulties getting integrations to work with minimal configuration, I’m having difficulty figuring out where this device belongs in the user spectrum. For novices, the troubleshooting I was working through likely would have ended up with a return first. For more experienced people, while it does keep the promise of a singly integrated point of service, it still feels like there are other alternatives.