Just a heads up - I was documenting how to use the nodes for a blog and went thru setup again and it fails authorising agains Amazon - having spent hours trying to resolve (and having to reset my password in the process) I went to issues on the node and its already been reported
If you follow link to other software using same concept and either speak Deutches or use a translator - you can see its something to do with changes at Amazon end
So, in the meantime - I think people will be fine for the moment as long as you don't change anything and have to re-auth!
[edit - found the same issue reported further down which says there is an update to the node - just updating now /]
[edit 16Jul 23:06 UK - I'm now thinking its not fixed and that it will need some work to update its main dependacy - still working for me but more by luck I think! /]
It would seem from github issue comments that the maintainer github Apollon77) of the main dependency node (alexa-remote) has fixed the core issue.
But I'm struggling as to howto get this fix into node-red-contrib-alexa-remote2.
Info and hints
but I don't quite know what to do in practice
Tried forking the node on github and changing the dependency version inside package.json and then doing a command line install from my branch but I get error about not being able to remove the node folder
I think if you don't touch it at the moment, it will carry on working - hopefully the cavalry will arrive shortly to help us out - shame the node author seems to be on a sabbatical
Just tried it...This Alexa node still works (I may regret I said that).
You can run it as a normal user on say port 8980 (I can post details if you need them).
Funny Dave, the node description says it needs root access:
"Amazon Echo Hub node is starting a service listening on port 80 which requires Node-Red process to be started with root user."
I used this node a while back and you had to redirect ports. If this has changed it would be a good candidate to control things. No speech output though.
Not saying issue has been fixed (since its been working for me mysteriously for a few days now) but the node author is active on Github so hopefully things will get fixed for everyone
The alexa-remote2 dependency has been updated to 3.2.6 (which that node's author says fixes the issue) [not yet on npm - so hold off unless your brave and manually update via github] so definitely worth upgrading and trying it out
For those that have it working again.... what's going on with the amazon.com/ap/signin page for you? Thinking it was a 2FA issue, I've also tried using an authentication app to add a number to the end of my password and I still get the "There was a problem".
For me - it just works with the 3.10.1 version but it shouldn't as its not working for others.
Current status is that the node author has made code changes that SHOULD fix it but hasn't published the new code to the npm catalog yet.
Unfortunately, the author doesn't seem to communicate with people so we don't know when this will happen or whether the code changes will fix the issue.
Someone with the issue could try updating their node direct from github and let us know whether this fixes their problem but no-one has done so yet
- you can see its something to do with changes at Amazon end
