@tim-s and @meyerdenney, yea I wish they didn't do that. Alexa's doing it now too, so I suspect there's some legal reason for it. I'm guessing it's to let users know this is a third party, not a Google service you're about to hear from.

I was research this and came across this pretty thorough blog post.
https://www.androidpolice.com/2018/02/10/ultimate-guide-google-home-tips-tricks-understanding-making-assistant-speaker/

I learned a few things from it, including that other people are annoyed by the multiple voices issue too:

"Assistant apps talk back to you in a different voice than the one you're used to hearing from your Google Home. It's jarring at first, but Home will respond with, "Alright, getting X," and another voice will come up and tell you what this particular app/service can do and will continue answering you until you're done with it and want to go back to the regular Home voice and commands..."

I also found this reddit post from a year ago that says Google Assistant will stop saying, "Alright, getting X" after you've been using X for a while. Unfortunately that hasn't been my experience.
https://www.reddit.com/r/googlehome/comments/80efhh/google_home_stopping_talkative_introduction_to/

I also noticed Alexa doesn't always say "Ok here's TRIGGERcmd, ..." For instance if I say, "Alexa, run calculator" she doesn't, so maybe if the command is short enough she doesn't say it.

@russ Thanks a lot, this worked. I shouldn't've assumed it would always run in the home directory. This saved me a lot of headaches.

I got it working. It turns out that when you add a TRIGGERcmd command to the Webcore device list on your SmartPhone (Webcore > Settings > Available Devices), you have to scroll way down the screen to the Switches section. Normally most devices will show up at the top in the Actuators section.

@hellomiakoda, when I uploaded the .deb file last time I updated it, apparently I forgot to make it public.

@hellomiakoda, thanks for telling me. Please try again. It should work now.

@russ Thanks! I will try it

Just tried it out and it works! Thanks!!

@jebus-jones, please try again. It should work now. I'm sorry it took so long to fix. I put some details about the problem here:

https://www.triggercmd.com/forum/topic/399/is-the-goolge-home-triggercmd-app-working

Please disregard. I figured out that I had to remove the current listed PC in the web console, and then it allowed me to add token.

@thecussen, awesome. Thanks for sharing your use case.

This makes a lot of sense (because most of the "on" commands are the ones experiencing issues. I'm at work now, but will modify the commands when I return home and post the results. Thanks again for your assistance.

UPDATE: The issue is resolved. Removing the "on" from the end of the voice field fixed the problem. Thanks again!

hello all

i have now figure it out how to fix this issue, i will give you the solutiont, if the administrator thinks its not really an issue please delete this whole topic.

turns out i had to go to smartthings gui and delete the smartapp from "my smartapps tab", i was just deleting the switch and the smarthome app from smarthings, but for some reason the smartapp just kept the old token and not the new one when i add my computer again in the triggercmg website

i figure this out by consulting live logging on the smartthings gui.

its all working now, thanks 🙂

@mats-gloppen, that might be due to your antivirus software. Can you try disabling AV and running the TRIGGERcmd agent again? It probably just needs to be disabled during the first run.

Also, which antivirus software do you have?

@russ Thanks for checking. GA could do everything else but claimed it just couldn't get a "response" from TriggerCMD, everything was good on my end too. The next morning GA connected to T CMD just fine with first request when I woke. Was certainly temporary. I think almost 17 months with T CMD and had never had anything like that happen before while I still had internet at my house. I've had internet down before and GA usually responds by telling me it can't reach internet. I've gotten spoiled leaving lights on way to bed and saying my "All Lights Off" command as I pull the blankets up. Kinda sucked to grab my old bedside x10 rf remote that hasn't been used in over a year to find the batteries dead too... lol. Had to climb out of bed and do it the old fashion way. Life was rough that night like it was back in 2009... 🙃 😆

@anon-qwerty, can you un-quarantine it? I'll add this to my todo list to try to prevent it. Hopefully I can.

@djmalcom, I used to have the SmartThings code immediately turn the switch back on every time you turn it off, so effectively it's always on. I left the line that did that remarked out. Just un-remark (remove the //) that off() line.

// handle commands def on() { log.debug "Executing 'on'" sendEvent(name:"switch",value:on) parent.on(this) // off() }

https://github.com/rvmey/SmartThingsPublic/blob/MSA-2199-2/devicetypes/vandermeyconsulting/triggercmd-switch.src/triggercmd-switch.groovy

@stevef9432203, no, but you could change this line to set your "homedir" to something else.

homedir = (process.platform === 'win32') ? process.env.HOMEPATH : process.env.HOME;

Or maybe you could symlink your ~/.TRIGGERcmdData folder to a path on your hard drive.

@cableghost, the SmartThings integration can run a command on your computer, but you can't use the integration to trigger anything in SmartThings - it's a one-way street from SmartThings to TRIGGERcmd servers to your computer.

Does EventGhost run a command to turn your lights on or off? If so, you should be able to run the same command with TRIGGERcmd.

@russ Thank you for your quick response. I tried installing the node-legacy but no change. I can trigger from the site and from SmartThings but no commands run. I am running Raspian OS.

Should i have uninstalled the npm nodejs first before installing the npm nodejs-legacy?

EDIT: For others reading this thread, we found that the Raspberry Pi version 2 runs a very old version of node js, and the latest version of the TRIGGERcmd Pi agent uses a function that requires a newer version.

We downgraded the agent to this one and it works fine (and still supports parameters) http://triggercmdagents.s3.amazonaws.com/triggercmdagent_1.0.1_all_pi2.deb

EDIT 2: I updated the Raspberry Pi version so now the latest version it works fine on a Raspberry Pi2.