That thread was moved to its very own section.
The thread is a pretty good read.
I started my migration to Hubitat last week after the endless problems and lack of transparency to the development community. It took about a day of learning curves then off to the reset zwave and zigbee devices. Overall I appreciate the set up on a desktop computer, and the IDE is built in so you are not jumping between the iOS UI and the IDE to see what is going on. I am a huge webCoRE fan, but have found most of my logic does work in the native Rules Engine.
To ease the pain, I am using HubConnect v1.64 that syncs the ST and HE hubs, which has provided a seamless experience to the household. In fact, I am using HubConnect to expose the devices to SmartThings, then SmartThings to ActionTiles. It would be great if ActionTiles was native to HE, but HE does have SharpTools integration that I will probably move too over time.
Never thought I would be a big fan of local processing since my job is all about the ‘cloud’, but when running local everything executes remarkably faster AND the last SmartThings outage really had no impact.
Odd on how my attitude changed in only one year when I said this about staying with ST.
The final reason to switch was the pending shutdown of Echo Speaks next month on the ST platform. I had the HE hub in my desk drawer and figured it was time to take back some control of my own household automation. It ST wants to become a closed ecosystem with an external API - great - I will use my HE hub to drive the ST API if still required. BTW, Echo Speaks runs fine on Hubitat.