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

Update: For anybody on the Apple ecosystem, I just used a workaround to solve the iOS ST developer mode problem. I installed the Android Studio on my Mac and used it to emulate an Android phone. I then installed Smartthings on the emulated phone and was able to enter developer mode to link to TriggerCMD.

@Mateo-Fernandez, yes, unfortunately you'll need to make it faster. Alexa only gives a few seconds before a reply must be returned to Alexa, so TRIGGERcmd has to impose the same time limit.

@Emanuel-Esteves, in your user profile folder, there's a subfolder called .TRIGGERcmdData, for example:

C:\Users\russe\.TRIGGERcmdData

In that folder there's a commands.json and a computerid.cfg file. If you put the ID of the old computer in the computerid.cfg file, it will login as that computer. The commands.json file contains your commands, so if you still have a copy of that, you'll be able to restore your commands. Otherwise, you'll need to rebuild your commands. When your computer logs in, it synchronizes the commands in commands.json with the computer record in your TRIGGERcmd account.

To find the ID of your old computer, you can click View Triggers for that computer, then you'll see the computer ID in the browser URL:

44363ede-f14b-41a3-891c-131f4deefc66-image.png

I hope this helps. Sorry if this means you lost your commands and you need to rebuild them. At least you have a list of them in your account in the old computer record.

@Thiago-Soares, which Alexa skill did you link? You need to link the TRIGGERcmd Smart Home skill for Alexa devices to appear for each of your commands. Your commands also need to have the voice field filled in. Your computer also needs the voice field filled in or it needs to be your default computer. You can set your default computer in your profile.