Great video, I manged to get it working, the difference is that whenever I make a change and deploy I have to enter my amazon password. Any idea why. You did not seem to do that in your video.
Just enter something (without spaces) in the File Path field when you configure your Alexa Account Node. Exactly as I'm showing in the video. This will keep your credentials when you re-deploy. Try it out and let me know what happened. Good Luck
Thank you for an excellent video. As a newby to running nodered in docker I did encounter issues that others may also experience. While creating/linking the amazon account, the url to visit must be the name or IP of the machine where nodered is running, and not localhost which will probably pointing to your laptop. Second, in docker one must add a - 3456:3456 stanza below - 1880:1880 in the docker compose yaml file. then run docker-compose up nodered to expose port 3456 and allow access. Thanks again.
An update, the server settings can be worth to play around with if Alexa wont speak.. I had everything set up and the Alexa could find my local devices with the right name, was sending stuff with success regarding to node red, but the echo-dot it self was still quiet.. Not a single sound or response.. I live in Sweden and regarding to the updated article and a general comment of this video, if you live in Europe you should use the British or German server settings (Server Host and Page), I was banging my head against the desk och looking everywhere to find a solution or someone else with the same problem. Then I just as a chans, I change the server settings to US, like in the video, and all of it was working.. Of course not your fault seems I guess something somewhere have been updated since the video was made, just pointing it out if it helps anyone else with the same issue :) Otherwise a great video as usual, big thank you for all the great content you provide! Keep it up, we appreciates it!
Very helpful video, even a year and a half later. Every time I reboot, I have to open the browser window and login to amazon and enter the OTA information, is this just part of things or am I doing something wrong? Subscribed to your channel, I can't imagine being able to instruct in what appears to be your second language, you're a smart dude! Meaning that as a huge compliment, nothing negative here.
After reading some of the other comments, maybe it will work upon next reboot, I did add the file in the File Path area, but not sure if I did that before or after the last reboot.
First of all - thanks for the good words and for the sub! That was one of my first videos that I uploaded in YT. Anyway, adding the file will fix the things with the restarts, but from time to time you will have to login again. I guess this is because the integration is not coming directly from Amazon. Good luck!
Had the same issue, I was able to resolve it by changing "localhost" in the alexa account settings in the node red "get echo devices" node to the exact IP of the server node red is running on. Hope it helps you
@@KPeyanski Hi Kiril. I have some flows with alexa-remote2, and some times I have the error: "no json at incoming". Do you have some fix to this error? Thanks in advance.
I have a device (Air conditioned) that works only with Alexa (cannot be integrated in Home Assistant so far). I can turn it on off through node-red and my own skill. I wish I could retrieve the temperature (current not targe) from the unit. How could it be done? Thanks in advance (the video is great)
Cheers mate, popped this on and its working great. looking forward to playing with the settings. First job is to integrate it into my alarm system that i'm making in node red.
That’s sounds cool. Can you share something more about your alarm system? Do you have a siren? And what kind of sensors do you use? Thanks for the comment.
@@KPeyanski Hi mate, its quite simple at the moment. saving up for the tech but thought I would do the front end while waiting lol. I do plan for siren, think it will be run by a wifi switch, poss a shelly1 as they are a dry relay. sensors not yet but have rigged HA with dummy boolean switches for now to test. Use NR Dashboard buttons set via NR to change colour when selected, cancel then resets the count and the button colours if you got it wrong lol. Needed the Alexa routine to set volume high, announce its arming, sensor detected etc. Also give notifications via Telegram to phone with actions.
This is just what I needed to make Alexa dot echo speaker work as part of alarm system that I'm working on. KPeyanski thank you for your great examples and video.
I tried this on my windows desktop and it works. But, I really want to run it on my home server where node red is a home assistant add-on and HA runs in a proxmox virtual machine. Not at all sure how to initialize the alexa account. Any ideas?
Yes, this is working in Node-RED installed as Home Assistant add-on. The only real advantage is that you are not dependent of Home Assistant and if your HA is not working for some reason your NR will still work.
Hi, thanks for the video. Did you write this node? I used it for a long time, but always had to re-authenticate manually. I did have the authentication file setup, although I used a subdirectory which didn't exist. I have now changed it to just a file and can see the file in /home/me - hopefully I will not need to keep re-authenticating!
Super-great video. I'm trying to implement it. I've been tearing my hair out...what little is left... to find 'file location' in Alexa Routine node without success. I'm running node-red and not having luck locating this file...So, filled in the 'file path' with a name in all caps and then when to my raspberry pi with a sudo shell and did a find from root. The file was in '/home/pi' directory but when adding the file path it crashed on deploy. Where should the path be pointing to and what should the syntax be? Also, how to convert msg.payload to ssml for my raspberry pi pin-status app? Thanks
actually it does seem to work by simply adding a file name as in the vide but you need to go to the auth page every time you restart HA, thats a bit rubbish :-(
nice ,great video, please help me with this, how to trigger alexa in listen mode? by using node red, another question, if i close gui of tts, will alexa remember , my text that, i was wriitten? last where does authfile stored. i installed node red in Home assistant
Hi Hassani, I don't know about your first question, but regarding your second I found the file once in the main folder where NR were installed, but I was using Docker version of the NR back then and inside the Docker container I found the file, as far as I remember it was unreadable.
I installed alexa AVS on Magic Mirror raspberry pi, Home assistant with node-red addon on AWS EC2 server. When I connect to my alexa with proxy auth method, browser said i have to enable cookies. I dont know how to solve this. My Alexa AVS device status is offline but working normal. I tried to use cookies auth method, connected and ready. but my device do not giving any voice. the result status is success. Can i add costum command trigger with this node? without amazon alexa app, because i cant install that app from my country. any ideas? Big Thanks
Hello, the video is amazing and straight forward, I have my Alexa set up on raspberry Pi on the developer platform, can use this with it? will it work? and will you mind doing some videos on how to build and use Alexa skills. Am still a novice in all of this. Thanks
Hi Tonu, I’m really happy that you like it. As long as you able to install Node-Red, and the Pi and Alexa are in the same network- it will work. Check my - Alexa’s dark side video as well. I’m showing there where to find Alexa skills and how to install them. It’s easy. Good luck
Fantastic, just what I was looking for, looks like there's lots in v2 to try. Subscribed. As I run it in docker i had to open port 3456 to do the initial authorisation, do I need to keep this port open?
Hi, I am really struggling with authentication part, it connects but deploy breaks it. Either have to reauthenicate or is giving me 3456 port already in-use.
Dear K, Tx a lot, realy to the point. perfect. Haven't got where the Authorization File is stored to. Anything to be protected or cosiderd arround this file? Anyhow great video !! Thanks
Hi< Where is local host pointing, do you need to be on the samebox as the nodered? If you not on the same box as the node red do you put the ip address of nodered instead of localhost. Both options aren't working.
Yes, you should use the IP where the NR is installed. Can you share your config in my discord so I can try to help. Also check the comments of this video. There are some tips for common issues with the Service Host that you can try.
@@KPeyanski I have Alexa media -layer installed and can get “tts” working in the Service tab. But when I place the code in a script it will not work. That is why I gave Node Red a try. I tried putting in a different port number but got the could not connect message again. At a losses.
@@KPeyanski I have the Alexa media player installed through Hacks. Bent know if that makes a difference or not? I have tried a bit of code yonder the service table and “tts” works. But when I use it in a scrip it dose not work. That is why I tried Node Red. I did try a different port number and it still could not connect? At a losses.
This is in Node terminal 21 Nov 21:57:03 - [warn] [alexa-remote-account:67db8cbb.cdd794] failed to initialise smarthome simplified: "no body" in video alexa-remote2 i v3.2.8 now is 3,8 is this problem
Hi again, regarding File Path for storing amazon credentials, if you want that file to be in the same folder as your config yaml files what would be the full path ?
Why do you need this? This file is filled with some random not readable chars. I just checked my configuration (I put it without any path) and the file is located in the /usr/src/node-red/ inside the node-red docker container
Hi there. Great video. I followed your instructions but gone a "port 3456 already in use" error. Restarted node-red and home-assistant and the problem is still there. Any ideas?
This looks like a great node. I cannot get it to work. Proxy method i get "no csrf found". when I try to password method it say logon unsuccessful when i know that the username and password are correct.Have you any ideas on how to fix this. I use chrome.
KPeyanski..Great Tutorial. I managed to reach up to "Alexa Speak" web page . But even after many time refreshing still I am not getting My DEVICE in Speak Page. It's stays blank/or initially only showing " select your Device". Can you guide ! Updae: I can not get my Echo,,,But it shows "Select Option" only (No Echo showing in Option). And It Works...May be I have only one Echo, that why ! But Dear, Thank you for such a good work.
It was working before, but now no matter what I do, Alexa's voice won't play on my android phone anymore. I'm at a loss edit: i restarted the whole process. It's working again. Thank goodness
@@timcash6372 It's not just you, there is an issue with this right now. Amazon changed something around the start of July, so now the IP:Port method for the cookie doesn't work properly in most locations. You have to follow the manual cookie method for the time being: github.com/586837r/node-red-contrib-alexa-remote2/blob/master/get_cookie.md Hopefully this gets fixed soon...
for UK and EU accounts, you need to use alexa.amazon.co.uk as service host and amazon.co.uk as Page. If you are using a vm for your Hassio (example) you need to fill in that ip adress instead of the localhostaddress...that worked for me..
@@KPeyanski hi there, set up as the video. changed to the UK as above. i type the ip of the server running HA / node red (installed via hassio) etc 192.168.0.xx:3456, it then trys to take me to localhost:3456/www.amazon.com/ap/signin?showRmrMe=1&openid.return_to=https%3A%2 etc. etc. which wont open. im running HA on a ubuntu server i assume running docker. ( was installed following instructions on HA install page) any ideas?
I could not get this to work (I am in Australia). So I first use the standard pitangui.amazon.com/amazon.com to sign in, and when that is done, change that to alexa.amazon.com.au/amazon.com.au, it just magically works.
I'm using home assistant os, so I have to enter the localIP of the device rather than localhost, but it's redirecting to localhost, and I can't get through it
When i changed the service host and page and deployed , i have linked my Alexa device through 3456localhost After that instead of showing ready under the node it is showing "ERROR WHILE CHECKING AUTHENTICATION".
What did you type as a Service Host and Page? Where is your primary Amazon location (which amazon web site are you are usually accessing exactly) If you return the previous Service Host and Page is the "ERROR WHILE CHECKING AUTHENTICATION" disappear?
@@KPeyanski i gave service host and page as UK alexa.amazon.co.uk amazon.co.uk en-UK iam using amazon.in and location is india, yes the error dissapear when i go back but on continuing with ssml i get the messege at rouitine speak as "account not initialized". help me out please.. and even my echo dot not responding as i mentioned before.
Can you please also try the following: Service Host: pitangui.amazon.com Page: pitangui.amazon.com and Language: en-US If you haven't tried that already
"Merde", I faild to create this account file. Running Node-Red on Hass.io (Home Automation). I'm not able to open "IP-Adress of Raspery:3456". The hint with get_cookie.md is for me that cryptic that I'm lost (not using the developer console even once a year). Is there a tutorial or alternative for this step?
@@KPeyanski Thanks. I don't own 3rd gen echo, asking more for a friend. Nevertheless, I had a quick play already. Seems to be working fine, but only downside I have noticed is, you need to confirm auth after NodeRED server restart.
Did you add a value in the File Path field exactly as I'm showing in the video? This option create an encrypted file with the Amazon credentials and the integration should work after restarts. Let me know if it worked for you after you try it.
@@KPeyanski Yes, I did create a file name. I only tried it once, so I will give it a go later on again. It works fine when you deploy flows, but if you need to restart nodered server, it asked me to go to localhost:3456 again. But, like I said, I only done it once, so I will give it a go again later on. Nice video, BTW
@@lucasch.159 My Node-Red server is on a Raspberry Pi that is connected to an UPS, so I almost never restart it. You can think of such setup if it's critical for you this to almost always work ;) And lastly, but most importantly - Thanks for the kind words, consider watch my other videos and subscribe to my channel if you like them.
I keep getting to the login for amazon but keeps telling me "To continue shopping at Amazon.com, please enable cookies in your Web browser". ccokies are enabled. tried chrome and Edge any advice
It was working well for me for a few days but now I have "Authentification failed: 'no body" I tried to delete my account and add it again but same issue
Nice! By the way , has anyone here acomplished this using a language other than javascript/nodejs ? Lets say , python ou c# ? Im wondering if i can trigger some tts using serverless computing like Azure Functions or Aws Lambda
Don't know that and never heard about it before. Node-RED and NodeJS (javascript) works natively. I doubt about the python and c# support for this exact plugin, but you never knows... everything is possible!
Thanks for your video - works perfect inside my RedMatic Setup. Just to help someone having same start issues like me with activating the account via accessing the localhost:3456 > Turn off the firewall from your Homematic CCU. After logging in to your Amazon Account you can turn it back on ;o)
Thanks for the awesome video.. I am located in India, tried with alexa.amazon.in and amazon.in in the service host page.. works great; had issues with authentication every time I redeployed when i tried with alexa.amazon.it and amazon.it .. works great after I changed the values to alexa.amazon.in and amazon.in in the service host page
![[Live สด] การออกรางวัลสลากกินแบ่งรัฐบาล งวดวันที่ 16 พฤศจิกายน 2567](http://i.ytimg.com/vi/wPd7VFfWHIA/mqdefault.jpg)
Great video, I manged to get it working, the difference is that whenever I make a change and deploy I have to enter my amazon password. Any idea why. You did not seem to do that in your video.
Just enter something (without spaces) in the File Path field when you configure your Alexa Account Node. Exactly as I'm showing in the video. This will keep your credentials when you re-deploy. Try it out and let me know what happened. Good Luck
@@KPeyanski Hi, thanks for the reply, I have added a file name but now get an error "port 3456 already in use"
Try to restart your device/docker container
@@KPeyanski Hi, that did not work, uninstalled Node Red and started again, now all working. Many Thanks
@@brianmoulson5512 Well done Brian. Enjoy.
All goes well until I enter localhost:3456 and I get a localhost refused to connect. turned off my firewall but still does not work. Any ideas?
Thank you for an excellent video.
As a newby to running nodered in docker I did encounter issues that others may also experience.
While creating/linking the amazon account, the url to visit must be the name or IP of the machine where nodered is running, and not localhost which will probably pointing to your laptop.
Second, in docker one must add a - 3456:3456 stanza below - 1880:1880 in the docker compose yaml file.
then run docker-compose up nodered to expose port 3456 and allow access.
Thanks again.
Thanks for the very detailed and helpful comment Alf. I’m glad that we have you here. Keep up writing ;)
Many thanks for the explanation!
An update, the server settings can be worth to play around with if Alexa wont speak.. I had everything set up and the Alexa could find my local devices with the right name, was sending stuff with success regarding to node red, but the echo-dot it self was still quiet.. Not a single sound or response.. I live in Sweden and regarding to the updated article and a general comment of this video, if you live in Europe you should use the British or German server settings (Server Host and Page), I was banging my head against the desk och looking everywhere to find a solution or someone else with the same problem. Then I just as a chans, I change the server settings to US, like in the video, and all of it was working.. Of course not your fault seems I guess something somewhere have been updated since the video was made, just pointing it out if it helps anyone else with the same issue :) Otherwise a great video as usual, big thank you for all the great content you provide! Keep it up, we appreciates it!
Thanks for sharing this Rasmus! I also have reports that devices in India worked with amazon servers in Italy only. So go figure...
Thanks a lot - the additional tips on your homepage regarding the 'Service Host' and 'Page' for the german language. Now I got it working.
Perfect job
Glad it was helpful!
OMG Finally got Alexa working on Home Assistent. THANK You
Glad to help, but are you manage to got her working on Home Assistant or on Node-Red?
@@KPeyanski i have hassio and node red as addon. I think ill manage later all my devices will node red and its dashboard. Thx.
@@ajiyahya Oh I see. Let me know what happened. And of course if you need some help.
Very helpful video, even a year and a half later. Every time I reboot, I have to open the browser window and login to amazon and enter the OTA information, is this just part of things or am I doing something wrong? Subscribed to your channel, I can't imagine being able to instruct in what appears to be your second language, you're a smart dude! Meaning that as a huge compliment, nothing negative here.
After reading some of the other comments, maybe it will work upon next reboot, I did add the file in the File Path area, but not sure if I did that before or after the last reboot.
First of all - thanks for the good words and for the sub! That was one of my first videos that I uploaded in YT. Anyway, adding the file will fix the things with the restarts, but from time to time you will have to login again. I guess this is because the integration is not coming directly from Amazon. Good luck!
My login screen for retrieving the cookie is different. I get a qr code and when I scan it it goes to my Alexa app, but then does nothing…
Had the same issue, I was able to resolve it by changing "localhost" in the alexa account settings in the node red "get echo devices" node to the exact IP of the server node red is running on. Hope it helps you
Thnks a lot!!!!!!! this is exactly what I was looking for!!!!. Regards from Chile.!!
Glad it helped! Greetings to Chile as well :)
@@KPeyanski Hi Kiril. I have some flows with alexa-remote2, and some times I have the error: "no json at incoming". Do you have some fix to this error? Thanks in advance.
I have a device (Air conditioned) that works only with Alexa (cannot be integrated in Home Assistant so far). I can turn it on off through node-red and my own skill. I wish I could retrieve the temperature (current not targe) from the unit. How could it be done? Thanks in advance (the video is great)
Cheers mate, popped this on and its working great. looking forward to playing with the settings. First job is to integrate it into my alarm system that i'm making in node red.
That’s sounds cool. Can you share something more about your alarm system? Do you have a siren? And what kind of sensors do you use? Thanks for the comment.
@@KPeyanski Hi mate, its quite simple at the moment. saving up for the tech but thought I would do the front end while waiting lol. I do plan for siren, think it will be run by a wifi switch, poss a shelly1 as they are a dry relay. sensors not yet but have rigged HA with dummy boolean switches for now to test. Use NR Dashboard buttons set via NR to change colour when selected, cancel then resets the count and the button colours if you got it wrong lol. Needed the Alexa routine to set volume high, announce its arming, sensor detected etc. Also give notifications via Telegram to phone with actions.
This is just what I needed to make Alexa dot echo speaker work as part of alarm system that I'm working on. KPeyanski thank you for your great examples and video.
Glad I could help!
I tried this on my windows desktop and it works. But, I really want to run it on my home server where node red is a home assistant add-on and HA runs in a proxmox virtual machine. Not at all sure how to initialize the alexa account. Any ideas?
Thank you very much. Your videos are really helpfull and inspiring.
You're very welcome! Check my other videos as well!
Will this also work using the Node Red add on inside of Home Assistant? Are there advantages to using it in a Docker desktop?
Yes, this is working in Node-RED installed as Home Assistant add-on. The only real advantage is that you are not dependent of Home Assistant and if your HA is not working for some reason your NR will still work.
KPeyanski I could see that being an advantage. Thank you!
Hi, thanks for the video. Did you write this node? I used it for a long time, but always had to re-authenticate manually. I did have the authentication file setup, although I used a subdirectory which didn't exist. I have now changed it to just a file and can see the file in /home/me - hopefully I will not need to keep re-authenticating!
No, I didn’t write this node. I’m just using it exactly as you do. And I also have to re-authenticate from time to time.
Hi, I followed your instructions but localhost:3456 refuses to connect. I am running node red inside home assistant. Could that be my problem? Thx
Super-great video. I'm trying to implement it.
I've been tearing my hair out...what little is left... to find 'file location' in Alexa Routine node without success.
I'm running node-red and not having luck locating this file...So, filled in the 'file path' with a name in all caps and then when to my
raspberry pi with a sudo shell and did a find from root. The file was in '/home/pi' directory but when adding the file path it crashed on deploy. Where should the path be pointing to and what should the syntax be?
Also, how to convert msg.payload to ssml for my raspberry pi pin-status app?
Thanks
same problem here all working well but cant store the authentication file explanation should be clearer, did you resolve this?
actually it does seem to work by simply adding a file name as in the vide but you need to go to the auth page every time you restart HA, thats a bit rubbish :-(
yes, you have to re-authenticate from time to time
nice ,great video, please help me with this, how to trigger alexa in listen mode? by using node red, another question, if i close gui of tts, will alexa remember , my text that, i was wriitten? last where does authfile stored. i installed node red in Home assistant
Hi Hassani, I don't know about your first question, but regarding your second I found the file once in the main folder where NR were installed, but I was using Docker version of the NR back then and inside the Docker container I found the file, as far as I remember it was unreadable.
@@KPeyanski thanks, I am expecting more videos from you,have a nice day!!!
Hi. Thank You for the video. I'm runniing my Node-Red on Raspberry Pi3 (Openhabian), not in Docker. How can I open port 3456 for Alexa authorization?
It should open automatically but you should add your raspberry pi IP in the configuration instead of localhost/127.0.0.1.
Thanks for the vid. Just wondering the same thing can be done with Google home hub/Google mini? Thanks
I believe so
thank you! just what I was looking for!
Hey, did you manage to enable the TTS on your Alexa?
I installed alexa AVS on Magic Mirror raspberry pi, Home assistant with node-red addon on AWS EC2 server. When I connect to my alexa with proxy auth method, browser said i have to enable cookies. I dont know how to solve this. My Alexa AVS device status is offline but working normal.
I tried to use cookies auth method, connected and ready. but my device do not giving any voice. the result status is success.
Can i add costum command trigger with this node? without amazon alexa app, because i cant install that app from my country.
any ideas? Big Thanks
Hello, the video is amazing and straight forward, I have my Alexa set up on raspberry Pi on the developer platform, can use this with it? will it work? and will you mind doing some videos on how to build and use Alexa skills. Am still a novice in all of this. Thanks
Hi Tonu, I’m really happy that you like it. As long as you able to install Node-Red, and the Pi and Alexa are in the same network- it will work. Check my - Alexa’s dark side video as well. I’m showing there where to find Alexa skills and how to install them. It’s easy. Good luck
Hi great video, did you have a problem with amazon cookies. If so how did you fixit.
Not yet!
Fantastic, just what I was looking for, looks like there's lots in v2 to try. Subscribed.
As I run it in docker i had to open port 3456 to do the initial authorisation, do I need to keep this port open?
Thanks for the sub! Leave the port open as you have to re-authenticate from time to time
Hi,
I am really struggling with authentication part, it connects but deploy breaks it.
Either have to reauthenicate
or is giving me 3456 port already in-use.
reauthenticate is needed from time to time, if 3456 Is used change the port or restart everything. Why deploy breaks?
can't get the local host to open in browser to link the account is there a trick i entered it just like you did it
Put the IP in the node of the host where node-red is installed instead of localhost
@@KPeyanski going to have to play with it some more. To figure it out. But thanks for the great video again
I got an error that port 3456 already in use. Is that number any number?
probably you have to restart everything and to try again
All the way from kenya
Greetings to Kenya. I always wanted to see the big 5 there. Maybe I will someday :)
@@KPeyanski You most welcome....When around HMU
Dear K, Tx a lot, realy to the point. perfect. Haven't got where the Authorization File is stored to. Anything to be protected or cosiderd arround this file? Anyhow great video !! Thanks
You're welcome! Glad it help. Nothing to worry the file is encrypted. I saw it somewhere, but forgot where it was ...
Can this device work out on newspaper reading???
you can schedule it to tell you the news from reuters at specific times for example
Hi, how to use TTS with telegram bot extension? (Alexa says what i send to the bot)
Thanks
Just to confirm you wish the Telegram bot to TTS the message you are sending? And Alexa is already fine?
Hi<
Where is local host pointing, do you need to be on the samebox as the nodered?
If you not on the same box as the node red do you put the ip address of nodered instead of localhost.
Both options aren't working.
Yes, you should use the IP where the NR is installed. Can you share your config in my discord so I can try to help. Also check the comments of this video. There are some tips for common issues with the Service Host that you can try.
Very helpful. Thanks for posting !
Did you manage to make it work?
@@KPeyanski I am watching this now at work ha but seems straightforward enough. Going to use this with my home assistant nodes / hue lighting nodes.
That’s great. I’m cooking more HA & NR videos, so consider subscribing. Good luck.
@@KPeyanski awesome will do
I will try not to disappoint ;)
I get red square that port 3456 "Already in use", how o I fix that?
Just change the 3456 value to something else in the port field. To get there click on the pencil button in Amazon account i
@@KPeyanski I have Alexa media -layer installed and can get “tts” working in the Service tab. But when I place the code in a script it will not work. That is why I gave Node Red a try. I tried putting in a different port number but got the could not connect message again. At a losses.
@@KPeyanski I have the Alexa media player installed through Hacks. Bent know if that makes a difference or not? I have tried a bit of code yonder the service table and “tts” works. But when I use it in a scrip it dose not work. That is why I tried Node Red. I did try a different port number and it still could not connect? At a losses.
If I haven't Echo dot can you start examples ?
If you have any other Alexa enabled smart speaker from Amazon - then yes
Now I haven't Echo Dot and test examples in NodeRed all is ok but in NodeRed > Dashboard UI Devices is empty after refresh.
Hot Monitor it happens like that when you have error/errors in some of you flows. Try to find them, compile and restart Node-Red
This is in Node terminal 21 Nov 21:57:03 - [warn] [alexa-remote-account:67db8cbb.cdd794] failed to initialise smarthome simplified: "no body" in video alexa-remote2 i v3.2.8 now is 3,8 is this problem
@@hotmonitor try to change the Service Host and Page in the Edit Alexa Account node window
Thanks for accellent video!!!
:) thanks for the great comment.
Hi again, regarding File Path for storing amazon credentials, if you want that file to be in the same folder as your config yaml files what would be the full path ?
Why do you need this? This file is filled with some random not readable chars. I just checked my configuration (I put it without any path) and the file is located in the /usr/src/node-red/ inside the node-red docker container
@@KPeyanski If HA or node red is restarted I still have to enter my Amazon password, is this normal, I wanted to see if the file existed.
Brian Moulson yes, this is normal after restart.
local host doesnt work when i search on the browser
Hi there. Great video. I followed your instructions but gone a "port 3456 already in use" error. Restarted node-red and home-assistant and the problem is still there. Any ideas?
Try change it from the node configuration or find which app is taking that port.
This looks like a great node. I cannot get it to work. Proxy method i get "no csrf found". when I try to password method it say logon unsuccessful when i know that the username and password are correct.Have you any ideas on how to fix this. I use chrome.
Hi Bradley, send me some screenshots of your configuration in my discord server - invite.gg/kpeyanski
it's exactly the same for me: "no csrf found"
yesterday everything worked well!
I run node-red under doker under synology, and I use chrome.
I just managed to get rid of the problem by stopping node-red, then relaunching it
@@laurentdaudibon5981 Good job Laurent. Thanks for letting us know how you fixed this. Very nice !
How does one initiate TTS via alexa voice command
Not so sure, sorry
KPeyanski..Great Tutorial. I managed to reach up to "Alexa Speak" web page . But even after many time refreshing still I am not getting My DEVICE in Speak Page. It's stays blank/or initially only showing " select your Device". Can you guide !
Updae: I can not get my Echo,,,But it shows "Select Option" only (No Echo showing in Option). And It Works...May be I have only one Echo, that why !
But Dear, Thank you for such a good work.
Hope all is sorted out already. Cheers
It was working before, but now no matter what I do, Alexa's voice won't play on my android phone anymore. I'm at a loss
edit: i restarted the whole process. It's working again. Thank goodness
Great to hear! Also thanks that you share the solution as well :)
@@KPeyanski it seems to completely stop working when I install SSML. Im trying to get her to whisper but it won't work
i cant get passed the localhost log in ive tried the ip address and the localhost but cant log in
Type the IP of the host where you node-red is installed.
I have nothing
@@timcash6372 It's not just you, there is an issue with this right now. Amazon changed something around the start of July, so now the IP:Port method for the cookie doesn't work properly in most locations. You have to follow the manual cookie method for the time being:
github.com/586837r/node-red-contrib-alexa-remote2/blob/master/get_cookie.md
Hopefully this gets fixed soon...
I could not get the browser to open the localhost:3456. I turned off firewall as suggested below but it still will not open the page. sigh...
Change localhost with the local IP where node red is installed. You should have Something like 192.168.0.2:3456
@@KPeyanski Yes I had tried that also.
for UK and EU accounts, you need to use alexa.amazon.co.uk as service host and amazon.co.uk as Page. If you are using a vm for your Hassio (example) you need to fill in that ip adress instead of the localhostaddress...that worked for me..
Thanks for that clarification Kxi, hope that helps the others.
@@KPeyanski hi there, set up as the video. changed to the UK as above. i type the ip of the server running HA / node red (installed via hassio) etc 192.168.0.xx:3456, it then trys to take me to localhost:3456/www.amazon.com/ap/signin?showRmrMe=1&openid.return_to=https%3A%2 etc. etc. which wont open. im running HA on a ubuntu server i assume running docker. ( was installed following instructions on HA install page) any ideas?
I could not get this to work (I am in Australia). So I first use the standard pitangui.amazon.com/amazon.com to sign in, and when that is done, change that to alexa.amazon.com.au/amazon.com.au, it just magically works.
@@krannock7 Hi Simon, did you have finaly found a solution for hass.io as base?
I'm using home assistant os, so I have to enter the localIP of the device rather than localhost, but it's redirecting to localhost, and I can't get through it
Same problem here
@@PileofKyle I realised that in the node there is a IP parameter, you need to remove “localhost” and add the server IP instead
You have to enter the IP where the Node-RED is installed.
@@KPeyanski @kevin Nadjarian Thanks for the response that did the trick!
@@kevinnadjarian3328 thanks for the suggest :)
thanks, much appreciated! :D
You are welcome. More good stuff is conning soon.
for everything it is showing success but my echo dot not giving any voice. can you help me out!
Try to change "Service Host" and "Page" inside your Alexa Account node and then restart Node-RED. I had a similar issue before and this helped me.
When i changed the service host and page and deployed , i have linked my Alexa device through 3456localhost
After that instead of showing ready under the node it is showing "ERROR WHILE CHECKING AUTHENTICATION".
What did you type as a Service Host and Page? Where is your primary Amazon location (which amazon web site are you are usually accessing exactly) If you return the previous Service Host and Page is the "ERROR WHILE CHECKING AUTHENTICATION" disappear?
@@KPeyanski i gave service host and page as UK alexa.amazon.co.uk amazon.co.uk en-UK iam using amazon.in and location is india, yes the error dissapear when i go back but on continuing with ssml i get the messege at rouitine speak as "account not initialized". help me out please.. and even my echo dot not responding as i mentioned before.
Can you please also try the following: Service Host: pitangui.amazon.com Page: pitangui.amazon.com and Language: en-US
If you haven't tried that already
"Merde", I faild to create this account file. Running Node-Red on Hass.io (Home Automation). I'm not able to open "IP-Adress of Raspery:3456". The hint with get_cookie.md is for me that cryptic that I'm lost (not using the developer console even once a year). Is there a tutorial or alternative
for this step?
Sorry I'm not sure.
Does it support 3rd gen Echos?
Yes, it is supported. You can try it and then answer back the result here. Good luck
@@KPeyanski
Thanks. I don't own 3rd gen echo, asking more for a friend. Nevertheless, I had a quick play already. Seems to be working fine, but only downside I have noticed is, you need to confirm auth after NodeRED server restart.
Did you add a value in the File Path field exactly as I'm showing in the video? This option create an encrypted file with the Amazon credentials and the integration should work after restarts. Let me know if it worked for you after you try it.
@@KPeyanski
Yes, I did create a file name. I only tried it once, so I will give it a go later on again. It works fine when you deploy flows, but if you need to restart nodered server, it asked me to go to localhost:3456 again. But, like I said, I only done it once, so I will give it a go again later on.
Nice video, BTW
@@lucasch.159 My Node-Red server is on a Raspberry Pi that is connected to an UPS, so I almost never restart it. You can think of such setup if it's critical for you this to almost always work ;) And lastly, but most importantly - Thanks for the kind words, consider watch my other videos and subscribe to my channel if you like them.
I keep getting to the login for amazon but keeps telling me "To continue shopping at Amazon.com, please enable cookies in your Web browser". ccokies are enabled. tried chrome and Edge any advice
I am getting this issue as well trying to authenticate from a raspberry pi. Perhaps Amazon has changed something.
im in the same boat.
I don't know what could be the issue my integration is still working.
It was working well for me for a few days but now I have "Authentification failed: 'no body" I tried to delete my account and add it again but same issue
and then after minutes its back to normal .... weird ... (but its working so whatever!)
And then not working again, weird
Glad that it worked at the end!
Nice! By the way , has anyone here acomplished this using a language other than javascript/nodejs ? Lets say , python ou c# ? Im wondering if i can trigger some tts using serverless computing like Azure Functions or Aws Lambda
I know i can do this with nodejs, but i dont know javascript
Don't know that and never heard about it before. Node-RED and NodeJS (javascript) works natively. I doubt about the python and c# support for this exact plugin, but you never knows... everything is possible!
Freezer Door Left Open and Alarm System
Yes, that can be accomplished!
@@KPeyanski I just created the freezer door part. Gonna work on the alarm part next.
Thanks for your video - works perfect inside my RedMatic Setup. Just to help someone having same start issues like me with activating the account via accessing the localhost:3456 > Turn off the firewall from your Homematic CCU. After logging in to your Amazon Account you can turn it back on ;o)
Thank you for your comment and instructions.
Thanks for the awesome video.. I am located in India, tried with alexa.amazon.in and amazon.in in the service host page.. works great; had issues with authentication every time I redeployed when i tried with alexa.amazon.it and amazon.it .. works great after I changed the values to alexa.amazon.in and amazon.in in the service host page
Great 👍 Greetings to India, hope that I will visit India some day!