Comments (8)
jpsim
commented on September 5, 2024
1
Your latest changes in v0.20b fixed everything for me! ❤️
Here's are slimmed down -login logs with curl -v:
$ ./alexa_remote_control.sh -login
cookie does not exist. logging in ...
> POST /ap/exchangetoken/cookies HTTP/1.1
> Host: api.amazon.com
< HTTP/1.1 200 OK
> GET /api/language HTTP/1.1
> Host: pitangui.amazon.com
< HTTP/1.1 200 OK
> GET /templates/oobe/d-device-pick.handlebars HTTP/1.1
> Host: pitangui.amazon.com
< HTTP/1.1 404 Not Found
> GET /api/bootstrap?version=0 HTTP/1.1
> Host: pitangui.amazon.com
< HTTP/1.1 200 OK
device list does not exist. downloading ...
> GET /api/devices-v2/device?cached=false HTTP/1.1
> Host: pitangui.amazon.com
< HTTP/1.1 200 OK
logged in
I think the 404 here is expected.
And then sending a command:
$ ./alexa_remote_control.sh -d 'Kitchen Echo' -e play
> GET /api/bootstrap?version=0 HTTP/1.1
> Host: pitangui.amazon.com
< HTTP/1.1 200 OK
sending cmd:{"type":"PlayCommand"} to dev:Kitchen Echo type:<REDCATED> serial:<REDACTED> customerid:<REDACTED>
> POST /api/np/command?deviceSerialNumber=<REDACTED>&deviceType=<REDCATED> HTTP/1.1
> Host: pitangui.amazon.com
< HTTP/1.1 200 OK
{}
Thanks for all your quick help on this, I was not expecting this level of hands-on assistance 🙌
from alexa-remote-control.
adn77
commented on September 5, 2024
I will try to have a look at this. Otherwise I strongly suggest you take a look at the modern device registration/refresh_token login.
That way you won't have to expose your password anywhere.
https://blog.loetzimmer.de/2021/09/alexa-remote-control-shell-script.html
from alexa-remote-control.
jpsim
commented on September 5, 2024
Thanks for the suggestions. Following those steps, I can authenticate enough to fetch the list of devices, but attempts to send commands fail with 401 unauthorized errors.
When I run the -login command, I get this error.
ERROR: cookie retrieval with refresh_token didn't work
Redacted logs passing -v to cURL
Logs
$ ./alexa_remote_control.sh -login
cookie does not exist. logging in ...
* Trying 52.46.149.20...
* TCP_NODELAY set
* Connected to api.amazon.com (52.46.149.20) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [225 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [104 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4050 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=api.amazon.com
* start date: Dec 29 00:00:00 2020 GMT
* expire date: Dec 14 23:59:59 2021 GMT
* subjectAltName: host "api.amazon.com" matched cert's "api.amazon.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
* SSL certificate verify ok.
> POST /ap/exchangetoken/cookies HTTP/1.1
> Host: api.amazon.com
> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
> Accept: */*
> Accept-Encoding: deflate, gzip
> Referer:
> x-amzn-identity-auth-domain: api.amazon.com
> Content-Length: 480
> Content-Type: application/x-www-form-urlencoded
>
} [480 bytes data]
* upload completely sent off: 480 out of 480 bytes
< HTTP/1.1 200 OK
< Server: Server
< Date: Tue, 05 Oct 2021 14:50:22 GMT
< Content-Type: application/json;charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< x-amz-rid: E40VDZANX7YCDG86R9CS
< X-XSS-Protection: 1
< X-Content-Type-Options: nosniff
< X-Frame-Options: sameorigin
< x-ua-compatible: IE=edge
< Pragma: No-cache
< Cache-Control: max-age=0, no-cache, no-store, must-revalidate
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Vary: Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
< Permissions-Policy: interest-cohort=()
<
{ [1168 bytes data]
* Connection #0 to host api.amazon.com left intact
* Closing connection 0
ERROR: cookie retrieval with refresh_token didn't work
$ rm /tmp/.alexa.*
$ ./alexa_remote_control.sh -login
cookie does not exist. logging in ...
* Trying 209.54.177.117...
* TCP_NODELAY set
* Connected to api.amazon.com (209.54.177.117) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [225 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [104 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4050 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=Washington; L=Seattle; O=Amazon.com, Inc.; CN=api.amazon.com
* start date: Dec 29 00:00:00 2020 GMT
* expire date: Dec 14 23:59:59 2021 GMT
* subjectAltName: host "api.amazon.com" matched cert's "api.amazon.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
* SSL certificate verify ok.
> POST /ap/exchangetoken/cookies HTTP/1.1
> Host: api.amazon.com
> User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
> Accept: */*
> Accept-Encoding: deflate, gzip
> Referer:
> x-amzn-identity-auth-domain: api.amazon.com
> Content-Length: 480
> Content-Type: application/x-www-form-urlencoded
>
} [480 bytes data]
* upload completely sent off: 480 out of 480 bytes
< HTTP/1.1 200 OK
< Server: Server
< Date: Tue, 05 Oct 2021 14:51:16 GMT
< Content-Type: application/json;charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< x-amz-rid: 22VC3APCQ07AS7E6W9B2
< X-XSS-Protection: 1
< X-Content-Type-Options: nosniff
< X-Frame-Options: sameorigin
< x-ua-compatible: IE=edge
< Pragma: No-cache
< Cache-Control: max-age=0, no-cache, no-store, must-revalidate
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Vary: Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
< Permissions-Policy: interest-cohort=()
<
{ [1168 bytes data]
* Connection #0 to host api.amazon.com left intact
* Closing connection 0
ERROR: cookie retrieval with refresh_token didn't work
$ ./alexa_remote_control.sh -login
* Trying 205.251.251.214...
* TCP_NODELAY set
* Connected to pitangui.amazon.com (205.251.251.214) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [230 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [91 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4732 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=pitangui.amazon.com
* start date: Jul 13 00:00:00 2021 GMT
* expire date: Jul 12 23:59:59 2022 GMT
* subjectAltName: host "pitangui.amazon.com" matched cert's "pitangui.amazon.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
* SSL certificate verify ok.
> GET /api/bootstrap?version=0 HTTP/1.1
> Host: pitangui.amazon.com
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:1.0) bash-script/1.0
> Accept: */*
> Accept-Encoding: deflate, gzip
> Referer:
> Cookie: sess-at-main="<REDACTED>"; session-id=<REDACTED>; ubid-main=<REDACTED>; at-main="<REDACTED>"; x-main="<REDACTED>"
> DNT: 1
> Connection: keep-alive
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 141
< Connection: keep-alive
< Server: Server
< Date: Tue, 05 Oct 2021 14:51:17 GMT
< x-amz-rid: BMXCF5B20GNJXX1QNPTF
< x-amzn-RequestId: 508849e4-305e-4a09-8403-ce815d591de8
< Content-Encoding: deflate
< x-amzn-ActionTrace: amzn1.tr.63582fb8-39ee-11e6-bea0-0a5b2c880200.872.P4OEdc.DvIkgr
< Vary: Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
< Permissions-Policy: interest-cohort=()
< X-Cache: Miss from cloudfront
< Via: 1.1 144825e0e5f4523d1f7ce8c9b62cd909.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: YUL62-C2
< X-Amz-Cf-Id: BGv3gBo0SO8EX7iimsRv_fhEnFET1eBEitakwsQOKFnalpC5ahNlEQ==
<
{ [141 bytes data]
* Connection #0 to host pitangui.amazon.com left intact
* Closing connection 0
device list does not exist. downloading ...
* Trying 205.251.251.214...
* TCP_NODELAY set
* Connected to pitangui.amazon.com (205.251.251.214) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [230 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [91 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4732 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=pitangui.amazon.com
* start date: Jul 13 00:00:00 2021 GMT
* expire date: Jul 12 23:59:59 2022 GMT
* subjectAltName: host "pitangui.amazon.com" matched cert's "pitangui.amazon.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
* SSL certificate verify ok.
> GET /api/devices-v2/device?cached=false HTTP/1.1
> Host: pitangui.amazon.com
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:1.0) bash-script/1.0
> Accept: */*
> Accept-Encoding: deflate, gzip
> Cookie: sess-at-main="<REDACTED>"; session-id=<REDACTED>; ubid-main=<REDACTED>; at-main="<REDACTED>"; x-main="<REDACTED>"
> DNT: 1
> Connection: keep-alive
> Content-Type: application/json; charset=UTF-8
> Referer: https://alexa.amazon.com/spa/index.html
> Origin: https://alexa.amazon.com
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 1504
< Connection: keep-alive
< Server: Server
< Date: Tue, 05 Oct 2021 14:51:18 GMT
< x-amz-rid: 1VHX92Q4KGWVY6NDPZEH
* Added cookie csrf="-167860349" for domain amazon.com, path /, expire 1948978278
< Set-Cookie: csrf=-167860349; expires=Sun, 05-Oct-2031 14:51:18 GMT; Domain=.amazon.com; Path=/
< x-amzn-RequestId: 59a2054d-83fb-46c0-acd6-fdaf9520b3d4
< Access-Control-Allow-Origin: https://alexa.amazon.com
< Content-Encoding: deflate
< Access-Control-Expose-Headers: x-amzn-dat-gui-client-upgrade,X-Amzn-Error,loginUrl,X-Amzn-RequestId,x-amzn-alt-domain,Date,Location
< Access-Control-Allow-Credentials: true
< Vary: Origin,Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
< Permissions-Policy: interest-cohort=()
< X-Cache: Miss from cloudfront
< Via: 1.1 c83536c4e12f4a229fa27266fc5fdd56.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: YUL62-C2
< X-Amz-Cf-Id: QB-TsnqeR1Gxh8BONmaPUoMLCawOdU9cANsf3vWP-C5QMjqob6KO5A==
<
{ [488 bytes data]
* Connection #0 to host pitangui.amazon.com left intact
* Closing connection 0
logged in
$ ./alexa_remote_control.sh -d ALL -e pause
* Trying 205.251.251.214...
* TCP_NODELAY set
* Connected to pitangui.amazon.com (205.251.251.214) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [230 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [91 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4732 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=pitangui.amazon.com
* start date: Jul 13 00:00:00 2021 GMT
* expire date: Jul 12 23:59:59 2022 GMT
* subjectAltName: host "pitangui.amazon.com" matched cert's "pitangui.amazon.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
* SSL certificate verify ok.
> GET /api/bootstrap?version=0 HTTP/1.1
> Host: pitangui.amazon.com
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:1.0) bash-script/1.0
> Accept: */*
> Accept-Encoding: deflate, gzip
> Referer:
> Cookie: sess-at-main="<REDACTED>"; session-id=<REDACTED>; ubid-main=<REDACTED>; at-main="<REDACTED>"; x-main="<REDACTED>"
> DNT: 1
> Connection: keep-alive
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 141
< Connection: keep-alive
< Server: Server
< Date: Tue, 05 Oct 2021 14:51:28 GMT
< x-amz-rid: 1KPS180278VWWE9K5HDR
< x-amzn-RequestId: 3dcb0e4f-5f5c-41e9-97f5-8d9aa5b0e4ab
< Content-Encoding: deflate
< Vary: Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
< Permissions-Policy: interest-cohort=()
< X-Cache: Miss from cloudfront
< Via: 1.1 0df778cadb5eaa000de4f1d7838b16e1.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: YUL62-C2
< X-Amz-Cf-Id: qj_s9PRwFkhr9UlCCm-LacoO8ANB2ewbXaqX41qZNihfS0ylUDXcyA==
<
{ [88 bytes data]
* Connection #0 to host pitangui.amazon.com left intact
* Closing connection 0
sending cmd:{"type":"PauseCommand"} to dev:Kitchen Echo type:<REDACTED> serial:<REDACTED> customerid:<REDACTED>
* Trying 205.251.251.214...
* TCP_NODELAY set
* Connected to pitangui.amazon.com (205.251.251.214) port 443 (#0)
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=pitangui.amazon.com
* start date: Jul 13 00:00:00 2021 GMT
* expire date: Jul 12 23:59:59 2022 GMT
* subjectAltName: host "pitangui.amazon.com" matched cert's "pitangui.amazon.com"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global CA G2
* SSL certificate verify ok.
> POST /api/np/command?deviceSerialNumber=<REDACTED>&deviceType=<REDACTED> HTTP/1.1
> Host: pitangui.amazon.com
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:1.0) bash-script/1.0
> Accept: */*
> Accept-Encoding: deflate, gzip
> Cookie: sess-at-main="<REDACTED>"; session-id=<REDACTED>; ubid-main=<REDACTED>; at-main="<REDACTED>"; x-main="<REDACTED>"
> DNT: 1
> Connection: keep-alive
> Content-Type: application/json; charset=UTF-8
> Referer: https://alexa.amazon.com/spa/index.html
> Origin: https://alexa.amazon.com
> Content-Length: 23
>
* upload completely sent off: 23 out of 23 bytes
< HTTP/1.1 401 Unauthorized
< Content-Length: 0
< Connection: keep-alive
< Server: Server
< Date: Tue, 05 Oct 2021 14:51:28 GMT
< x-amz-rid: KMBN6RR64BW6VM3TCKWT
< x-amzn-RequestId: 4cf2bf30-9021-45ac-8f37-bcf72eb09ebe
< Vary: Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
< Permissions-Policy: interest-cohort=()
< X-Cache: Error from cloudfront
< Via: 1.1 18b0fca4845f3542d7f0566683e26627.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: YUL62-C2
< X-Amz-Cf-Id: 7DPGYxpl1Da5putCrviR2BW7it5m4Q1DB-8O94Nx34HRZGM2qHbCtg==
<
* Connection #0 to host pitangui.amazon.com left intact
* Closing connection 0
So it seems that the first -login command fails, producing a /tmp/.alexa.cookie value that looks like this:
.amazon.com TRUE / TRUE 2137924610 session-id <REDACTED>
.amazon.com TRUE / TRUE 2137924610 ubid-main <REDACTED>
.amazon.com TRUE / TRUE 2137924610 x-main "<REDACTED>"
#HttpOnly_.amazon.com TRUE / TRUE 1633521410 at-main "<REDACTED>"
#HttpOnly_.amazon.com TRUE / TRUE 1633521410 sess-at-main "<REDACTED>"
Which doesn't have the at-acbde that's expected.
If I run -login again, it can successfully acquire the Alexa devices tied to my account, producing a /tmp/.alexa.devicelist.txt value that looks like this:
Kitchen Echo=<REDACTED>=<REDACTED>=ECHO
However, attempting to send commands results in 401 unauthorized errors.
Thanks again for your help. I'll keep digging on my end to see if I can get it to work.
from alexa-remote-control.
adn77
commented on September 5, 2024
@jpsim the default Amazon domain for alexa-cookie-cli is amazon.de. Did you run the program with your local domain?
from alexa-remote-control.
jpsim
commented on September 5, 2024
Did you run the program with your local domain?
Yes I ran it with ./alexa-cookie-cli-macos-x64 -p amazon.com -L en-US -a en_US, which matches my changes to alexa_remote_control.sh
from alexa-remote-control.
adn77
commented on September 5, 2024
perfect! maybe my assumption about the cookie naming is wrong. Looks like you're getting a cookie different from my German one.
Would you mind posting a redacted version of your /tmp/.alexa.cookie.json which you get running the first -login
from alexa-remote-control.
adn77
commented on September 5, 2024
I updated https://github.com/adn77/alexa-remote-control/blob/master/alexa_remote_control.sh in respect to the different cookie names.
I still don't understand why this endpoint /api/np/command would give you a 401 when /api/devices-v2/device works... maybe we're on to something ;)
from alexa-remote-control.
Korki67
commented on September 5, 2024
Dear Alex, dear all,
I used the refresh_token on win64. I could login to Amazon through 8080. Output was:
Error: You can try to get the cookie manually by opening http://localhost:8080/ with your browser. / null
I tried to re-open the browser on 8080 but it was just waiting for ever ... In line after the error, I got the token anyway:
Atnr|Abcd and so on ....
So I copied all incl. the "Atnr|" into the script. Didn't work. I added my email and my password, still not working.
I also tried the refresh token without the "Atnr|" without success. This is output of alexa_remote_contro.sh -a or -login:
cookie expired, logging in again ...
ERROR: cookie retrieval with refresh_token didn't work
I would appreciate any proposal how to get it working
Regards,
Horst
from alexa-remote-control.
Related Issues (20)
- how to use "sound:<soundeffect_name>" HOT 4
- Tunein Jingle HOT 8
- "Phantom" device, how to remove?
- Seems answer from "-lastalexa" is changed by Amazon HOT 2
- 20220617 - "Strange" REFRESH_TOKEN generated by alexa-cookie-cli HOT 2
- Trouble Installing HOT 1
- setting default device to: ERROR: unknown device dev: HOT 10
- <InternalFailure/> from Play & Pause // parse error from jq? HOT 6
- Multiple errors "date: invalid date" HOT 14
- Can't get the script to speak HOT 5
- Old Linux Distri with jq 1.4 and curl 7.38 script error with solution ;-)
- Initial login page has changed HOT 2
- Failed writing body HOT 2
- ERROR: cookie retrieval with refresh_token didn't work HOT 2
- Error -lastalexa and -last command HOT 20
- Login procedure does not work anymore (even with new uri) HOT 2
- alexa_remote_control.sh dosn't recieve a cookie anymore... HOT 2
- Return code for commands given to alexa-remote-control HOT 1
- no idea how to use it
- ERROR: no CSRF cookie received HOT 21
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from alexa-remote-control.