Google Home Notifier

Devices & Integrations
#21

Read the installation instructions for the Pi. They recommend a change on the config. I had this same problem until I did the change and then worked.

#22

I did, tried it all twice. Based on the instructions in this posted issue, I did the following:

sudo apt-get update
sudo apt-get upgrade
curl -sL https://deb.nodesource.com/setup_7.x | sudo -E bash -
sudo apt-get install nodejs:
sudo apt-get install git-core libnss-mdns libavahi-compat-libdnssd-dev

Then cloned project and ran npm install

Then modified vi node_modules/mdns/lib/browser.js

Then modified example.js replacing Google Home with name of my device, Kitchen Home

#23

Did you do this?

After ā€œnpm installā€

Modify the following file ā€œnode_modules/mdns/lib/browser.jsā€

vi node_modules/mdns/lib/browser.js
Find this line:

Browser.defaultResolverSequence = [
rst.DNSServiceResolve(), ā€˜DNSServiceGetAddrInfoā€™ in dns_sd ? rst.DNSServiceGetAddrInfo() : rst.getaddrinfo()
, rst.makeAddressesUnique()
];
And change to:

Browser.defaultResolverSequence = [
rst.DNSServiceResolve(), ā€˜DNSServiceGetAddrInfoā€™ in dns_sd ? rst.DNSServiceGetAddrInfo() : rst.getaddrinfo({families:[4]})
, rst.makeAddressesUnique()
];

#24

Yes

(10 characters)

#25

In example.js did you try setting the name to one of the ā€œGoogle-Home-xxxā€ strings listed in the debug? I couldnā€™t get my friendly names to work but those internal names work for me.

#26

Same here. The default worked but my own name didnā€™t.

#27

Youā€™re talking about the ā€œGoogle-Home-clasmlc939hr3anfp9aw393fjwhateverā€ name thatā€™s in the output? I have not tried that, I use the ā€œKitchen Homeā€ name that I assigned through my Home app. Iā€™ll give this a try when I get home. Thanks for the idea :slight_smile:

#28

I used the original name from the config which I believe was ā€œGoogle-Homeā€.
I tried changing it and wasnā€™t working and I rolled back to original and
workedā€¦

#29

That was it guys, thanks. I used the long name Google Home-lknasclascon9f38903jf0w93f and itā€™s working now. Thanks!

#30

@Ev1l5anta did you say in another thread that you had this working through CoRE? Iā€™m trying to get it set up but it looks like CoRE can only do JSON and FORM content, while google-home-notifier seems to require application/x-www-form-urlencoded content. If itā€™s working for you, how did you set up?

#31

It does work. I will check and send what I used.

#32

You should use FORM. You need to initialize a variable with a value which you will use. I created multiple with something like text=whatever I want it to say

#33

Can you post a screenshot by chance? I have been trying to send variables and itā€™s not working.

Hereā€™s the piston setup. The variable text is set to value of Hello:

Screenshot_20170112-070524.png1440Ɨ2560 139 KB

Hereā€™s the console log. No data between the brackets:

Pasted image770Ɨ127 17.3 KB

Hereā€™s what Wireshark shows as the incoming request. Note that the format is [variable name]=[variable value]

For comparison, hereā€™s what I see when using the example cURL with the -d (application/x-www-form-urlencoded) content request.

Request:

Pasted image1179Ɨ40 2.85 KB

Console log:

Wireshark:

Pasted image874Ɨ54 15.6 KB

Pasted image736Ɨ140 20.2 KB

I tried using cURL to send a FORM request instead of the encoded request and it responded the same as my CoRE piston above.

A screenshot of yours would be really helpful if you donā€™t mind.

#35

When I execute this -> curl -X POST -d ā€œtext=Hello Google Homeā€ https://ae474203.ngrok.io/google-home-notifier I get the following output on my Pi:

{ text: ā€˜Hello Google Homeā€™ }
Device ā€œGoogle-Home-76475acb66ca2e7225c2d03247435263ā€ at 192.168.1.141:8009
Device ā€œChromecast-41a5b7694d0677c433d89bf2058b0c6eā€ at 192.168.1.136:8009
Device notified

When you initialize the variable, it should be called text and the content on the variable content field.
It should not be text= or text:, just text

This should work even though I have not been able to test now. Give it a try.

#36

Unless Iā€™m misunderstanding, what you are describing is exactly what I had posted above. My variable name is ā€œtextā€ (without the quotes), and the variable value is ā€œHelloā€ (without the quotes).

As far as I can tell, the issue is that CoRE is sending the ā€œtext=Helloā€ as part of the URL (which it should not be doing in a POST request), whereas cURL is sending correctly as part of the request body.

CoRE request:

cURL request:

#38

Got this working - awesome. Thank you all for this thread, it really helped.

#39

Can you share how you got your CoRE settings so it can help others? Iā€™m traveling and cant play to get the settings good again to share.

#40

Iā€™m getting exactly the same results as @destructure00

#42

Second time that Iā€™ve had to delete my post, lol. I got core to work. The literal name of the local variable must be text. Then the raw value will be what you want it to say. Other then that is post and form. Iā€™m using the internet URL with the port forwarded to my rPi

#43

Unless Iā€™m misunderstanding you, thatā€™s exactly what Iā€™m doing (except Iā€™m sending it over my local intranet). Hereā€™s my piston:

Can you post a picture of your piston for comparison?