@user01010, I'm working on getting an iOS device so I can take some screenshots, but in the meantime you can look at the screenshots above, and change these things:

Remove the "authorization" header Add "token" under Request Body and paste your token from the Instructions page in as the value. Remove the } and { characters. Optional: change computername and triggername to computer and trigger.

Example:
computer=macbook
trigger=calculator
token=(token from the instructions page)

@Xander, thanks for reporting these details. Sounds like there might be an issue with the Alexa Smart Home device discover process. I'll do some testing.

@oloryn, please try this - put a space in the Voice Reply field for the command.

That tells Alexa or Google Assistent to say nothing.

@Russ Stripe.com has the ability to do yearly subscriptions.

@Lewis-S, "sleep PC" isn't a valid format. You could say, "Alexa, ask triggercmd to run sleep on PC". It needs that on word to split the command from the computer.

@Russ I see.

It works, but the command is not working when it gets executed, as the ""s are being interpreted.

I guess I'll have to use script files after all.

Thank you very much!

Edit: (split)

Hi Russ,

It runs fine if I run it from a prompt, but does seem to be getting caught up on the curls, which it has not previously.
I'll have to look at that, I'm doing some network changes so that's probably not helping.

log.log does seem to appear after running it via TriggerCMD.

Thanks again!

It's all working now. Thank you!

@kellanist, wow 2 minutes is a long time. Way too long. I just tested and it's immediate for me. I saw your chat. I'll answer more there..

@dsc3507, please tell me more. Are you looking for an easier way than this to install the agent on Arch linux?

@Baptiste-Patry said in Problem "Please unlock your device" on Alexa...:

Please unlock your device

I did some googling and it seems you might have a pin enabled on your Alexa? Or you have children's accounts with access to your Alexa?
https://www.reddit.com/r/alexa/comments/9mp5gg/show_mode_makes_me_unlock_device/

It doesn't seem to have anything specifically to do with TRIGGERcmd - I think you'd have this problem working with any smart home devices via Alexa.

@kellanis, the delimiter is %20

@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