Repository navigation
Replies: 23 comments 19 replies
|
I concur with this, having the same issue. Have tried the same steps as Cooch069. No log errors appear on scrypted alexa plugin when trying to link. |
|
Same issue here, shows briefly .jp and wont connect to the skill |
|
@nberardi is there another Alexa endpoint url that needs to be added? |
|
I noticed that there was a recent update to the Alexa plugin in Scrypted. I'm still unable to connect. When i sign into my Amazon account via Amazon.com.au and attempt to link this skill its redirecting to alex.amazon.co.jp and failing. |
|
The JP region is correct for Australia, however if it is hard coded to “alex.amazon.co.jp” that seems like a bug. @Cooch069 could you turn on the DEBUG option in the plugin, try again, and copy your logs and attach them? |
|
With Debug Events enabled, enabling the skill produces no Alexa.Authorization/AcceptGrant directive and no Amazon/Alexa request in the plugin log. The plugin only logs tokenInfo is undefined on startup and then asks to reauthenticate. It appears the Amazon linking flow is failing before the request reaches my Scrypted Alexa plugin/Scrypted Cloud instance. I can access my Scrypted server from outside my network using the Scrypted Cloud login. Here is the log. linux x64 #86009 SMP Wed Nov 26 18:29:22 CST 2025 |
|
This is the first part of the URL during the linking process. |
|
I also checked the Scrypted Cloud plugin logs from the same attempt. Cloud appears to start and route normally: scrypted cloud server listening on 46323 When I retry skill linking, the Cloud log only shows browser/login traffic and core websocket/polling endpoints, for example: /login There is no Alexa-specific callback, no AcceptGrant, and no request that appears to be coming from Amazon/Alexa. So both the Alexa plugin log and Cloud plugin log suggest that the Amazon account-linking flow is not reaching Scrypted Cloud/Alexa plugin at all. |
|
linux x64 #86009 SMP Wed Nov 26 18:29:22 CST 2025 |
|
I'm not sure if this is the right log, I am new to scrypted but this is what it shows in the alexa log and the home assistant scrypted add on log if this helps at all, i have no debug option in the alexa plugin that i can see using hassio add on ######################## HA log unhandled rejection of RPC Result RPCResultError: RpcPeer has been killed (apply) undefined I also tried completely uninstalling and reinstalling the Scrypted Cloud plugin as well |
|
@Cooch069 by any chance if you roll back the version of Alexa plugin does it start working again? |
|
Yes, I have already tested several older versions of the Alexa plugin and the issue persists. For network configuration, I do run a reverse proxy on my Synology NAS, but it is only used for resolving hostnames and providing access to other services on my local network. Scrypted itself is not behind the reverse proxy. The Scrypted server is accessible directly and has its own port forwarding configured. I can access it successfully both from inside my local network and from external networks, so the server appears to be reachable without going through the Synology reverse proxy. With DEBUG enabled, I still do not see any Alexa
which makes me wonder if there is a problem with the stored authentication state or account-linking process before Amazon ever reaches the plugin. |
|
Im still having this issue too. Has anybody successfully added the alexa skill? |
|
What I've worked out so far is that if I change my amazon account country to US (Content and devices -> Preferences -> Country/Region Settings), i'm then able to link the skill. After changing the country back to AUS, the skill stops working. I prefer not to keep the country as US for obvious reasons. Hopefully there's a solution soon :( |
|
@koush we will likely need to pull logs from your server account around Headers :status: 400
content-type: application/json
content-length: 251
server: Server
date: Sat, 18 Jul 2026 18:31:08 GMT
strict-transport-security: max-age=0; includeSubDomains;
x-amz-rid: 5TF7ENYPY5TN6QPYVSZC
x-amzn-requestid: 28383880-4d06-441e-865b-2d975c38ec0e
access-control-allow-origin: *
cache-control: no-cache, no-store
access-control-expose-headers: x-amzn-RequestId,x-amzn-ErrorType,x-amzn-ErrorMessage,Date,smithy-protocol
vary: Accept-Encoding,User-Agent
x-cache: Error from cloudfront
via: 1.1 56bbab08f5381e532e122035df26be58.cloudfront.net (CloudFront)
x-amz-cf-pop: IAD61-P13
x-amz-cf-id: svXgwcJI83lXZnqnkpu6wnKRSnozes7ctOwfxcC8mi-G2ZgKY6FxVw==Body {
"message": {
"description": "Please try again later.",
"title": "Unable to link the skill at this time."
},
"skill": {
"asin": "B09WHHD9VN",
"id": "amzn1.ask.skill.ff879ff4-881e-4a4d-9913-305b4857ac93",
"stage": "LIVE",
"status": "PUBLISHED",
"types": ["SMART_HOME"]
}
} |
|
Anybody got this working or have a workaround? |
|
I looked at the Alexa backend service I provide and I have not seen anything related to australia not being supported |
|
Hi, as a workaround, if anyone is keen to run their own backend on AWS (Serverless with Cognito+Lambda) and (private) Alexa Skill, I thought to share this repo I created, with my AI agent, on a weekend 😉: |
|
Ooh yes, this would be nice to have fixed. I've messed about with it for far too long. Glad it's not just me. |
|
Have I missed something somewhere? Both the issues have been closed as completed. |
|
fixed. was an aws lambda config issue in different regions. |
|
Good news! Works for me too. Thanks for the fix. |
|
All working again. Thank you for fixing this and thanks mehrdadgit for investigating the linking issue. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
The Scrypted Alexa skill has been unable to link for approximately 6 weeks on an Australian Amazon account. During the linking process, the OAuth flow briefly shows
alexa.amazon.co.jp(Japan endpoint) before failing — which seems incorrect for an AU account and may point to a regional routing issue on the skill's OAuth configuration.Environment
What happens
alex.amazon.co.jpin the URLWhat I've already ruled out
curl https://manage.scrypted.appfrom inside the Docker container returns in ~0.54s (no slowdown)Key detail
The appearance of
amazon.co.jp(Japan) in the OAuth redirect URL during linking seems like the wrong regional endpoint is being used for AU accounts. This setup worked flawlessly before and stopped working approximately 6 weeks ago without any changes on my end.Question
Has something changed in the Scrypted Cloud OAuth configuration for non-US regions? Is the AU marketplace routing through the correct Amazon endpoint? Happy to provide any additional logs or diagnostics.
All reactions