Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use plugin with Australian Registered devices #1170

Open
ksn-systems opened this issue May 7, 2024 · 5 comments
Open

Use plugin with Australian Registered devices #1170

ksn-systems opened this issue May 7, 2024 · 5 comments
Labels
question Further information is requested

Comments

@ksn-systems
Copy link

Check if the Bug maybe is with Amazon
The adapter is using the same API as the Alexa mobile App. This means:

  • If you can not do this what you want with the App then the Adapter also can not do it!
  • Also if the App can do it please test if the same effect then the bug also happens with the App (e.g. a speak command do not work on a certain device ... can you do a speak via Alexa App? If not - Amazon problem!)

Describe the bug
A clear and concise description of what the bug is. Especially describe what you verified using the Alexa App (see above).

Trying to use the plugin with an Alexa device that is registered on amazon.com.au

To Reproduce
Steps to reproduce the behavior:

Install plugin
try and get cookie
adaptor fails to connect to any devices

set endpoint to https://alexa.amazon.com.au (assuming this is the correct endpoint)

same result

Expected behavior
A clear and concise description of what you expected to happen.

Plugin should start and my alexa should be visible in Objects on iobroker

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

  • Adapter version: 3.26.5
  • JS-Controller version: 5.0.19
  • Node version: 18.20.2
  • Operating system: ubuntu

Linux iobroker 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Additional context
Add any other context about the problem here.

@Apollon77
Copy link
Owner

Apollon77 commented May 8, 2024

In theory the following should help:

  • go toinstance settings
  • there is one tab that allows to override special parameters
  • enter en-AU (should be correct locale right? ... in fact use the locale which is correct for australian english) in the accepted-language field
  • enter "amazon.com.au" in the "custom cookie amazon URL"

then restart the adapter and try to get a cookie. Does that work?

Infact comparable to how it worked for US in #1148

@ksn-systems
Copy link
Author

Hi

Thanks for getting back to me.

No luck, tried both combinations above to no avail.

I could get a cookie adding amazon.com.au and en-AU to the config but the adaptor would fail to start.

@Apollon77
Copy link
Owner

"Fail to start"? mean? Logs? Details?

@ksn-systems
Copy link
Author

Here is a complete cycle

host.iobroker 2024-05-30 05:51:55.835 info Do not restart adapter system.adapter.alexa2.0 because desired by instance
host.iobroker 2024-05-30 05:51:55.834 info instance system.adapter.alexa2.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
alexa2.0 2024-05-30 05:51:55.317 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
alexa2.0 2024-05-30 05:51:54.317 error Adapter seems to have issues and crashed three times in a row. Disabling!! Please start again and check logs.
alexa2.0 2024-05-30 05:51:54.313 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
alexa2.0 2024-05-30 05:51:54.298 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v18.20.3, js-controller: 5.0.19
host.iobroker 2024-05-30 05:51:53.769 info instance system.adapter.alexa2.0 started with pid 162878
host.iobroker 2024-05-30 05:51:51.241 info instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
alexa2.0 2024-05-30 05:51:51.220 info terminating
host.iobroker 2024-05-30 05:51:50.756 info stopInstance system.adapter.alexa2.0 send kill signal
alexa2.0 2024-05-30 05:51:50.720 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
alexa2.0 2024-05-30 05:51:50.719 info terminating
alexa2.0 2024-05-30 05:51:50.718 info Got terminate signal TERMINATE_YOURSELF
host.iobroker 2024-05-30 05:51:50.713 info stopInstance system.adapter.alexa2.0 (force=false, process=true)
alexa2.0 2024-05-30 05:51:50.698 info Update cookie in adapter configuration ... restarting ...
alexa2.0 2024-05-30 05:51:45.129 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged.
alexa2.0 2024-05-30 05:51:45.113 info starting. Version 3.26.5 in /opt/iobroker/node_modules/iobroker.alexa2, node: v18.20.3, js-controller: 5.0.19
host.iobroker 2024-05-30 05:51:44.559 info instance system.adapter.alexa2.0 started with pid 162860
host.iobroker 2024-05-30 05:51:44.544 info "system.adapter.alexa2.0" enabled

@Apollon77
Copy link
Owner

Pleas enable debug logging: Instances, enable export mode, expand alexa2 instance, set Loglevel to "debug". adapter restarts ... grab log from logfile on disk in /opt/iobroker/log/...

@Apollon77 Apollon77 added the question Further information is requested label May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants