.... I said that it has a new home at Hubitat.
aaaand they banned me from the group.
Oh well :).
21 Likes
Truth hurts I guess.
4 Likes
I am sure many are bitter that they are having to deal with the issues and tired of hearing about greener pastures.
When they first announced the demise of Groovy, I decided that if I was going to have to recreate drivers and rebuild my system, it would be on another system. So, I did. Glad I switched when I did. It is almost sad seeing the posts in that other community. People popping on today that were unaware any transition was happening. (I really don't know how)
5 Likes
Wow...just wow. It's been SO long since the info on the changes was available.
4 Likes
Not everyone tinkers on their hub every other day, or even reads emails for that matter. Probably had the hub all setup humming along, did not expand their devices or check in on anything.
If it ain't broke, Samsung will break it for you?
10 Likes
I did not think it was possible to go longer than a month without being forced to tinker with something on ST. Samsung routinely broke stuff on my hub. Or, at the very least, I was logging on to find out if the latest failures were a cloud outage or just my hub.
4 Likes
When I was on ST, I rarely did ANYTHING with my hub. Once I set up my lock and half a dozen bulbs I was done. Moved to Hubitat, and I seem to be in a never-ending cycle of tinkering and expanding.
5 Likes
I realized the other day that I was subscribed to several home automation channels on YouTube from my ST days which was over 2 years now. Most recent videos were at least 6 months ago and just basically a remake of old content.
Outside of Samsung appliances and electronics, who is keeping the platform alive!?
1 Like
It is the ST community, catching up with Edge drivers for hundreds of devices at incredible speed... I have the feeling that 90% of the Edge drivers are now made by ST community developers, not by Samsung.
5 Likes
I'm not entirely clear on what an edge driver is.
The Edge drivers (written in Lua language) are replacing the Groovy language DTH (device handlers) that were used in SmartThings until now.
They are executed always locally on the ST hub.
1 Like
Geez, shouldn't the conversation in that group be about finding solutions, not protecting or promoting some non-existent single-solution fiefdom? I expect most of us are already using some combination of the available tools, whether it's Alexa, Google Assistant, IFTTT, SharpTools, node.js servers, or whatever. What are they afraid of?
Perhaps pointing out that they could continue to run webCoRE with SmartThings with a Hubitat hub and an app like HubiThings Replica still would have upset them—because then they'd have to begin facing all they've been missing over here on what they misguidedly view as the "dark side." 
3 Likes
I was banned from that group looong ago. When AT 'sponsored' the group, I stepped back my posting/commenting. If someone tagged me in something or directly asked a question, I would reply. But I'd often find that those posts would be deleted anyway, so I suppose "SharpTools" is a forbidden topic too. 
8 Likes
Yeah, and it's too bad - I still have a ST hub for a device or two that Hubitat doesn't yet support (Schlage FE599)..
..and I have a long history with ST. I was an original kickstarter backer, I was the first ST featured community developer.
8 Likes
Unfortunately, my ST hub isn't even useful as a doorstop. Mine was deprecated and I was forced to either update to a new hub or shut down. Since they STILL do not have a viable path for migration, I figured I would just get a new hub that does have a path (not perfect, but better than nothing). To the best of my knowledge, none of the Hubitat hubs have been deprecated either. They may be old and eventually die. But, if they still work, you aren't forced to replace them.
Between their hubs, and the features that they are removing from their phones, and the removal of Tizen from their watches, I swear it is like they are intentionally trying to put themselves out of business. I know they are pushing themselves right out of my household.
3 Likes
I will also say that Hubitat doesn't force you to upgrade platforms. It's entirely up to the user. And if something goes wrong, you can always roll back. ST doesn't give you that option.
3 Likes
Most cloud service based products are going to be this way, not specific to Samsung. Amazon just shut down all the Cloud Cams, Arlo is shutting down a line of their cameras. Insteon went offline without notice. The list goes on and on.
Was your hub a V1 ? The V2 came out in 2015...
In Samsung's defense, the V2 and V3 ST hubs were not shutdown and they built a migration path for the possibility of most of the Groovy based DTH's to be supported under the new environment. Its been rocky and there are caveats but they didn't just kill them all off.
I actually have that line. You will still be allowed to use them, albeit with limited capability and no updates. I left them long before I left Samsung for similar customer service reasons. However, they apparently still have my cameras in their database listing as they sent me an e-mail.
2 Likes
Same here. When ST first started down this path I also had a V1 hub and saw the writing on the wall. I jumped ship at the beginning of 2020 when they started making changes to the ST platform and some of my apps quit working. My only regret is that I didn't jump to HE a lot sooner.
4 Likes
