The End of Groovy Has Arrived

[alissa.dornbos]

Hello. Which devices are you concerned about having to re-onboard? Perhaps I can help if you share more about your set up?

We have a migration plan that covers many situations, and are trying to avoid having this case.

Edit: spelling

[pomartel (Pierre Olivier Martel)]

How about Sonos playlists? How can we start them with a Routine if Speaker Companion goes away?

[Shanapadila (Shana Padilla)]

I did that once for each hub I own months ago and just got broil plate response.

[Skates]

@alissa.dornbos I am in the beta program, when will Option 4 listed in your FAQ start occurring?

Specifically, I have Jasco and Inovelli switches currently running on Groovy drivers that I would like to see transitioned to Custom Edge drivers (already installed). I was told in the beta thread that this would not be supported without disconnecting and reading a device.

[markplewis (Mark)]

You’re giving your user community 6 weeks notice? This has been in the works for over two years and you decide to pull the plug with 6 weeks notice. Of course you do, Samsung, of course you do. Good riddance.

[alissa.dornbos]

If your Zigbee or Z-Wave device is currently backed by a Custom DTH (not published in the ST repo) and you have a replacement community Edge Driver on your hub, ST will migrate those devices for you to the installed community driver (What is highlighted in Option 4 from the FAQs).

Please note this will not work for Lan devices.

Also, because we don’t know the entirety of the custom DTH was and what it’s replacement driver is, we cannot guarantee the expirence will be exactly the same (as we haven’t reviewed the code of either and it isn’t in our repo).

When in this situation, I recommend to please check the name of your preferences between the Customer DTH and the Non SmartThings owned Driver. If they are not the same, preferences will not migrate.

I don’t know the previous communication you received, if it’s helpful to you I’d be happy to review it if u send a link.

[junrau]

So how do we create simple virtual devices, like a switch/contact sensor or a switch/presence sensor? Is there a catalog of community developed drivers?

[jkp]

[ST Edge] vEdge Creator: a virtual device generator for end users

Here is an Edge driver that will enable end-users to create virtual devices that run locally on-hub. UPDATED JULY 2022… Features: Supports the following virtual device types: A/C, air quality, alarm, battery, contact, door, fan, garage door, light, lock, momentary button, motion, panic, presence, refrigerator, shade, smoke, switch, temp/humidity, TV, switchlevel/dimmer, thermostat, video camera, water Create any number of virtual devices Easy and fast to use: No coding or CLI required Enables you to create 100% local automations with virtual devices See how many devices you’ve created of a given type (inventory) Devices include additional controls and features beyond what is available through CLI-created virtual devices Several virtual device types include a switch that mirrors cont…

[ST Edge] Virtual Things Edge Driver

Hi, Following @TAustin 's great work on vEdge Creator, I was curious to explore a different approach for creating virtual devices. The driver allows creation of devices one-by-one. Please install “Virtual Things Edge Driver [YG]” How to use After installing the driver, press “Add device” and then “Scan nearby”. This will create “vDev Controller” - virtual devices controller (currently it only creates virtual devices, but does not actually allow to control them). Once the controller is created, enter its detailed view. The user specifies a type of the device to create by choosing “Virtual Thing Type To Create” and presses switch button. The controller will report its status (ready/creating/created) and the name of the device being created. When the device is created the switch g…

And you can also create some of them through CLI.

There is also a virtual calendar which you might find useful in Routines.

Sunrise-Sunset and Calendar functions for edge

New name and version of the driver Zigbee Sunrise and Sunset Mc (Zigbee Calendar Mc) To give it some utility more than a calculation of susrise and sunset with offsets, I have added Calendar functions to this driver, since from time to time someone needs to use it to automate irrigation or other things, that they need to use IFTT for example: Added Capabilities of Date one and two: They allow to make automations for period between dates In order to make equal, greater or lesser comparisons, the chosen format must be an integer number. The format to build a representative and comparable number of a date will be YYYYMMDD, that is, for today 2022, June, 10 it would be: 20220610 I didn’t find another way to enter usable data formant of date, Capability Hour of the day: In this way it c…

