@MikeH_Iver, the TRIGGERcmd Smart Home skill only allows turn on and turn off, but you can create an Alexa routine if you want to say something else. You can say whatever you want that will trigger your routine, and your routine will turn the TRIGGERcmd device on or off.

Cheers, I'll try this out

OK - I solved my issue. I was using nano file editor to create token.tkn file. I would then paste the token into the first line and save using CTRL-O. It failed with the above error.

I tried creating the file with cat > token.tkn and pasting the token followed by CTRL-D.

It now works fine. So nano must be putting some invalid character at the end of the pasted token string that 'tcmd' can't deal with. Maybe 'tcmd' could be updated to check for this?

Thanks!

@CheddarLifeForm, I'm sure I can move the text below the icon within the widget. I'll do that and see if that helps.

EDIT: I created a new version (v1.0.7) but I'm waiting for Google to review it. The new version includes your other request too - it has a pulldown to select a trigger from your account instead of having to type it in.

@CheddarLifeForm, yes that's a reasonable ask. I like the idea of a list to pick from better than using the voice names. I'll work on it.

@CheddarLifeForm, for security reasons, I built TRIGGERcmd so you can only change commands if you have access to the computer itself. That said, I suppose deleting commands doesn't add much of a security threat. Adding or changing commands would, but not deleting.

@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