@Gabriel-Martins you could try the new version I just released, but I don't have confidence it will solve that error.

Do you have admin access on your Windows PC? What Antivirus do you use?

@D0llyy, yes there are many tools for many OS's that can send the magic packet to wake up another computer.

Windows: https://www.nirsoft.net/utils/wake_on_lan.html
Mac: https://formulae.brew.sh/formula/wakeonlan
Ubuntu: sudo apt-get install wakeonlan

@Mariana-Castro, if you didn't save your c:\Users\(your user)\.TRIGGERcmdData\commands.json from your previous Windows load, you've lost your commands.. You should delete your computer from your TRIGGERcmd account so you can recreate it from your new Windows load.

For security reasons, TRIGGERcmd does not store the actual commands in the cloud - they only exist on your computer in your commands.json file.

@Luigi-Marco-Silvestrini, I think I fixed it but I'm not 100 percent sure because the error showed up so rarely. Please upgrade to the latest version (1.0.36), and please tell me if you ever see the error again.

Thanks @Javier-Juarez, I'll look into Binance. I tried adding Stripe but they cancelled me after a couple weeks because a customer claimed they didn't subscribe.

@Mauro, there's no built-in way to open the GUI Editor using a command, but if you want I could build it into the next version of the agent.

I remember you did it this way, so I assume you're looking for a simpler/cleaner method.
https://www.triggercmd.com/forum/topic/2716/macro-to-open-triggercmd-gui?_=1718324644863

@Luise-Fernandes, I'm not sure, but please try deleting this folder, then re-run the "TRIGGERcmd Agent" app.

c:\Users\luise\.TRIGGERcmdData

@Ben-Klinger Awesome. Thanks.

@James-Clark, great! Thanks for confirming you're all set.

@Joao-victor-0 That's not TriggerCMD causing the problem, it's another device connected to your PC that's causing it to power back on. If you run the command outside of TCMD, it will do the same thing.

Try unplugging your USB devices and see which one is reawakening your PC.

@boblewis, that all sounds good. Do you have any remaining problems or are you all set now?

@Russ Thanks!

@tuicemen

You can add house code (A-P) and unit codes (1-16) as parameters in your bash scripts.

#!/bin/bash
house_code=$1
unit_code=$2
action=$3
curl "http://url:port/api/HomeAutomation.X10/${house_code}${unit_code}/Control.${action}"
Run it like this:
./control_x10.sh A 4 On

This way, you only need one script.

Thank you
boblewis

@DarkGreen92, great. You're welcome. Thank you for your patience.

@northyen-0, if you leave the computername blank, it will use the Windows computer name.

By automatic sign up, I wonder if you mean you want to install the agent automatically? If so, that's possible. You can find a script in this article.

@Petter-Cardoso, thank you for telling me it's working. I didn't do anything, so maybe it was a temporary problem on Amazon's side.

If you're not using the TRIGGERcmd Smart Home skill, I recommend switching to it, or at least try it to see if you like it better. I find that it works better. And you say, "Alexa, turn on Calculator" to run a command instead of the longer sentance, "Alexa, ask TRIGGERcmd to run Calculator."

@Michell-Laureano, I translated, "eu sou inscrito ja nao consigo nem importar minhas config ja" as "I'm registered and I can't even import my settings anymore."

I'm assuming you're talking about your commands. Your commands are stored in the commands.json file which is in your c:\Users\(your user)\.TRIGGERcmdData folder. You can copy that file, or use the Text Command Editor to copy the text and paste it into a different computer.

Also you said you registered. If you mean subscribed, I looked and your account does not seem to be subscribed yet, so you can still only have 1 computer.

@abaratz, you're welcome. I'm glad that worked as a work-around. Thank you for reporting the problem too.

If anyone else experiences this problem, please tell me.