This is a limitation of the SmartThings system in general when developers (like myself) combine the parent and child app into one code base. However, it should not impact you creating and using the app. When you enter the app it should take you to the main menu, NOT the last scenario. If it does, however, simply press the < button in the upper left to go back to the main menu.
This is unlikely to get fixed per SmartThings as the way the single codebase is implemented actually goes against SmartThings standards. However, from a developer standpoint (and giving instructions to end users) it is MUCH cleaner and is why we continue to use this method. When it stops working we will all need to go back to the dual code method…until then the exit after done is a issue we all choose to live with.
I don’t think you can use the goodnight Google wording…Would probably be “OK Google, turn on night mode” with a virtual switch called “night mode”…That should work fine as that is how mine is set up.
I’ve set up a IFTTT using “Good Night” as the phrase (“Hey, Google, Good Night.”) that trips a virtual switch that runs the SmartThings Good Night routine routine.
Rube Goldberg would be proud!
Works fine - Google Home doesn’t seem to mind using “Good Night” to kick off the IFTTT action.
Also have a “Good Morning” IFTTT.
Oddly, I wanted to use “nite nite” as the phrase to initiate my IFTTT action (I entered that in the IFTTT as the first/preferred phrase), but Google Home persistently refuses to launch my IFTTT action on that phrase, and just says good night back to me when I say Nite nite. Haven’t been able to figure that one out.
Good feedback, thanks! I think I tried “Night night” as well as “Nite Nite” but I’ll give it a try and confirm. Night night is just a lot more fun to say.
May also try Nightie night as well, to see if that is less confusing.
[Edit] Just checked, I did have “nighty night” in the IFTTT and that wasn’t working. Changed to “Nightie night” (“nightie” is an actual word, I think “nighty” isn’t used/recognized as commonly) so maybe will work better?) and will try that after brunch.
Someone created a Google Home Notifier that allows you to push text to speech and announcements to Google Home. I’m no dev but thought you could port this to Smartthings as a Smartapp. Here is the Github link for his code if you’re interested: https://github.com/noelportugal/google-home-notifier
@MichaelS I am trying to use GHH to send http requests to my Kodi installation. I can get it to work as long as I don’t have a username and password specified on the Kodi web server side. I’d really like to have the ability to set user/password though, is there a way to add this ability to internal HTTP requests? Format is as follows:
I’m also trying to make sense of Cloud Interface, if I’m understanding correctly it would make a publicly available URL that would trigger a switch when the URL is called, correct? What would be the difference between this and directly turning a switch on or off through Google Home integration?
This functionality would be so awesome. I have been using this app for a month now along with IFTTT to setup custum voice commands for my whole house. I’ve had smart lights and switches in my house for a year or so but adding the GH integration has really made shine. My wife is finally warming up to it also. Thanks for the great app
You can review your google account activity to see what google actually thinks you said. That might help with knowing which spelling google is using as well as what its interpreting you saying.
I know I’ve been hijacking your thread with this Google Home TTS wish I have but just an update of my tests.
I tried the Google-Home-Notifier NodeJS application by noelportugal. Installed it on a Raspberry Pi and the way it works it’s mainly a listener that sends TTS to Google Home… if you do a URL POST to the listener it will send a TTS command to Google Home.
The listener listen on HTTP if on local network so no problems with HTTPS. I have zero dev skills otherwise I would try to create a Smartapp that you can set when something happens then do a POST to the listener with the text you want Google Home to speak.
Even though this works well and easy with IFTTT, IFTTT service creates a big delay that is annoying… the ideal would be to have this as a Smartapp so you don’t have to deal with the delay.