Expecting my new hub to arrive on Monday. Currently use Smartthings with about 130 devices, and have been using Webcore and Echospeaks. Finally got hacked off when the new ST app came out (how is that an improvement?!?!) and it looked like Echospeaks was being ditched.
Plan is to fire it up and use Hubconnect to get used to it, move all my routines from Webcore to Hubitat Rules, and when I'm confident it all works move the devices over.
I'm planning to keep my Hue hub, and probably keep ST running for presence and Ring bell integration (that's still not supported, is that right?) and DSC Alarm (via Envisalink, although currently connected vi Konnect) and anything else that doesn't work during the cross over.
Devices I've got are:
Hue hub + about 10 bulbs
Smartthings sensors and power outlets
Fibaro smoke detectors
Tado Thermostats (do they work?)
Xiaomi sensors (motion and contact)
Echo devices (via Echospeaks)
Foxx leak sensors
And a few virtual switchs, Raspberry Pi via WebIO etc.
Just joined for exactly the same reason and roughly the same ideas. May as well hang on your coat tails rather than a new thread.
I got hacked off for the same reasons and for the complete lack of forward motion in ST with respect to "generic" things. Everything being added has to be business case based it looks like, no new generic device profiles regardless of Zigbee/Z-Wave/BT standards etc.
What finally made me make the move was - and I hope this works - trying to integrate a couple of old but reliable CCTV cameras that just do RTSP and ONVIF out of the box, but ST has nothing.
Node-red is my cross platform home logic engine with ST being principally a device handler with some lighting logic, so the move may be simpler than yours.
I love node-red for it's variety and simplicity. But.
I've recently taken to coding again becuase of Go (Golang) and I'm thinking of playing with that as my in-house logic engine since it does pretty much everything (protocol and format wise) out-of-the-box. But no UI, which to be honest isn't a big deal for me.
So is the performance OK? I'd read somewhere that it can be slow?
Also I've sometimes struggled with some of the logic working when stuff is changing states and timers are timing out, so was going to look at native rules to see if any of that worked easier?
Typically I've integrating Google Cal feeds with time-base events and presence sensors to do stuff that IFTTT or the ST build in routines can't cope with.
That is what I heard as well when I first came over, but since then I have heard from several folks who have many more devices and pistons running than me with no issues. I have not had any issues, that I can tell. My Hub will sometimes seem to slow down, automations will be slow, but not just webcore automations.
Also many people who don't run webcore experience that so I really don't think it is the cause. A reboot and things will go back to normal. Some folks reboot their hub nightly I do not. I only occasionally will see this and I will reboot manually as necessary.
You can use an Alexa Routine (even if you don't use Amazon Echo devices) to like Ring with Hubitat. Just use the Ring Skill to integrate the doorbell with Alexa. Use the Ring Motion and Doorbell Presses as Triggers for Alexa Routines. Within the Alexa Routine, turn on a Hubitat Virtual Switch (be sure to enable the auto-off feature on the virt switch.) Now use that virtual switch as a trigger for any Hubitat automations you desire.
I have used this technique for ~2 years now, and it works reliably and quickly. Much, much faster than using IFTTT.
It really depends on how much you pile on. At first I made my poor litle C-4 run all my devices, all my dashboards, all my apps and rules, plus all the community app I wanted to run for dashes and other stat tracking.
Did my hub slow down? Yes
Do I blame it? No
Now I have two one for devices, one for custom app/dashes, and most my rules run via NR. Once the dust settles and a grab a C-7, make the switch, not sure how I will divey up the task yet.
In the end I think it is all about how you utilize your resources, much like everything else.
So been having fun with this, moving stuff across from ST bit by bit, sorting out snags as I go. All pretty good so far. I think I may have to keep the ST on in the lng run for various legacy reasons, but happy so far.
The main problem I've had is that I'm using HubConnect to link the ST to the HE, and HE can see the ST devices etc all fine and dandy, but I can't see any HE devices in ST? I've selected these in the HE app and have the ST app installed by I can't see an HE devices in ST, am I missing a step? I did a search on the forums and couldn't see anyone else with this issue so I must be doing something dumb!
I've made some real newbie clangers which means I've had to redo some things but can't say I regret it so far. You definitely need to make sure you do your research for some stuff, there's not really a single point of all info you need.
Part way through the journey now and all good. Well worth the effort.
So I've rebooted and moved to a different network connection and got it working, so it must have been the network I guess? A bit worrying that nothing works if it loses it's connection, that can't be right? I mean I guess Hue etc won't work, but I thought the other stuff (Zigbee etc) should work?