@kellanist, sweet! I'm glad that worked out.

@buaamm, so far I've added Japanese support for TRIGGERcmd Smart Home - both Alexa and Google Assistant.

Would you mind testing? Please tell me if I got anything wrong.

@Russ said in Timeout not working in TRIGGERcmd:

echo %1 >> c:\tools\params.log

That is exactly what is happening...and I can't find a way to get her to pass a number instead of text...she just takes the first word after "parameter". I may have to just go with a number of set durations for the timer...thanks for your help.

@rtn17, awesome. You're welcome.

@Forbidden-Duck, that's good. I hope it stays working.

@Russ Thanks for that. Indeed, beaten by the comma. Thanks for the help.

@edbgsk, a command like this should work. I shared my printer with a share name of "xerox".

print /d:"\\mycomputer\xerox" c:\docs\test.pdf

@Lucas-Soares, no, Internet access is necessary, sorry.

@LR2, I added this feature just now.

Now you'll get an email if you try to run a command on an agent that's not connected.

Smart Home -> Devices, then scroll to the bottom of that screen and select Forget All, then Discover.

Works great now! Thanks for your help!

@F4u5t, here's an example to watch a folder for new files, and call the IFTTT webhook.

$watcher = New-Object System.IO.FileSystemWatcher $watcher.Path = 'D:\folder_to_watch' $watcher.IncludeSubdirectories = $true $watcher.EnableRaisingEvents = $true $action = { $path = $event.SourceEventArgs.FullPath $changetype = $event.SourceEventArgs.ChangeType Write-Host "$path was $changetype at $(get-date)" $postdata = @{ value1=$path value2=$changetype } # To get your key, click the Documentation link at https://ifttt.com/maker_webhooks/ $key="your_ifttt_key" $event="new_file" $json = $postdata | ConvertTo-Json $response = Invoke-RestMethod "https://maker.ifttt.com/trigger/$event/with/key/$key" -Method Post -Body $json -ContentType 'application/json' write-host $response } Register-ObjectEvent $watcher 'Created' -Action $action "Waiting for events. Press CTRL-C to quit." while($true) { Start-Sleep .5 }

Obviously I can not run GUI programs as root. Background triggers work fine and do the job anyway. Thank you

Awesome @Rafael-Requena. Thanks for letting me know it's working.

@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.

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.

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