bbindreiter / node-red-contrib-alexa-remote2-applestrudel

Node-Red Nodes for interacting with Alexa
https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel
MIT License
74 stars 20 forks source link

Set up process on iOS (iPad) opens the Alexa app via port 3456? #154

Closed nodecentral closed 6 months ago

nodecentral commented 8 months ago

Hi

Following the set up instructions, when I go to the node red IP http://192.168.1.134:3456/ via the browser - it opens a page asking me to go to the IOS Alexa app ? Is that expected ?

IMG_3720

Matten-Matten commented 8 months ago

Same issue #143

Matten-Matten commented 8 months ago

By default the settings say localhost, this will have to be changed to 127.0.0.1 in the future...

nodecentral commented 8 months ago

Hi, I’m not sure that change will help me?

I read the other thread and I’m running node-red on docker under the host, so it doesn’t have its own IP, and entering either local host or 127.0.0.1 just gives me an error.. but when I access the :3456 port using the host IP which 192.168.1.134 (:1888 for node red, :3456 for this add-on) it always prompts me to opening of the Alexa app.

I assume this is due to how iOS handles calls to the redirected Amazon Alexa url, can you share the full url that’s supposed to be opened when I go to port 3456 ?

nodecentral commented 8 months ago

Not sure what happened but it gave me the Amazon Alexa log in screen and after I entered my credentials- it said

Amazon Alexa Cookie successfully retrieved. You can close the browser.

My challenge now is the debug says "Unexpected end of JSON input" so currently reading through this thread https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/53

nodecentral commented 8 months ago

Nope, sadly I can get past the "Unexpected end of JSON input" error ☹️

It tells me I retrieved the cookie successfully each time after I have authenticated Tried different browsers(chrome/safari on ios) but same JSON error I’m in the UK, and checked the options are correct for .co.uk and en-UK

Would love to get this working …

nodecentral commented 8 months ago

Hi, still looking for any support anyone can give on this.. thanks

Apollon77 commented 7 months ago

Please try with a PC or pad which is not opening the alexa app ... I think the login page from Amazon check if the app is there and directly uses this ... so you need a PC to login or such where the App is not on

Spazpeker commented 7 months ago

same problem for me, it is the same on the PC It just opens the App on your Phone you get no alert image

Apollon77 commented 7 months ago

No this is a different issue! You need to make sure that the IP/FQDN you really opern the proxy pahge in your browser is exect as the settin for "proxy own ip" - this match is used to detect the initial needed login start URL. So make sure to have the settings right!!

Spazpeker commented 7 months ago

No this is a different issue! You need to make sure that the IP/FQDN you really opern the proxy pahge in your browser is exect as the settin for "proxy own ip" - this match is used to detect the initial needed login start URL. So make sure to have the settings right!!

I am putting in the local address ie 192.168.1.79:3456

Apollon77 commented 7 months ago

And then you also need to call it with exaclty this IP and the port

Spazpeker commented 7 months ago

Ok it’s the local host on the account setting needs to be changed to the actual Ip Address.

done that and it’s back working 😀

nodecentral commented 7 months ago

Please try with a PC or pad which is not opening the alexa app ... I think the login page from Amazon check if the app is there and directly uses this ... so you need a PC to login or such where the App is not on

Hi @Apollon77

To confirm, it doesn’t take me to the app anymore, I’m taken to 192.168.1.22:3456 which is an Amazon Alexa login web page, where after I entered my credentials- it still says

Amazon Alexa Cookie successfully retrieved. You can close the browser.

But no matter how many times I go through this, when I go back to NodeRed the debug says "Unexpected end of JSON input"

☹️

Apollon77 commented 7 months ago

this error (in the past) was mostly because of special stuff in the account or wrong parameters that do not match to the account country ... and in fact this issue is off topic for this thread :-) so open a new one with any infos

github-actions[bot] commented 6 months ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 6 months ago

This issue was closed because it has been inactive for 14 days since being marked as stale.