Marking old architecture topics?

Meta
8

I’m starting to mark some of the smartapp topics. If you are the original author and want it marked a different way, just go ahead. I’m just marking them as a convenience so fewer community members get confused. :thinking:

Here’s what I’m doing so far:

  1. If it’s a fairly simple groovy smartapp and it’s also using Groovy DTHs and it’s either quite old or has been dormant for a while. I’m just marking it OBSOLETE.

  2. If the main thing that’s being shared is a script that runs on another device, like python or something, and the integration through smartthings is just done with a virtual device, then I’m marking it NEEDS UPDATING because the main issue is that the instructions tell people to create a virtual device through the IDE now they’ll need to use one of the new architecture methods.

If you are one of these authors, here’s the link to the new 2023 FAQ on creating virtual devices:

FAQ: Creating Virtual Devices Without the IDE (2023)

  1. if the author is someone like @rboy who has already told the community that they are working on versions for the new architecture, I’m not changing anything on the title for now. I assume that that developer will eventually update the first post in that thread, or close it themselves and replace it with a new thread.

  2. if the author is someone like @heythisisnate (for Konnected.io ) who has already published the new integration method hopefully they will update the first post in the thread, but I will try to add a linking post at the end if they haven’t done that yet. I may Mark these NEWER VERSION AVAILABLE when that’s appropriate.

Again, this will be a slow process, so if there are any smartapp authors who want to go ahead and mark their own threads, please do so.

3 Likes