Farewell Hubitat

I've had no complaints and have happily used it for three years.

But about a year and a half ago, I fired up an instance of Home Assistant, and it has slowly been sucking all the devices and automations from my Hubitat.

At long last, the Hubitat has no more devices connected to it.

If you are pretty technical and want to tinker, I would reccomend trying out Home Assistant. Hubitat is fine and very reliable, but home assistant just has more features. There is a bridge in both directions, making them very easy to integrate and slowly move over.

Also, if anybody knows a decent price to sell a C7 hub for (locally at this point, no shipping), please tell me!

6 Likes

Have fun w/HA...

Very true, I'm a tinkerer who found tinkering in HA was just a bridge too far for me. :slight_smile:

Glad you had a good experience here. Best of luck. :smiley:

7 Likes

Happy travels on your HA journey

I've had HA running and connected to Hubitat both ways for a bit now. It really is not sucking me over, though. I'm pretty technical and I like to tinker, which is why I stay on Hubitat and just use Groovy code to do everything.

I haven't found any features I want to use on HA over Hubitat, but HA offers some fun toys so I see why people like it. It certainly seems like a plenty capable system though, overall.

4 Likes

I do use HA but exactly as it stands for ASSISTANT.
it is very nice companion for bringing in devices not directly compatible with HE.

3 Likes

You could even say HA stands for Hubitat Assistant :grin:

6 Likes

I have started an instance of HA as well but only use it for the integrations not in HE and the expanded device list supported by Z2M.

I bring everything possible into HE via the HADB and write all rules in HE. Nothing at this time goes the other way. Don't plan on it either.

I am glad you had a great experience on here and if I was you I wouldn't get rid of my hub. You never know what might happen in the future.

2 Likes

Great to hear.

Not sure if you recall, but you're the sole reason I'm here. Back in the smartthings days, you talked me through using konnected.

This was pretty limited in smartthings, but you showed me how much better these little boards worked under hubitat.

At the time I'd heard of hubitat but thought it was out of my reach for various reasons.

Combination of smartthings really pissing me off, plus your nudging towards hubitat, made me bite the bullet.

The wife and I weren't in a great place financially and I'd invested a bit of cash into smart trvs already due to the structure of the house and the cost of heating. Plus we had our 2nd child on the way. Smartthings utterly shagged my heating system, overnight. I was fuming.

Bit the bullet and bought a c7 totally unknown to the wife. Quickly learned a bit,, managed to get refunds from amazon for the smart trvs (they really didn't need to do that, so that was lucky). Bought a few cheap actuators to replace the trvs and a handful of nodemcu boards.

Knocked a basic dash together and managed to get everything up and running 100%, zoned heating on every room.

Once that worked, I let the wife know expecting her to bite my bollocks off, but the WAF was through the roof. She ■■■■■■■ hated smartthings.

And so here I remain.

Best of luck with it all and thank you so much for the initial recommendation and guidance.

:+1::+1::+1::+1::+1::+1::+1::slightly_smiling_face:

8 Likes

I want to learn more about Groovy (retired programmer) and possibly write my own drivers. What resource would you recommend for a newbie to Groovy?

Groovy is just a variant of Java that allows scripting, if you know Java at all, you should be good. Still nothing hard if you have a programming background. You can even include Java libraries in your code. Of course, Hubitat does limit what libraries can be used in the sandbox, but the most commonly used libraries can be included at the top of of an App or Driver.

The developer pages are pretty good, I would start here with the platform overview.

Do you use Webcore now? That really teaches you a lot about the platform, the way it presents things to you as you select them. I used all Webcore for years, and I could make some very complex automations.

I first started writing simple drivers to store global variables, instead of using the Webcore global variables. Writing a data storage driver is a good first driver to write. I still use drivers as data stores, I can name all the state attributes like variable names. Commands in a driver are like Setters, and by using the currentValue("attribute") method, you can get the values from it into an app like a Getter.

A good first app is a simple connector app, that links two devices together. You will need to create inputs in settings to add devices, and you can then subscribe to events from the device to call a method, and you will get the event object that triggered it as parameter to the method, which you can then check for the value the event sent.

So I would look at the Hubitat Developer pages, simple data store devices, and simple connector apps. That was all I needed to get a basic idea of how things work.

The nice thing about starting from Webcore is that all your automation logic is already written into visible coding structures, to help you convert them into apps. I converted about two hundred Webcore pistons into custom apps using storage drivers as time went on.

The limit of Webcore for me was not being able to call methods, and trying to call a piston like it was a method by sending it values just isn't the same, as a Webcore a piston cannot return a value. So it is hard to reuse code in Webcore.

I wrote my automation apps based on areas in my house, instead of one big app. I have three main apps that control "areas" of my house, for all my lighting scenes and automations for those rooms.

Good luck! If you want a hand with something send me a message, I can share some of my code with you which you are welcome to use or learn from. I'm no coding genius for sure, but I can get it all to work. My methods may not be the best way to do things, but examples are always good.

2 Likes

I never actually knew you used the konnected for heating! I'm glad it worked out for you. Back here, I'm more worried about cooling than heating, but its still interesting to see!

1 Like