I was such a fan of this node for the longest time but then I started having issues with it remembering authentication if even able to authenticate at all. Ended up switching to Home Assistant's Alexa Media Player integration and this has been way more stable. But like anything, your milage may vary. This video makes me want to give it another try as it was easier to tie into Alexa routines with Alexa2. It's still possible with Alexa Media Player, just way more convoluted.
If you apply innit correctly you should be ok. I had more issues trying to deauthorise it 🤣😂 I had it installed long time ago as well but at first things were clunky. Got better in last few months
@@notenoughtech so after watching your latest video about using this node instead of IFTTT, I decided to give Remote2 another try. It's been a while since I've used it and for the life of me I cannot figure out which node I'd use to listen for a Routine being called... I see the node to execute a routine but i'm wanting to react to a routine called by a device and do stuff in Node-RED... any quick tip on that?
@@notenoughtech ah, my issue was i was "Running Routine" from the Alexa app (trying to be quiet in the house as i coded this) and nothing was kicking off in Node-RED. I guess that makes sense since there is technically no echo device involved with that.
Id have to check .. I think running a routine from mobile phone should be picked up too. It may have slightly different JSON format so it's worth checking the debug
I have some tutorials on nodered for beginners - perhaps they will help you notenoughtech.com/home-automation/why-nodered-server/ and a good live session: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-0rZj6qPWdmE.html
That's how tutorials should be: short, precise, well prepared and without annoying background music. Great! The device activity event seems to offer a lot of possibities, because you can extract the spoken command as a string and parse it. My idea is to ask alexa for the state of various devices and prepare the answer depending on the device. Example: The command "Alexa, what is the status of the inverter?" would be parsed, would trigger an API call and finally let Alexa say "your current power consumption is ...". Do you have recommandations for me how to realize such a scenario, especially how to avoid an unknown command answer from Alexa? Thanks a lot and take care :-)
Hi! Thanks. This will interest you notenoughtech.com/featured/alexa-routines-setting-volume-on-all-echos-at-once/ In an essence creating routine prevents Alexa from talking Back while query is sent over (part with custom commands)
Is there a way for alexa to say "your package is outside or your package has been delivered" when the yellow light notification turns on?? What program(s) should I use?
Might be helpful to explain somewhere, anywhere -- video title, video, info -- this entire video is about using a tool called NodeRed and you can find out all about how to use NodeRed to program with Alexa at . . . .
Of I understand it correctly the host machine is used to get cookies. You will need to certify your RPI to get SSL connection routed as the server is obtaining credentials on your behalf. (At least that how it looks like to me)
This is game changer !! Man I have very important question for me! Can control system like crestron trigger alexa to do something which is connected already to alexa ! (I hope my question is clear enough)
Thanks for a great tutorial. Looks like some major improvements since I last used it. An update to the latest version soon had me authenticated again. I will be using your method with the initialise node if I have problems with using a cookie text file. Node red 1.1 is nice isn't it? I didn't realise you could view context data in the side bar!!!! That is awesome!!! Another node I use is node-red-contrib-alexa-home-skill. This lets you set up a device, such as a temperature sensor in my case, to be recognised by Alexa. So I can ask Alexa what is the temperate outside. Is somewhat harder to set up than Remote2 though. Time to dust off Alexa and have a play.
@@notenoughtech Yes indeed. It was just after I watched your video that I realised that I could use home skill as the virtual Alexa device and then speak back via remote2. Makes it all very easy to get it to speak context variables. Keep up the good work.
Custom things are easier with Alexa. Yes some search queries are better with GA but on daily basis I don't come across anything that Alexa doesn't answer so frankly speaking... Doesn't bother me which ecosystem is better "on paper" :)
@@notenoughtech I will have to agree with the "on paper" statement! What I think is very strange is that they share a great integration with IFTTT, but then they don't allow any one else to have access to that kind of integrations!
I've installed node-red-contrib-alexa-remote2 (ver 3.10.4). I did as you suggested in your video clip (3:05) and after trigger, I can get message from debug as
There are some compatibility issues after recent amazon was changes. Please take look at GitHub page as someone forked the update that fixes the issues
Hi! Nice video :). I’ve one question, what about the login? Do the cookie expire and how often you need to relogin? I’m using a custom component in Home Assistant for similar things and I need to do it from time to time... Cheers!
I got the cakebaked version. Followed your instructions... However all I can see to get out of it is the 'Alexa Event' node, "Device Activity", and the 'Alexa Other' node "Get Skills". Those show some data on the debug node. However, anything I try to push into the Alexa, such as "Play a sound" or 'Smarthome' node "Action", it says there are no devices with executable actions! What is going wrong?? Please help
@@notenoughtech it will not get devices or show them in a drop down. It won't even play a sound or txt from the node that does that so something isn't working.
Strange. Anything similar reported on GitHub? Problem with these things that if API changes node has to be updated and this is usually someone's pet project at best :(
Very nice videos, specially the intro music. Lol. Can you describe with more details how do I use the init node? Because every thing works fine for me, but can't configure the auto login. Thanks
Hey, I have tried using alexa routine node ,got to know what changes need to be done in routine but what should I change in the inject node because after deploying it's showing null and alexa is not speaking anything ,I have tried to check the device I have added the right device. so what may be the isssue could you please help .
Thanks for giving me hope that I can trigger a routine in Alexa from HASS. Unfortunately, I can't seem to get past the first 'Initialize' step. The Initialize node states "success", but I don't get the cookie to display on the Context Data. I am assuming that I don't have the correct arguments in the Inject Node and Change Node. I have three nodes, Inject Node, Initialize Node and Change Node. The Inject Node I have [msg.payload = flow.alexa]. What are the arguments in the change node? I assume it must be [Set] -- [flow.alexa]. When I refresh the flow, all I get is "" displayed. I am missing something. Thanks in advance for your help.
I wish I would have waited one more hour to write my previous note as I solved it on my own. It was my mistake on the Change Node. The arguments should be [Set] --- [Flow.alexa] to [msg.payload]. Getting the Alexa LInk working solved a huge problem I was having. I want to control an awning and outdoor shade with HASS. I could control each using the broadlink RM4 Pro, but i couldn't control the RF commands from HASS. Alexa recognizes the devices on the Broadlink automatically. With Alexa-Remote2 Node Red component, I created a binary switch in HASS. The switch triggers a State Node which triggers an Alexa Routine. Problem Solved!!! It works great and I don't have to integrate the broadlink into HASS (which is limited in its RF capabilities). Thanks for the video and keep them coming.
Thanks great video, just subscribed to your channel! Question, so creating a dashboard to control all your Alexa devices is pretty simple.....what I am struggling with is how you go about maintaining the current status of the device. For example, say a light is turned on via the dashboard, then someone does a Alexa voice command to shut off....how do I have the switch on the UI update this status? I struggle with wrapping my head around this....I get you can have an event stream coming in, where I am confused is how you monitor that stream for particular device ID's and then inject that data into the flow. Also would love to pick your brain on pulling video into the dashboard. Via a simple HTTP GET request I can pull like video streams from my VMS anywhere and in various formats/codecs.....MJPEG, H.264, H.265 etc.....have been able to pull rtsp streams in using but only works half the time. Ohhhh and if you could make some videos on the dashboard that would be awesome lol. Thanks again, your videos are great and very helpful!
notenoughtech.com/home-automation/why-nodered-server/ This should answer a lot of questions ;) to save the values of the devices use flow context to store the state. My recent heating system video shows you how to embed the content (as a frame) so you could try this with RTSP. as per monitoring changes from Alexa use event listening option from Alexa remote
I find that this is un-initialized rather frequently. This means none of the automations work when until I go in and initialize it- drastically reducing the WAF (Wife Acceptance Factor for those who don't know). Is there a way to store the cookie via a file for long term storage and/or a way to automate the initialization? Otherwise, this is one of the best Alexa node red videos out there, thanks.
@@notenoughtech Ok I had to again put my credentials in to initialize so maybe I have to ask the question: does this need to be manually reinitialized every few days? Am I missing something? does it need to be reinitialized after a few days? does it need to be reinitialized after a updating HA? it was working for a few days then not.
That kind of really defeats the purpose of automation if I have to go into node red and re-sign back in to get the dependent automations to work, doesn't it? And it definitely means the the WAF just went to unacceptable.
hi, i'm a new kid on the block and have a question regarding initializing. every time i deploy a step i need to re-initialize node red every time again. this is quite annoying when i watch this video that the guy is doing changes without this step. any idea how to get rid this annoyance?
I would like my devices to issue a warning to node-red when there is a state change, for example when a light turns on an event is fired. Is this possible and how to do it?
@@notenoughtech What exactly is the node? I've tried it with "On Device Change" and no event is triggered when I turn on a light or motion sensor picks up something.
Your Video Is really great and helped alot, I have a question, the initialize code for alexa authentication is enough even you restart the Node-red Server or the raspberry pi? Or we should open web browser every time we restart?
@@notenoughtech I added your sample to the flow, after triggering flow.alexa manually and "opened browser to login" after any deploy it gonna init from proxy, but if I restarted the server I have to trigger the flow.alexa then open the web browser .. what did I miss?
@@notenoughtech Man Im so sorry. I can see the cookie in context data for the flow under Alexa, But can not find checkbox. Is it included in your video?
Hi thanks for sharing. I have tried this with my Echo devices and cannot get the speak at volume to work. Does it work for you or any one else? I have used the node-red-contrib-alexa-cakebaked fork. I can get the TTS but the speak at different volumes is not working.
@@notenoughtech Thanks! I'm testing on Echo Plus and Dot V3. Both fail to set volume if I use speak at volume. Good idea to try volume command separately. Yes, that works and can set the volume but I was hoping for the speak at volume to work as I am trying to use this for a doorbell notification and I want to raise the vol, speak the message then have the echo device go back the initial vol level. If I use the volume setting, I will have to be reading current vol settings, storing it and then reversing it. That all gets a bit 'chatty' when I'm speaking my doorbell message on 4 echo devices :)
I believe AWS has introduced some changes to the API and node isn't updated yet. On my end I no longer can listen to alexa actions as well. Unfortuantely we will have to wait for the patch
I receive the following whenever I hit the Deploy button. "Authentication failed: "Authentication unsuccessful"" It seems to be disconnect me, but I don't know why?
@@notenoughtech Yeah, whenever I redeploy it happens. I have two IPs associated with my Home Assistant (running on a raspberry pi 4), one is over 5G, the other a direct connection from the pi to my router. When using the 5G IP I get the "Authentication failed" error, when using the other IP I have to reauthenticate again using the login page.
@@notenoughtech Hi Matt, thanks for getting back. Using a couple of 3rd Gen Echos. Frustrating as fine for a day or so, but just stops talking until reinnitalise. Using your flow and tried various time gaps, but no joy.
Can you please share how are you discovering your devices into Alexa? I'm using the Alexa-local method, but only get my devices to be lights and want to have the other types available - TIA
@@notenoughtech Not following what you mean, I'm using HomeAssistant with Node Red as a plug-in, my devices are mainly sonoff, with Tasmota installed, I have a fan plugged into one of the sonoff plugs, to get the devices into the Alexa app I have been using the Alexia-local node, that sets all devices as lights as it emulates Philips Hue. When I do an Alexa detect devices they show up in the app as a light, and I cannot edit it they way that Amazon describe on their website... Thanks for your responses by the way!!!
@@jayargent4156 take a look at Alexa and nodered integration. I have article and video covering just that. You can create virtual Alexa devices and map them to your sonoffs etc
You should get output each time something happens (voice query song request etc) do you have anything on msg.payload? Are you able to control other devices
@@notenoughtech "on device activity" node in on "listening"...but when i say "Alexa....." not start listen me (in debug message no payload, nothing is written into debug message
I cannot reach the webpage of the alexa device is there a easy way to fix this issue? i have a amazon echo dot and i know the IP adress but when i go to that ip adress and use the 3456 port it wont let me in
I am experiencing some issues with this nodes. I have configured everything and all seems OK. I can make alexa speak through my sepakers, play music... all from node-red. But when I try lo listen to events like volume changes or me speaking to Alexa I receive nothing. I hace checked and the configuration of the Alexa Account has the "events" option turned on. Some idea of what can be the problem?
@@notenoughtech Shouldn't this issue be affecting all the users? I'm using the applestrudel version, but with cakebaked the same happened. Is there any other thing I can do besides reporting the issue in github and wait? Thanks in advance :)
@@notenoughtech One last thing. From your perspective, can it be a problem not having SSL active in my HA installation? My hypothesis is that Alexa won't start any communication via an unsecure connection
I'm having a problem. I managed to login first time with proxy after more issues. Now (3 days after) I have to re-login, but when I try the node sent me "Authentication failed: "Authentication unsuccessful"". How can I solve this problem? Thanks
@@notenoughtech Yes, I tried more times, but it fails with the proxy, and does not login with others. The message always remains to go to the broswser at the link "192.168.1.10:3456". I have a PC like server on my home, and it has IP 192.168.1.10
@@notenoughtech yes, I put in my credentials, and I get the successful sentence, but when I return to node red page I see again "open a browser at x.x.x.x:xxx"
I have 12 Alexa devices .... I wish I could stick around but it is two many devices to mute :( Hopefully in new videos you can just say "echo" likely increase your sub count
If all 12 devices hear you at once, you have a bigger problem. Also you can use Alexa Remote to trigger mute on all devices :) Ie Alexa, I'm watching video about alexa (and it mutes all for 20 min)
@@notenoughtech Whole home audio in a house full of echos and my windows machine (and my phone) also has it installed (so it is even tiggered when my headphones are on). I do admire your confidence in making 20,000 subscribers do more work because it would take you 15 seconds to change your wake word to "computer". We need more people that won't cater to the masses. You are the one putting in the work to make these videos' and if I don't like it I can eat dirt. :)
@@bubbasreviews5295 I just really like to see people suffer. That's why I make all the suffer oriented projects and use the wake word in videos that demonstrate the use cases of specific voice assistant. {Cue evil overlord laughter}
@@Alcatraz2k but if you new to nodered I have bunch of tutorials that could make thing easier ;) What didn't happen ? I don't know what you are talking about 🙈🙈🙈
