@Russ It appears the service doesn't want to startup properly now. I have to manually start it up myself. Currently it's set as Automatic. and abort sleep isn't being discovered by my alexa.

Awesome @Eduardo-Lezcano, that's good progress. There are two reasons the voice commands wouldn't show up on the website: The voice field for the computer is empty. Use the Edit button on the website to fill that in. The voice field for the command is empty. Use the commands.json to fill that in ("voice":"firefox"). Can you verify both of them have a word in them? For a Raspberry Pi I like to use the word "pie" in the computer's voice field because it's what Alexa or Google Assistant think you're saying when you say Pi.

@Rafael-Requena, you were probably using the skill where you say, "Alexa, ask TRIGGERcmd to run X on Y". That works already. The newer skill where you say, "Alexa, turn on X on Y" doesn't work yet where Y is a computer someone shared with you. EDIT: Both Alexa and Google Assistant Smart Home skills work with shared computers now.

@bignoob, does it work if you run the command yourself, in a cmd window? You can copy that chromedriver exe into a new folder, then add that folder to your PATH environment variable, or just copy the exe into C:\windows folder which is already in your PATH by default.

@LR2, that's not possible right now, but I think I could add that as a feature. I'll look into it.

@fcovalls, that's odd. It worked for me as a background command. It should work because background commands run in the context of the TRIGGERcmdAgent Windows service which runs as Local System, which should allow elevated commands to run. This is what I see in the log when I ran it via TRIGGERcmd: D:\tools>type chkdsk.log The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 1139968 file records processed. File verification completed. 6948 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 725 reparse records processed. 1477194 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 725 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 168614 data files processed. CHKDSK is verifying Usn Journal... 37970336 USN bytes processed. Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 732469247 KB total disk space. 614040080 KB in 964604 files. 410280 KB in 168615 indexes. 0 KB in bad sectors. 1267367 KB in use by the system. 65536 KB occupied by the log file. 116751520 KB available on disk. 4096 bytes in each allocation unit. 183117311 total allocation units on disk. 29187880 allocation units available on disk.

@TheValkyrieAsh, I think your best bet is to watch some of the Youtube videos. If you got the TRIGGERcmd agent installed, you should be able to right-click the tray icon in the lower right near your clock, and select "GUI Command Editor". You'll probably have to click the up arrow to reveal the tray icon. Please let me know how it goes.

Perfect, i contact you in a few days when i do the test hahaha Thanks for all! :D

@ecki, this is the command to start PowerPoint: start powerpnt Or, if you want to launch a particular PowerPoint file, use this command: start powerpnt "c:\Users\russe\Documents\TRIGGERcmd Presentation.pptx" Or, use the /s parameter to start the presentation in a full screen slide show like this: start powerpnt /s "c:\Users\russe\Dropbox\Public\TRIGGERcmd Presentation.pptx"

@Terry-King, no, but that's a good idea. I'll work on that - hopefully tomorrow. EDIT: It's done: https://youtu.be/Iv6ifjHyWF4

Awesome, got it working. Thank you.

@racoon1211, no offence taken. People worry about who's behind the software they install on their computers - for good reason. It's always been an issue for TRIGGERcmd. I tried to help that by publishing the source code for that software, but that only helps a little. Thanks for talking about TRIGGERcmd on Facebook.

@EL-Dirtbag, I'm actually surprised you can use this to type more than a short sentence. I think Google Assistant has a timeout of only a few seconds. That said, you could have your script type two enter keys at the end (or beginning), so each time you invoke the script via TRIGGERcmd, it would create a new paragraph.

On win10 Im using: usoclient ScanInstallWait

@Byron-Trantham, sorry about the extra work but I'm glad you have a solution now.

@jbeckmantx, using the word ON with the normal google action ( as opposed to the newer TRIGFERcmd Smart Home action) has often been a problem because the word ON is used as the delimiter between the trigger name and the computer name (calculator on downstairs). I've tried to train Google's AI to handle that but it's still an intermittent issue. If you haven't tried the TRIGGERcmd Smart Home action, you really should. That's the best solution for thing you turn on and off.

it's ok after change tokken