Quick question and I apologize if this has already been covered here. Is it possible to change the activation name from smart things to something else? If so how, and are there negative ramifications for doing so? Basically our house has a name and my wife would prefer to address commands that way rather than saying smart things.
Janisary. A very unique name I came up with a long time ago when I first tried to do voice command x10, and essentially ever since anything house related uses that name. Looking forward to when Amazon letās us change to a custom invocation word instead of the 3 they provide. If you are a big Halo person you might recognize the nameā¦ Last hint, I love beesā¦
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
1725
Thatās awesomeā¦ Not many unique namesā¦ We just went with home for nowā¦
Our next home will be our final homeā¦ Just six more years till retirement then we are back to the beachā¦ That one will have a name.
Iāve re-installed twice and Iāve not found this error list in any of the forums. Is there something special I need to be doing since Iām stuck on this newer shard?
Letās start with the basicsā¦First, I assume you have the latest versions: 2.0.8 and 1.1.7 of the Lambda code?
Second, you may want to PM this, but when you go into Settings -> Setup Variables, what are you getting? If the web page with the variables DOES come up, this will all work. The location of the website is determined by your account and is NOT hard codedā¦if you are interested, it is the getApiServerUrl() command. Either way, whatever it gives you is what SmartThings determines is your location and you app probably wouldnāt work if that was screwed up.
Yes, 2.0.8 of the SmartApp and 1.1.7 of the Lambda code are installed and I did enable OAuth in the IDE (Client ID and Client Secret are populated). I just went into the respective consoles to confirm that there wasnāt anything that didnāt get saved, etc. And just to reiterate, Iām performing all of the ST-related tasks on https://graph-na02-useast1.api.smartthings.com/ide because thatās where my hub is and nothing Iāve ever done on the āmainā IDE site has ever worked.
In the ST app on my phone, Iām opening the AskAlexa SmartApp, clicking settings, then āSetup Variables (For Amazon Developer sites)ā, and thatās when I get
Itās so early in the installation process, that Iām not sure what I could have messed up - the smart app is running, so itās installed, the OAuth ID shows up, so itās working. I donāt know how to test the lambda code, but I think I need these variable before it would run anyway.
Access token and Application ID are populated in the Ask Alexa SmartApp, but they do not correspond to the Client ID and Client Secret that show up in OAuth section in the IDE. Do I need to run the Generate new Client ID and Generate New Client Secret links in the IDE?
Clicked New Client ID and New Client Secret, and then for good measure removed and re-installed the smartapp on my phone. Same errors and the Access Token / App ID in the App are still not remotely similar to the Client ID//Client Secret in the IDE.
I have never seen this beforeā¦While support wonāt help you with community developed apps, if something like the IFTTT integration doesnāt work (which also uses OAuth and the location API) then you have a case to get SmartThings to look at thisā¦Very strangeā¦Are there any other apps you have difficulty with? SmartTiles? Have you loaded up my Cloud Interface appā¦it is much easier and will tell you right way if you are having an issue.
For those that are interested in the survey, I am closing it down. I will be releasing āCourtesyā as the first personality, and then Snarky soon after thatā¦Thanks for everyone that participatedā¦I got less than 50 results, which I hope doesnāt mean only 50 people use thisā¦either way, enjoy!
4 Likes
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
1738
Nahā¦ People just donāt like surveys lolā¦
I still think you should publish this to Amazon for access on the Alexa app.
SmartTiles works for me, but itās the ānewā install, and I was reading that they changed some things regarding how OAuth works nowadays, so Iām not sure if that impacts anything.
Your Cloud Interface app does seem to work (It generates URLās without errors), but the Access Token shown in the app doesnāt match either of the Client ID or Client Secret shown in the IDE.