Can you control the device’s on your test account ? They don’t show unresponsive til you try it seems.
So if it works for you Brad with those settings what am I doing wrong ?
Any more info mate ? Really keen to get this going. Can k migrate manually of I decide now to an Aussie server ??
I tried disabling the Alexa skill and re-linked it but it’s still not working. I can’t see what’s different compared with @Brad_ST’s Test…
1 Like
Me too. No luck
I’d happily buy a new hub. But it will take me quite a while to migrate manually . So really hoping there is a tool.
FWIW I have this same issue: I can link ST successfully to a US-based Amazon account, but it fails for my Australian account.
I have opened it as a ticket in the devportal but no response yet. (Ticket 5244 if you have access to that).
With the smart logging it appears there is an error when ST POSTs back to Alexa…the error is “postEventToEndpoint: Error while trying to post event back to Alexa groovyx.net.http.HttpResponse.Exception: Forbidden”.
I don’t see that equivalent error when working against the US-based Amazon account.
The error seems to be whenever ST needs to push an update to Alexa; in response to an Alexa-initiated command or a notification (like a motion event). After the error, it appears like ST believes the user has disabled the skill and all devices show as ‘unresponsive’ in the Alexa app.
I’ve attached a screen shot of the logging for the unsuccessful AU account.
1 Like
Smarthings support said to contact Amazon as errors on their side.
Unfortunately, we will be unable to assist you with that since it looks like a server error on amazon. Please contact Amazon Customer Service: 1 (888) 280-4331. An agent will be happy to assist you with this situation.
I am getting the exact same error after setting it up.
postEventToEndpoint: SKILL_DISABLED_EXCEPTION: The user does not have a valid enablement for your skill.
I am on the phone with amazon now. The service is pretty good even here in Oz!
Update: their team are looking into it and have seen this thread. Hopefully we’ll hear back soon.
3 Likes
I did that via the Alexa app but you only get a couple of lines to describe it before the Submit button gets cut off, at least on a phone! No response so far, I reported it a couple of days ago ( I think, just flown MEL->LHR so slightly confused about days right now…)
1 Like
Curious if you heard anything back yet on this?
This Alexa page describes how to post asynchronous events (such as device state changes) back to Alexa.
It also mentions that the SKILL_DISABLED_EXCEPTION is returned for attempts to call the wrong regional endpoint.
https://developer.amazon.com/docs/smarthome/send-events-to-the-alexa-event-gateway.html#endpoints
Australia is considered part of the “Far East” region…as opposed to North America or Europe/India.
Since the calls work for a US-based account, my suspicion is maybe ST is not posting to the correct endpoint.
Perhaps its posting to the North America region when instead it should be Far East.
I can’t confirm though as the endpoint URL is not logged.
If this is the issue, it would be for ST to investigate/address in their Alexa skill.
1 Like
Nope nothing yet. But not expecting a response for several days.
You’re definitely right about the issue. It should be easy fixed
Still no update. Even followed them up
called up again. they said it was fixed… but it’s not. i have tested it multiple times.
@AndrewD can you see if it’s working for you now?
i’m guessing it won’t
I am seeing same errors:
info Deactivated from client
15:34:23: info postEventToEndpoint: SKILL_DISABLED_EXCEPTION: The user does not have a valid enablement for your skill.
User has disabled skill or removed consent.
15:34:23: debug postEventToEndpoint: Error while trying to post event back to Alexa groovyx.net.http.HttpResponseException: Forbidden
debug Property Change Event level: 15 (source: DEVICE)
edit:
they have escalated it. am told i’ll hear back from the support case manager hopefully.
@Brad_ST i’ve spent probably 3 hours chasing this. It’s getting a bit ridiculous - regardless of which side the error is coming from. the integration has not been setup property for amazon.com.au users.
can you re flag this internally and ask them to follow it up? The amazon team said today they had fixed the issue. But after a bit of push back it was clear it hasn’t been touched. Surely Smartthings has a line to someone at amazon skills team… and can get this sorted faster than I can by being on the phone for hours. Repeating the same issue over.
1 Like
Are you saying you now have the Alexa SmartApp visible in your IDE (previously neither of us did which appeared to be probable number 1), but you getting the above errors still? Or are the errors because there is no SmartApp installed?
I’m not sure why someone at ST can’t just add the SmartApp into our accounts- I’m sure I’ve read of that being done for other SmartApps…
i think there’s a clear domain issue here with .au… but i am indeed getting the exact same errors. No smartapp in my ide still
I actually have a case number now and have been told its been escalated.
With Joel and Paul’s help, we have a developer on our side working with Amazon to resolve this. Sorry for the delay!
4 Likes
Thanks for the update. Much appreciated