@VeepuEco try this example: https://www.pcworld.com/article/3100057/how-to-remove-your-login-password-from-windows-10.html

i use this. the computer have password, but when you lok the pc and need to unlok you need to put password.
but on start you don't need to put password. so if you have this option on and when talk with google assistent to power pc on, the pc enter on windows without password

in my case but i dont know how to setup my google home to turn on my pc

ps: sorry my english. i dont talk and write english very much

@Oliver-Oßwald, awesome.

@Lewis-S, I see a "Apply always" option on your screenshot. That might prevent it from deleting the .exe. You could also exclude that folder from scans.

@meetb, the commands.json file gets created in the home folder of the user who runs the agent.

On a Raspberry Pi I generally run the background service (daemon) as root because I'm dedicating the Pi to be a garage door opener, PiHole, or using it to wake up my PC. So I use /root/TRIGGERcmdData/commands.json and all of my commands have ground = background.

It's possible though that you might want to run X-Windows on your Pi and run the agent in foreground mode as pi, in which case you'd use the commands.json in pi's home folder.

Your commands.json file will be restored if the agent detects a problem in the json format, like a comma on the last entry, or if you forget to escape a quote or backslash. It restores the last valid commands.json file it had.

@meetb, I just tested using both the original Alexa skill (Alexa, ask TRIGGERcmd to run Calculator on PC), and the newer Smart Home Alexa skill (Alexa turn on Calculator on PC). Both skills worked for me. PC is a shared computer from another account. So I have some questions:

What exactly are you saying to Alexa? Have you verified your computer's voice name matches what Alexa is hearing?

You can use https://alexa.amazon.com to see what Alexa is hearing. In my case, for the original skill to work I had to make the voice name "p. c." because at https://alexa.amazon.com I saw this:

Alexa heard: "alexa ask trigger c. m. d. to run calculator on p. c."

@krl69, what is your browser's language? It might be a bad redirect for your language.

Thank you for telling me about this. I need to fix it.

Can you get to these links?
https://www.triggercmd.com/user/auth/signup
https://www.triggercmd.com/user/auth/login

Where do you live (in the world)?
Also, can you send me that full URL? The q=... value got cut off. That might give me a clue about what's going on.

@Russ said in Backup And Migrate Trigger Commands:

~/.TRIGGERcmdData/commands.json

Thank you!

@Pietro-Gonçalves, do any of your commands work? I suspect the problem might be that you set the command to be a background command?

If you do that, your commands will run in the foreground via GUI editor, and they'll run the background when you run them remotely. You also have to have the background agent installed for background commands to run remotely.

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