Trying to decide (Homey Pro or Hubitat)

Good morning.
I know this is a Homey community, so I’m would think responses would be skewed toward Homey.

Try to find a good solution for my Smart Home to have control locally. I’m not too advanced with it yet but will be adding more as I go. I currently have a Ecobee thermostat, nest doorbell (which I will be switching to Eufy), Philips Hue lighting, iKea blinds and Arlo cameras (which will also be switch to Eufy). Opinions on whether I’d be better to go with Homey Pro or Hubitat would be appreciated.

Thank you.

I don’t know Hubitat, so I cannot help comparing. What I can say is that Homey is very simpel and I do like the app and the simple flows. But most important is if both solutions support all your smarthome products in use and how many brands will fill in future needs. But look into Homey Pro, I would not recommend the cheaper Bridge in combination with a cloudsubscription.

I don’t have experience with Hubitat, a friend who is a software engineer does. He likes it well enough but from plenty of chats I can’t help but think that Homey is more user friendly for those of us not software engineers

Just some ChatGPT information … (quickly checked and from my perspective seems to be relevant - I did not alter output in any way (even I’m Homey Pro fan despite of all it’s “benefits”)

Given your requirements and current smart home devices, let’s evaluate both Hubitat and Homey Pro to determine which might be a better fit for you.

Device Compatibility

  1. Ecobee Thermostat
  • Hubitat: Compatible and can be integrated locally.
  • Homey Pro: Also compatible and integrates smoothly.
  1. Nest Doorbell (switching to Eufy)
  • Hubitat: Nest devices require cloud integration. Eufy integration can be achieved through community drivers, but it might not be fully local.
  • Homey Pro: Offers better integration with Eufy through the Homey app store, though some functionality might still require cloud access.
  1. Philips Hue Lighting
  • Hubitat: Integrates well with local control using the Philips Hue bridge.
  • Homey Pro: Integrates smoothly with Philips Hue, both through the bridge and directly to bulbs.
  1. Ikea Blinds
  • Hubitat: Supported, with local control via the Zigbee network.
  • Homey Pro: Supported and integrates well with direct Zigbee communication.
  1. Arlo Cameras (switching to Eufy)
  • Hubitat: Limited direct support, relies on community integrations which may not be fully local.
  • Homey Pro: Better support for Eufy cameras via the Homey app, though some features may still need cloud access.

Ease of Use

  • Hubitat: Known for its powerful automation capabilities but has a steeper learning curve. The user interface is functional but not as polished, which can be challenging for beginners.
  • Homey Pro: Offers a very user-friendly interface with an intuitive Flow Editor for automations. It’s designed to be accessible for users of all technical levels, making it a smoother start for someone not very advanced yet.

Local Control

  • Hubitat: Emphasizes local control, which means faster response times and increased reliability as it doesn’t rely heavily on the cloud.
  • Homey Pro: While it supports local control for many devices, it does rely more on cloud services compared to Hubitat. However, its ease of integration and use often outweigh this dependency.

Future Scalability

  • Hubitat: Highly scalable with robust support for custom scripts and advanced automations. As you become more experienced, you can take advantage of its extensive customization options.
  • Homey Pro: Also scalable with a wide range of apps and integrations available. It’s user-friendly and can grow with your increasing needs and comfort with smart home technology.

Community and Support

  • Hubitat: Strong community with active forums where you can find a lot of custom drivers and automations shared by other users.
  • Homey Pro: Active community and extensive app store. The visual Flow Editor is widely appreciated for its simplicity and effectiveness.

Summary and Recommendation

Given your current devices and the need for local control while not being too advanced yet, Homey Pro might be the better choice for you. Its user-friendly interface and easy-to-use Flow Editor will make it simpler to manage your smart home setup. It offers good compatibility with your existing and planned devices, and while it does rely on some cloud functionalities, the trade-off for ease of use and integration is often worth it for users who are gradually building their smart home.

Hubitat is a strong contender if you prioritize complete local control and are willing to invest time into learning its more complex system. It’s great for advanced users or those planning to dive deep into custom automations and scripting in the future.

Ultimately, Homey Pro seems to strike a balance between ease of use and local control, making it a solid choice for your current needs and gradual expansion.

Thanks for the detailed analysis Sharkys. If read that voice integration works using Google or Siri shortcuts. Do you happen to know if the response is pretty instantaneous or is there a delay with it going to the cloud and back?

Thanks again.

It’s kind of immediate when using Google Home controls but using voice control, it’s kind of “works as designed” (but the delay is not on Homey side)

Hmm. This could be reasoned either way…

From a non programmers perspective Homey has a much friendlier UI and provides a really nice ‘flows’ based logic/scheduling offering… however.

If you are a hobbyist+ level programming user then it’s actually far easier to code a driver or application on Hubitat using Groovy. Hubitat provides a very approachable environment for intermediate programmers although the documentation is a bit lacking… you can also easily view other code examples.

Homey however is a much more complex (and refined) environment and needs skill levels above Groovy. I mean the coding language not the UI. Competent pro coders prefer this but it can makes entry/mid level programmers feel a little adrift. Homey’s code documentation is complete and excellent however.

For my own ‘quick’ HA needs I implement on Hubitat and only use Homey if I’m prepared to spend a lot of time on the project as I’m an enthusiast still learning. Both Homey and HE (and HA) have different strengths and can be used together if and as needed .

So Hubitat at a coding level sits neatly between Homey… and Homey. UI on Homey is great for non coders.

Ooops forgot to mention Homey has a scripting language called HomeyScript (Javescript) that provides a. solution between UI and full coding needs.

Going back to your OP either would suffice but Homey has a sexier UI.

So … I have Hubitat. For 1 hour already. First impressions:
The app is rather medieval. But … this OOMI Mote switch was added without any problem (as Aeotec).
I added a wall plug too. The switch can control the plug two floors below the hub in the garage. It works flawlessly and reacts immediately. No other devices between the floors. On the other hand, with Homey Pro, I needed to add several plugs along the way (about 3) to create a Z-Wave mesh and it still works slowly and is not reliable in the garage.
So my conclusion is clear: Homey Pro is a pure disaster from hardware / sensitivity point of view. And its software too (crashing when trying to add this switch). Their rule editor is much nicer though. The mobile app too (although the Fibaro one is even nicer).

Update: Integrated hubitat with home assistant. Very happy so far.

I am in a similar boat, and can’t decide between Hubitat or Homey Pro. I am moving to a new home and will buy everything new. Homey Pro biggest concern is the lack of support for product.

Wish I could run both side by side.

I think that you cold run both. However, I do not see the reason. As for Hubitat, its mobile app is poor. You need to integrate it with Home Assitant and then this duo is great, much better than Homey.

I run both a certain things work in Homey, but not hubitat.

I’m probably a few months late to the discussion, but I want to add a personal note here:
I’m in the process of leaving Hubitat.

Over time, I’ve become increasingly disappointed with the direction the platform is taking and, more importantly, with how customer feedback is handled. I was a strong supporter of Hubitat for years, so this isn’t a decision I take lightly.

Here are a few concrete examples.


Example 1: Dashboards and UI decisions

Hubitat dashboards still follow a Windows 8–style tile concept, which feels outdated and extremely limiting.

I tried to work around this by creating a much smaller grid (8×8 pixels) and spanning buttons across multiple rows and columns. This does allow tiles of different sizes and more flexible layouts.

Hubitat offers a custom CSS page to style dashboards, which in theory is great. In practice, however, the HTML lacks meaningful class names. I often had to rely on fragile selectors like:

div > div div div

As a developer myself, I know how trivial the fix would be:
add clear, semantic classes to the HTML, so users can simply write something like:

.hvac_fan { … }

This was never done. Instead, Hubitat introduced EZ Dashboards, which feel even more restrictive and, frankly, more childish.


Example 2: European TRV support

For years, European users have been requesting proper TRV (thermostatic radiator valve) support.
The response from the team has consistently been that TRVs are a niche product.

From a European perspective, that’s simply disconnected from reality.


Example 3: Matter implementation

Hubitat prominently displays the Matter logo on its homepage.

In practice, Matter works through device- or brand-specific drivers, leading to an overwhelming setup process with far too many choices. That completely misses the point of Matter, which is supposed to simplify onboarding and abstraction — not make it more complex.


The breaking point

I can’t yet say whether Homey performs better — I’m still waiting for my device.

What I can say is that I’m deeply disappointed by Hubitat’s attitude toward its community. After posting constructive, technically grounded criticism on the forum — in a friendly, non-personal tone — I was blocked.

That was the final signal for me.


I’m not here to attack anyone. I’m sharing this because I believe platforms live or die by how they listen to experienced users — especially those who supported them for years.

Just my perspective.

What I can say is that I’m deeply disappointed by Hubitat’s attitude toward its community. After posting constructive, technically grounded criticism on the forum — in a friendly, non-personal tone — I was blocked.

Your Hubitat forum account was suspended for the weekend (it’s already active again). While you no doubt see even that temporary action as unjustifiable, the threads you created, and continued to participate in, turned into a disruptive flag fest.

So a moderation decision was made (not by me, in case you’re curious) that was deemed to be in the best interest of that forum.

ETA: wishing nothing but peace and love to the rest of the homey community :victory_hand: .

4 Likes

I respectfully disagree.

I was consistently polite and repeatedly stated that Hubitat simply does not fulfill my requirements. I also made it very clear—multiple times—that Hubitat is a solid and stable platform for other use cases. My disappointment is personal and related to the direction of development, not a general condemnation of the product.

What actually happened afterward speaks for itself: once I was allowed to post again, my new thread was again flagged and hidden. A moderator then contacted me asking what arguments I could provide to convince him to reopen and show the thread. That, frankly, felt absurd. I replied that I was done and that the thread could be closed.

From my perspective, Hubitat prefers to build walls rather than engage in constructive discussion—walls instead of taking criticism seriously and working with it. In my final post there, I stated factual things only: that I am replacing my Hubitat hub, that my migration has been ongoing for about a year, and that despite all this, I had recently recommended a C-8 Pro to someone because it fit his needs. At this point, I honestly hope he can still cancel the order, because I am done supporting a company that handles users this way.

I didn’t want to bring this up here, but to be honest, the main trigger was a side discussion about an action by Hubitat that I consider legally problematic. I won’t go into details here. I have no intention of escalating this further or pursuing legal action—that’s simply not who I am.

What makes this even more striking is the contrast: years ago, on this very Homey forum, I wrote a lot of aggressive and frankly unreasonable posts when my Sphere didn’t work—not even for basic functions. Not a single thread was blocked, closed, or hidden. I still don’t know whether the new Homey will ultimately be better for me, as I don’t even have the device yet—but at least moderation here does not build walls.

That difference matters. To me, it reflects a cultural difference: openness versus defensiveness. Europe versus America, if you will.

Last word: you were always different. And if everyone at Hubitat acted the way you do, they might actually have a better future.

Hi Pascal I we spoke recently on the Hubitat forum.

I am in the process of moving over from Hubitat to Homey. I am not a programmer these days and I have competing interests for my time. I like to tinker have an idea and then implement and tweak it. I have been doing some form of home automation for decades.

Moving to homey was not a choice I was intending but I lost my Hubitat system a week ago and have been unable to get it back up and working. The problem has been a flood of system busy messages and despite going back to previous versions it remains, it might well not be a Hubitat issue but it has been impossible to diagnose and therefore fix. Up to this point it had been rock solid and a great improvement from my previous system Homeseer.

So I decided to try homey and got a mini pro principally because I see the future as Matter and Thread. Also Homey appears to be more aligned to Europe and Hubitat to the states.

I run a hub and spoke arrangement and was looking for an integration hub to pull together, at a high level, the various systems that manage the house; cameras, alarm, heating, lights, presence sensors, voice, robot vacs etc whilst still keeping those systems autonomous.

My thoughts, so far for someone in their first week of ownership;

  • I have simple needs, which system works for you depends on where you are coming from, what devices and systems you are trying to integrate
  • Matter and thread are a must these days - both systems have some issues with Matter, Homey at least has a Thread router and will be more future proof.
  • Homey is so much simpler to create, maintain and validate logic flows. this makes it much faster. I have got my core system flows (lights mainly) up in around 24 hours, which includes both learning and writing the flows. Because I have most of my lights and presence sensors on separate hubs I could just move those connections using matter bridges.
  • You can organise the code easier in homey and group multiple logically aligned processes in the same flow making it easier to work out what is going on.
  • The functionality I get from the two systems is different, some of which is choice (I took a decision to not take my two remaining more specialist zwave devices across). For me I get slightly more functionality though from Homey and the forums suggest other areas that would be interested in going down
  • Both systems have a large reliance on community apps to add functionality.
  • I am still learning but it looks like Homey has more potential in some of the functions and what you can do with them.
  • Both have lots of great people who will help you out.
  • Homey has moods which whilst it has limitations do simplify lighting stuff incredibly.
  • Homey has the concept of zones which makes some of the functions I want to do easier to setup

I hope that gives you a bit of a view of the differences.

Thank you very much for taking the time to share this extensive feedback after using Homey for a week. I really appreciate it. My Homey should arrive in about two days, and I’m looking forward to testing it myself.

I used Homey around four years ago, and at that time the execution of rules was not very predictable. Even a simple automation like “At 6 a.m., do …” would sometimes run randomly. In contrast, Hubitat was rock solid and fully predictable. When I switched to Hubitat, I already knew I would lose the nice, user-friendly interface, but as a hobby programmer that didn’t bother me too much — reliability was my top priority.

Over time, however, I became tired of constantly having to build heavy workarounds due to missing or poorly implemented support for European devices. Eventually, it also became clear to me that the platform’s development direction was drifting further and further away from what I was personally looking for. That’s not necessarily Hubitat’s fault, but it no longer matched my requirements.

I’m hoping that Homey’s reliability has improved with software updates and newer hardware. If that’s the case, I’m very much looking forward to starting a new adventure with it. My setup is also quite different now: if you look at my overall strategy, Homey is meant to be the “cream on top of the cake,” while Apple Home and Hue — which already work extremely well for me — will remain the solid foundation underneath.