Groovy deprecation - October 15, 2022

What new app?

There’s supposedly a new app version being announced this fall to support the Home Connectivity Alliance. That’s not Matter: it’s a different initiative just for appliances (which are not presently included in Matter). Lots of rumors:

Plus this official “major update” announcement:

Both may be Android-only.

1 Like

Would i be right in thinking the HCA is geared more towards C2C connectivity JD, bringing a more diverse set of wifi products into ST without the need for an ST hub

It would not make sense to require a hub for wifi products

I just cannot see that being the case JD, although it is true the Apple version of ST is very poor

Maybe Apple themselves are making it hard for ST to get it right, they are pretty cut throat on there approach to competitors

I don’t think it’s Apple in this case: the Ikea and Aqara home automation apps both have fullfeatured iOS versions and both are adding Matter support.

I think it’s more that many of the features in the “major update” that’s been officially announced are specifically in regard to the Android operating system: they may just not be relevant to a nonAndroid phone. :thinking:

Right that WiFi does not require a hub, but it doesn’t require a cloud either. Only if you run without a cloud you might then need some kind of hub to handle the local messages. :thinking:

For example, HomeKit devices use WiFi, Bluetooth Or Thread, but everything except the voice assistant and camera cloud storage runs locally, no active internet connection required. The same Meross WiFi devices that require a cloud connection for SmartThings run just fine without internet on HomeKit. So it just depends on how the platform is designed, it’s not a technical requirement.

Matter is also intended to run locally for WiFi devices: we’ll see how that goes once it arrives.

BTW, @TAustin has an Edge Driver for Shelly WiFi switches and sensors which allows them to run locally with ST now. (The official integration is cloud to cloud.) he’s done some amazing work on the new platform. :sunglasses:

1 Like

And his patience knows no end, i know coz he developed the camera integration which i helped with in small part :innocent:


Here’s everything I know about the end of Groovy


just curious on an item in the Platform Transition FAQ page:

Philips Hue (V1)
Philips Hue V1 Bridge
This device will no longer be supported in the SmartThings app.

I thought the V1 Hue Bridge lost cloud connectivity with Hue a few years back after they stopped supporting it.

1 Like

I think your right, so I assume it still worked over LAN which is how it still worked with SmartThings?

A couple other resources:
Official Announcement (there should also be one coming in the app at the end of the month)

Official FAQ


The hardcore webCoRE users are going to be very disappointed.


indeed. It’s unfortunate nobody from the webcore team was able to take the time to adapt it to the new platform.

1 Like

It would still have to be hosted somewhere…

right. they had two options to keep it alive:

  1. cut the feature set back and become a frontend for the Rules API (basically exactly what we saw as a POC at SDC 2018)
  2. Become a paid service with their own hosting

They did neither :man_shrugging:


I’m a hardcore Webcore user and had been planning to make the move to Home Assistant, but I very much doubt I’ll have the time to do so before September 30th. What a pain…

1 Like

try Routines in the mobile app or

There’s no way I can replicate all of my Webcore automations using app routines. Whatever happened to the promised Routine Creator?


What are you talking about?
You have no idea, there is no “they” when it comes to webCoRE, there is no executive board, who is this “they” you speak of?
Do you know what the “CoRE” stands for in webCoRE?
“Communities own Rule Engine”.

Exactly what happens on September 30th seems to be described slightly inconsistently. In one place it is is made to sound like the lights are being turned off, but in other places it is the start of a transition.

Frustrating to see the FAQ claiming, yet again, that the presence or absence of ‘Driver’ in the device settings in the app can be used as an indicator of whether or not a device uses Edge. That only applies if you are using the app as the Location owner, or possibly the hub owner if that isn’t actually the same thing (and if it isn’t then I’ve no idea how you know who the owner is). At least that is how it works for me.

1 Like