Good afternoon.
I am facing issues with adding a test device to my SmartThings app.
I have followed the instructions on the official Samsung resources, but what I have faced so far is the following:
The interface of the app is different from the official guide and I do not see the “My Testing Devices” button when trying to add a device.
The official QR code generation tool in fact creates a link which eventually opens the SmartThings app and immediately crashes it.
Every other step that was described on the official resources and forums - didn’t help and I still do not see the “My Testing Devices” button.
Please advise me on the next steps as I have tried every single option and it didn’t work out
Thank you
Hi, @Pavel_S
The “my testing devices” option appears in the “Partner devices” section of “add device”. Remember you need to enable the developer mode in the SmartThings app for it to appear.Here’s a screenshot of how it looks like:
You were looking alphabetically at the “M” section, right? The option “My testing devices” is at the top, in the “Recommendations” section. Is it also missing there?
There isn’t a “My testing devices” anywhere, we checked. Is this a known issue and is there workaround? We can’t move forward until this is resolved. Please help.
Hi, @mv4
There’s only a known issue in iOS where new users cannot enable the developer mode, but I haven’t heard that the “my testing devices” option is missing.
Please, provide the following information:
Disable the developer mode and restart the app as it asks you to.
Start recording your phone’s screen and show how you enable the developer mode, go to add devices > partner devices and the “my testing devices” option is missing
Then, collect the ST app’s logs
Go to Menu > Gear Icon > About SmartThings
Tap the SmartThings logo 10 times.
This will open the developer’s space > tap ‘report a problem’
This will generate a log file which we need you to send to build@smartthings.com
This is for the engineering team to compare what you see on the screen and the log info.
@nayelyz Without wishing to derail this thread, do you happen to know what triggers the appearance of ‘My Testing Devices’? My interest is in Webhook SmartApps for creating devices and those disappeared from the Developer Workspace quite some time ago. I was kind of hoping creating an installed app with the DEVICE classification would be enough but clearly not.
As I understand, it should appear only by enabling the “Developer Mode” but I could be wrong.
So, you also don’t see this option even though you have enabled the Developer Mode?
Do you have any device integration “deployed to test”? As I remember, we’ve seen that we can create apps through the API but cannot deploy them to test to make them appear in the app.
Also, something curious about this case is that the app shows “empty_devices_ids” instead of a developer ID on the page below. In my case, the organization ID appears next to the developer ID:
I do have a SmartApp deployed to test. By changing the classifications of the app I can make the installed instances appear in various places in the app, such as on the Routines page, Life page and in the Linked Services. I can’t remember if I tried Labs. It is also possible to specify DEVICE which supposedly lists it on the Devices page somehow.
The Developer Workspace used to explicitly support SmartApps as an alternative to using a schema for C2C devices. However that option disappeared months ago and I am wondering if just like the automation apps are ‘deployed to test’, they also did something with the device catalogues.
Yes, that is right. I won’t quote the URL the Developer Workspace uses to self-publish but it includes the project ID from the Developer Workspace so it is all rather incestuous. I wouldn’t be surprised if all it really did was add a private entry to the apps catalogue so the app could find it but I’ve never seen the private catalogues populated.
after sending the logs and a video recording to Support, we still don’t have a workable solution, or an explanation as to what might have caused the problem. We tried creating a brand new developer account, but that account has the same problem.
Since we’ve been blocked from testing for several weeks now, is there a way for you to escalate this internally?
Hi, @mv4, @Pavel_S
I already escalated the corresponding ticket of this issue, the engineering team replied yesterday saying the timestamp of the logs and the one in the screen recording doesn’t match.
In the video, we see it’s 12:19 but in the logs, there are only events from 13:09 to 13:10, did you collect the app logs immediately after the screen recording?
Also, where did you sign up (through the Developer Workspace, or another SmartThings tool)?
ok, I see you have only one project deployed to test but it’s direct-connected. Could you deploy to test the other one “Spartan Cloud”, please? This is just to confirm that it’s not related to the type of project that we have deployed.
Hi, @Pavel_S, @mv4
I’m reaching out here because I sent an email and didn’t get a response. We would like to know if you’ll continue with the investigation.
I’ll include my email here as well:
