What do I need to do to get ready for Sept 30?

Devices & Integrations
41

This is the list of everything that has been migrated to date. There is more on the way. Beta users already see these, but the main user base will be transitioned to these soon.

1 Like
42

Right now points 5 and 12 in my long post above could still get you. @martin.borg had devices using stock DTHs, migrated them manually to stock edge drivers, and they didn’t work. @philh Ended up creating a custom edge driver for him for some of them.

Multicomponent devices just don’t work The same way anymore, and the dependent components don’t work with the voice assistants. :disappointed_relieved:

43

Hi, @uberrob. The team is looking into this requirement, but there is no news yet.

This is in the same situation. The team is aware of the reports made when hitting this limit.
I’ve seen the Community drivers support several devices, so, we suggest you check which drivers you install according to your needs and that you can switch a device from using a driver to another (compatible) one.

44

And again, I have no idea what’s going to happen to those accounts that have more than 200 devices when they go through the automatic migration. :thinking:

45

There will be a notification in the app for this kind of user that isn’t around the Community or up-to-date on what’s changing on the platform.

46

Thanks @nayelyz - I’m way less concerned about the drivers than I am about the low caps.

47

Thank you for this

48

My guess is that they will go through. If this is similar to what happened before, the limitations are on the UI client side, not the server side. If they are already in the DB for the user, they are in.

My guess, anyway.

49

The limitations aren’t in the UI for the 50 edge drivers, because you don’t add them through the app. I don’t know about the devices.

50

Regarding device limits. Anyone with multi switches (parent/child) will have to create virtual switches to have Alexa be able to control those swiches. One power strip can add 8 devices. Do virtual devices count against the 200 device limit?

51

Yes, unfortunately. but since it’s possible that future virtual switches will have to run on the hub as edge drivers, I suppose that makes sense. again, we are still waiting on a detailed answer for what virtual switch options will be available and whether they will all require a hub or not. :disappointed_relieved:

52

I previously asked this same question (not sure where) and was told that it wasn’t a hard cap but could result in degraded performance beyond that cap.

I suspect that would really come down to the processing load of the devices involved. A virtual switch would have almost no load, but a device that does a lot of polling would have a higher load. Devices that share a driver (hub-hub integrations, zwave switches, etc.) would also have a lower system cost since they aren’t spinning up a bunch of different drivers.

53

@philh30 I have exactly 50 drivers running, without any issues. Many of those are testing versions. I might have to consolidate some of them.

Actually, I think that will be the next big step for developers to consolidate multiple drivers in single one. I have realized that many of them are just added fingerprints, based on the same driver, that should be consolidated into one.

Bigger problem is how can that be achieved. Maybe shared GitHub repository.

Screenshot_20220913-182956_SmartThings
Screenshot_20220913-182956_SmartThings1080×9119 423 KB

54

Some how I missed this. Do I read correctly that as of 10/15 SmartLighting stops working but we have no insight yet on what the replacement is or if there is an automatic migration? I hope I am misunderstanding as that would be awful.

55

My Honeywell Thermostats show placeholder but they don’t have an edge driver. Probably cause they are linked to SmartThings thru the Honeywell app. It’s concerning because it’s the deprecated app, not the new one. The new one never shows any thermostats installed even though I’m using it to control the thermostats.

56

Multiple questions there.

Read the official announcement carefully:

September 30, 2022, at 00:00 (PST) we will start migrations of Groovy device DTHs as well as SmartLighting and SevereWeather SmartApps, two of our most popular Smartapps built on Groovy. On October 15th 2022 certain functions of the legacy developer IDE, such as the creation of new DTH’s, Smartapps, and debugging tools will be removed from the SmartThings platform and will no longer be supported. After migrations are complete, this means that devices and automations previously using Groovy will now exclusively operate with our latest hub and cloud technology.

The End of Groovy Has Arrived

A) we don’t have an exact date for when any groovy smartapp will stop working.

B) Smartlighting IS going to be migrated to the new platform, but we have no details as to what that means exactly or whether it will have all of the same features that it does now.

C) they are allowing for the possibility that the smartlighting migration could start as early as September 30th, but again, no specific timeline has been given.

D) they have not said anything one way or the other as to whether the region locks for the new SmartLighting will be the same as the ones for the old.

E) They have not said one way or the other as to whether smartlighting automations will count towards your routines and automations limit.

F) it sounds like it’s possible that we will lose the ability to add more groovy smartapps before our existing Groovy smartapps stop working. That lines up with something @rboy said he and other developers have been told quite a while ago. But again, no details.

——
So there are just a lot of unknowns except that there will be something called smartlighting on the new platform for some people. :thinking:

2 Likes
57

I have Honeywell thermostats at two locations. They do show as placeholders in the IDE, which I’d expect as they are linked cloud services. But I also have the thermostats displaying in the ST app. I have controls on the thermostat’s device page for temperature, fan mode, mode and an indicator of humidity. Strange that you don’t have the device in the app.

58

Same here (thru TCC cloud) and mine show both placeholder in the IDE and have tiles in the app.

59

@JDRoberts - you are correct on this except that the (excellent - I have to say) Edge driver created for me by @philh30 is a replacement of a custom DTH actually (the one for MCOHome MH-S312/4 switches). The ones using a stock Groovy DTH that gave me trouble thus far are:

  1. Aeotec Dimmer Switch (lights suddenly flickered, like crazy flickering, because of an unsolicited, unexpected parameter change during the change to Edge driver, fixed manually);

  2. My Philio Pan-08 blind motor controllers - these are the worst as they bind themselves to a stock DTH without manual intervention and worked surprisingly well out-of-the-box… yet no Edge driver works for these now.

  3. My Vision Security garage door tilt sensor: this one “works”, but keeps reverting to open right after closing (a fraction of a second later), then reverts to closed anywhere between a few minutes to a couple of hours later. Yes - it could be a device issue, maybe I broke it during exclusion/inclusion, but I have no way to know as I only have one of these devices.

I still have more to test, but hopefully I won’t have to add to the above list.

1 Like
60

Thank you @nayelyz. Notifications and any other communications are good, of course, and appreciated. However I am still disappointed that not all fingerprints covered in the old stock DTHs have been included in the Edge Drivers.

Also, I have seen it stated that if the manufacturer is no longer producing/selling the device, then it would not be added to the Edge Drivers. I don’t actually know whether that is an official ST line, but I do have a specific device that is still being manufactured and still being sold, yet its fingerprint is nowhere to be seen in the Beta drivers.

1 Like