SmartApps changes for August 2025

Developer Programs Support
1

Deprecation Notice: Cloud integrations in Developer Workspace

Cloud integrations through the Developer Workspace will be deprecated on August 4th, 2025. Migrate your integration to the new Schema Cloud Connector to ensure seamless operation. For migration instructions, visit the Developer Documentation. If you have any questions, contact us at partners@smartthings.com.

and

Automations are available for self-use only in the SmartThings app. Publishing your automation to other SmartThings users is not currently available. If you have further questions, please contact support.

Does this mean that advanced automations via webhooks are being discontinued, and we must rely solely on rules?

2

I think they are telling us what we already know, which is that Webhook and Lambda SmartApps can currently only be made available to the user’s Location. That’s actually fine by me.

Not only that but it seems we are still lumbered with the ridiculous ‘publish to test’ and installing/updating via the mobile app so the Developer Workspace won’t be put out of its, and our, misery just yet. That’s not fine by me as we need a more open solution so we can develop via the API.

I noticed that cloud integrations using SmartApps seem to have largely disappeared off the face of the earth.

1 Like
3

Tagging @nayelyz @Itati

4

Does this make Automation Engines like Sharp Tools irrelevant?

5

Hi, @veonua
This notice is referring to Schema Integrations. By the way, the meaning of them being “deprecated” is that we won’t be able to create new projects or edit the existing ones from the Developer Workspace. Instead, we’ll have to use the Console or CLI (API), but their functionality won’t be affected.

About SmartApps, that legend about self-use has been present for a long time; meaning that the purpose of this kind of integration isn’t to be shared with others.
That’s not the case for API_ONLY type apps (OAuth Integrations) which we strongly suggest to use instead. You can authorize their access to the user’s location, and depending on the authorized scopes, you’ll be able to perform various actions, such as sending commands to devices, creating rules, and changing location modes.

Since you seem concerned about SmartApps, I would like to take a moment to hear about that. Could you please let us know if you have this type of integration in your ecosystem and its purpose?

6

Hi @nayelyz, thank you for the clarification.

To give some context on my concerns, my main frustration is actually with the Rules Engine and how limited it currently is. It lacks what I would consider very basic functionality. For example, I’d like to toggle curtains, locks, or even restore an AC to its previous state with a single button — this is currently not possible.

In some cases, I have no idea why rules fail to trigger. There are no tools to debug or trace what happened. One example: I have a rule that should lock the storage door 5 minutes after it’s closed, but I often find it left unlocked for hours. What should I do in such cases?

I really appreciate the help from Mariano, who added support for my favorite “dimmed light after 10 PM” mode to the driver—otherwise I would have needed to create 3–4 separate rules per light to achieve the same result.

Finally, I’m helping to manage homes for my parents and sister as well, so the “self-use only” model doesn’t work for me. I need a scalable way to manage and share these setups.

Would love to hear if there are any plans to provide better tools for rule setup, visibility, and debugging.

Thanks again!