[JDRoberts]

@junrau

So how do we create simple virtual devices, like a switch/contact sensor or a switch/presence sensor? Is there a catalog of community developed drivers?

You can find community-created Edge drivers on the quick browse lists in the community – created wiki. There are a couple for virtual devices.

https://thingsthataresmart.wiki/index.php?title=How_to_Quick_Browse_the_Community-Created_SmartApps_Forum_Section#Quick_Browse_Links_for_Edge_Drivers

[Vishlance (vish)]

Any news on HomeAssistant integration? Will that remain?

[nathancu (Nathan Curtis)]

The HomeAssistant Integration is based on API access - not groovy. That’s why it requires a Personal Access Token on the SmartThings developer portal.

So you could in theory use HomeAssistant and NodeRed instead of WebCoRE…

…Just realize while HA itself may be local, the HA integration to ST is a cloud integration (it connects to the ST back end not your local hub) and therefore susceptible to all of the happy fun times with lag all cloud integrations have to deal with.

[infofiend]

Although this has been communicated for some time, now that the end is upon us, I cannot express how disappointing this news is. I’ve created multiple DTHs and Smartapps. No longer. The Rules API is confusing, limited, and simply not up to the task of replacing webcore - which I’ve used with SmartThing to build my entire smarthome around. No longer. I have recommended SmartThings to others for years, and personally set up many of their systems. No longer. I’ve stayed with SmartThings for nearly its entire existence. No longer.

[Shanapadila (Shana Padilla)]

So how do we get additional model numbers of a device added to a fingerprint for a “standard edge driver”. According to IDE … All my Keen vents are listed as: SV02-612-MP-1.3. That does not seem to be included in the standard driver. If every model number has to be listed, then who does that.

at

[GSzabados (Gabor Szabados)]

@SmartThings

All of this platform growth has increased reliability, decreased latency, and reduced the need for data transfer outside of the home environment.

A local API reduces the need the transfer outside of the home, a cloud Rest API does NOT!

[mvevitsis (Matvei Vevitsis)]

My main concern is how rboy/yves will respond as their integrations are paid.

[veonua (Andrew Me)]

I still have color temperature bulbs on the old platform. And I have a Philips led strip on the official Zigbee driver on the old platform.

Will these be converted to Zigbee Edge driver automatically or do I have to do it manually?

[DaWeav]

I have a few devices currently running on the SmartThings Edge Beta drivers. It was previously advised that to get the device on the SmartThings Edge Main production driver, that I would have to delete and re-onboard the device to change it from the SmartThings Edge Beta driver to the SmartThings Edge Main production driver.

Is this still the case?

Or (hopefully) will any Edge devices currently using the SmartThings Edge Beta drivers be migrated to the SmartThings Edge Main production drivers during this migration effort?

Or, can I simply change the devices Edge driver from the SmartThings Edge Beta driver to the SmartThings Edge Main production driver in the SmartThings app?

[Shanapadila (Shana Padilla)]

When and how will smartthings be communicating to the average user who does not follow the blogs or visit this site of the up coming changes? And is the help desk/support teams going to be staffed up for all the "it is not working calls/emails?

[Helder_Rodrigues]

Hi @andresg

I have a doubt.

I’m not a programmer. Will the devices that are connected to the Hub and that are working without Device Handler automatically switch over?

I have, for example, Blinds Controllers (Philio Pan08) that are currently like Z-Wave Window Shade working in the cloud!

At the moment I can edit the device type in groovy.

In the future if I need to remove the device, will I have problems adding it again?

Or is the problem only those who use Device Handler?

Thanks

[johnconstantelo]

@alissa.dornbos , can you help answer my question above?

The End of Groovy Has Arrived

@andresg and @nayelyz , did I read that right? ST is rendering these not supported at all or just supported as a Zigbee Smoke Detector? I have 9 of these and this is quite unexpected. Please let me know. [image] When Halo folded and went out of business and the community requested the DTH code so we could maintain it we were told no, now there’s a sense of urgency to provide this code.