Control Node Red with voice from Google Now 

Thanks for the response mate. Comments like this make me want to continue working on the subject and posting more videos.

Yes, it is quite amazing how much you can do with just a small amount of programming when you have the correct tools.

Yeep!!! Now im trying to understand Databases to do a logger. Have TV control from Node-red and some devices added. I have uploaded a video showing my first steps with this. :D Have a look! Keep posting!

google assistant

After a quick Google, I can see a node-red-contrib-broadlink for node red. The page says that it works with RM pro, so that sounds promising.

The audio out plays audio on over the browser. You need to be running dashboard and you can hear the audio on your computer, not the raspberry pi.

@@csongorvarga it must be like as you said,but I can not hear anything with no error message ,another thing I notice when I double click on the audio node in node red there are a selection for a TTS voice file that you can chose from. but in my case it show nothing it mean I can not chose any TTS voice file..thanks alt for you answer

It was a long time ago, but I am sure it works. But this example shows how you can use the voice recognition on your phone, that is not the same the smart home speakers like Google Home, Mini or the Home Hub. That needs a completely different process called Google Actions, but I have not used that yet.

That is interesting. I also have security on the UI and also on admin, but all other HTTP addresses do not have login credential issues.

Okay I found the problem was actually this line of code which sets the HTTP password: httpNodeAuth: {user:"guest",pass:"password_hash_here"}

I don't know. This is the only app that works with AutoVoice I know of.

I must have missed something. Why do you say "before scrapping it"? I also got a Google Home a few weeks back, but I did not manage to integrate it with Node Red yet.

Scrap wasn't quite the right word. So the code picks up on the keyword - and traps the rest of the text for you to use - I did this about a year ago - BUT Google Now then goes off to the search engine as it normally would and if I recall rightly Tasker is used to STOP that search - but you can see in the video it is still there, sometimes extremely briefly, sometimes not so briefly. I stopped using this at that point and I went down the Alexa route where we wrote a SKILL for Alexa which works and returns all the words back in an array - sadly it has to go via Amazon's servers and (a) you need HTTPS on ONLY port 443 - not much good if your service provider uses 443 for maintenance (there is no NEED to use 443 for HTTPS but Amazon insists on it despite pleas to the contrary and (b) Amazon have apparently now scrapped something that is needed to recreate what we've done - I found that out today hence I would MUCH rather use Google now but depending on the speed of your phone, that brief burst of Search and the need for it to turns the screen on AND be plugged on mean that Google's version "could do better".

I see, I did not realize that is happening in the background. In my previous comment when I said Google Home, I meant the Amazon Echo like device. That eliminates the issue of phone speed and turning the phone on.

There is Google Actions integration for Node Red, but it is not very simple and I have not done it yet.

I have a Google Home for more than 2 years, but had not done integration yet. It is yet to come

+Sascha Bürk Thanks for letting me now. I must have missed it.