Open ksn-systems opened 4 months ago
In theory the following should help:
then restart the adapter and try to get a cookie. Does that work?
Infact comparable to how it worked for US in https://github.com/Apollon77/ioBroker.alexa2/issues/1148
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.
"Fail to start"? mean? Logs? Details?
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
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/...
Check if the Bug maybe is with Amazon
The adapter is using the same API as the Alexa mobile App. This means:
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:
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.