Connection Problems for new SmartThings cloud device

[nayelyz (SmartThings Developer Support)]

Welcome to the SmartThings Community, @StevenReiss!

@StevenReiss

First try was to use an oauth server created using express-oauth-server that would authenticate using

So, when you select the ST Schema in “my testing devices”, the app redirects you correctly to the URL you defined as “Authorization URI” in the Developer Workspace (Device Cloud Credentials) which in your case is https://sherpa.cs.brown.edu:3336/oauth/authorize, correct?
After you login with a valid user, do you receive a request in the “Token URI” (https://sherpa.cs.brown.edu:3336/oauth/token)? This is when SmartThings requests an Access Token from your cloud

Please, check this sample where an OAuth server is included for testing purposes and you will be able to see its behavior during the authentication process:

Schema Devices and Custom Capabilities

Creating custom capabilties for schema devices Using the SmartThings CLI and Developer Workspace We are going to create a Cloud Connected Device using Schema and webhooks. Our base device will be a basic switch. The first part of this tutorial will cover create the connector, oAuth server, and adding the Switch to SmartThings. The second part of the tutorial will cover adding a custom capability to this new device. Prerequisites: Samsung Account Developer Workspace Access Developer Mode Enabled Glitch Account Text File Step 1: Remix this Glitch account (connector) Set the values in the .env file using .env-example as a guide. Once the remixed app is up and running copy its URL to your text file. Register the webhook url in SmartThings Developer Workspace and deploy it for t…

@StevenReiss

I can send messages to this address via both GET and POST

This is weird…have you checked if you’re not getting an error like “Forbidden - failed verifySignature”?