After a long pause I decided to get back into this.
I have a new project created and am hosting a Schema Connector in node, and I also have a simple oauth service running. Both are accessible from the cloud and both are backed by a good cert, verified with SSL Checker.
On my phone I disabled and re-enabled developer mode, because I read somewhere that this can help. I go to add device → partner devices (this is new since the last time I checked) → My Testing Devices. I see my app name in the list, which is good. However every time I click it I ALWAYS get “Couldn’t add device”. “A network or server error occurred. Try again later”.
I see zero traffic to my hosted web services, and I re-double-checked everything I can think of.
Hi, @djarvis8
Currently, there’s an issue in the app when adding new Schema Connectors, you will get this error if your Schema integration is newly added, but you can discover new devices of those already installed.
The engineering team already has a fix and we were told it would be included in the next release of the SmartThings app but we don’t have the exact ETA, it should be soon.
Once we get more info about the release, we’ll let you know.
Hi, @djarvis8
The issue installing a new Schema integration should be solved now, please confirm if you can do it successfully.
Just verify you’re using the latest Android app version (1.8.07.23). Thanks!
Hi, yes. I did get the app update and I was able to get further with adding my schema connector. The rest of the problems are likely on my end. But yes the update seemed to fix that one issue. Thanks!
Did something change on the OAUTH side of things? I re-mix the sample glitch from here Glitch :･ﾟ✧ as specified in the SmartThings docs but all I can ever get is a “Cannot GET /oauth/login” message.
Where are you getting this message? The project you linked belongs to the sample of the Schema Connector, not the one from the OAuth server sample which should have that endpoint configured as mentioned in this step of the tutorial:
Maybe that’s why you get an error when the integration tries to call the OAuth server when you install it for the first time.
Mmm, I don’t know either, it might have been a glitch because recently we implemented that sample again and we didn’t have any issues.
So, we’ll keep an eye on other reports about this just in case.
I did notice there were a few changes in the app.js file in the mock oAuth2 server from a version I had a few months ago. But yeah, I am not sure what the issue was before.
