Thanks @kellanist. I'll take a look.

I hoped Microsoft would whitelist apps signed by my code signing certificate by now. Maybe I'm missing something.

If it's new, I think it must be because I recently renewed my certificate.

EDIT: I submitted the agent to Microsoft just now, so hopefully they'll whitelist it soon. Otherwise I just have to wait for its reputation to build as users install it.

This is what I saw when I submitted the agent installer:

"The SmartScreen warning that you reported indicates that the application and/or certificate used to sign it do not yet have a reputation established in our system. Applications without a known reputation will show warnings when downloaded or installed. This does not prevent users from still clicking through to download or run the application. To do so, they can select "More info" -> "Run anyway" option within SmartScreen prompt window.

Reputation is established by how your download is used by Windows, Edge, Internet Explorer users and the SmartScreen Service intelligence algorithms. Downloads are assigned a reputation rating based on many criteria, such as download traffic, download history, past anti-virus results and URL reputation.  This reputation may be based on the downloaded program or can also be assigned to the publisher, based on digital certificate information.

Once your signing certificate has gained reputation in our system, all applications or releases signed with your certificate should have warn-free experience"

@Kevin-0, it should work now, but only if you have a paid ChatGPT "plus" subscription or greater.

To add the TRIGGERcmd MCP server (https://www.triggercmd.com/mcp) to your ChatGPT account:

1. Enable development mode here: https://chatgpt.com/#settings/Connectors/Advanced
   

2. Go here: https://chatgpt.com/#settings/Connectors
   

3. Click "Create app" and set it up like this:
   

I paid for the ChatGPT plus upgrade and tested it:

Old behavior:
Before, the TRIGGERcmd Smart Home Alexa skill/ Google Assistant action logic wouldn't create devices unless the computer had a Voice Name or it was your default computer. Also, devices on your non-default computers always had " on [computer voice name]" appended to them, which is a lot to have to say to Alexa or Google Assistant.

New behavior:
Now you'll get a device with a shorter name (without "on laptop" or something similar) for all commands as long as the command's voice name is unique.
If there are multiple commands with the same voice field value, you'll still get a device, but with a name like "calculator on laptop" assuming the computer has "laptop" as its Voice Name.

Commands with unique voice words create devices (even without computer Voice Name) with the command's voice field value only.
Commands on your default computer always create devices for commands, as long as they have a voice field filled in.
Commands on computers with Voice Name always create devices, but if the short name has a conflict, " on (computer voice name)" will be appended.
Commands with conflicts on non-default computers without Voice Name are skipped

I hope that helps.

Thanks @Kevin-0. Now that you asked, I'll definitely look into it.

@mega_big, on a Raspberry Pi, assuming you installed the agent using these instructions, your commands are in this file:

/root/.TRIGGERcmdData/commands.json

You'll see the default commands in there.

You can run these commands to edit it:

sudo su -
cd /root/.TRIGGERcmdData
nano commands.json

While the agent is running, it will detect changes in that commands.json file and create/remove triggers for those commands in your TRIGGERcmd account. If you mess up the json at all (an extra comma even), the agent will restore the last backup it took. You'll see that in your debug.log.

If you don't want to deal with editing text, you could create a command on your Windows PC using the "GUI Command Editor" then copy/paste the json text of that command from the "Text Command Editor" into your commands.json file.

@JoshuaJSlone, that's a known issue with the windows timeout command. It doesn't work in contexts that don't have an interactive terminal, like when running it via TRIGGERcmd. Here's one method that does work:

start /wait timeout 3

I've also added delays with the ping command like this:

ping 127.0.0.1 -n 2

@jett, you'll need to cancel your subscription from your Paypal account.

@Smart-Communities, why not click that Configure button for your short bookmark, and re-select the computer/command combo?

@Smart-Communities, I think you need to edit your short bookmark and re-select your reboot command.

I suspect maybe you renamed your computer?

I just did that - I added a space between New and Laptop. It made my short bookmark red because it no longer matched the computer name:

Then I fixed it by editing my short bookmark and re-selecting my reboot command:

About your idea to have the ability to view all standard and short bookmarks - it's not possible to show the standard bookmarks because they're not stored in the database. The standard bookmarks use a JWT, which is what makes them so long.

@Smart-Communities the red on the Short Bookmarks page is not showing the online/offline status of the computer. It's telling you that the command/computer combo no longer exists.

For example, I have a command on my DS computer that no longer exists. I probably renamed it.

If you click Configure, it will show you a blank Select Trigger field with a pulldown to re-select something for that short bookmark URL.

About your other questions:

Q: Possible to display short bookmarks on the main " View Triggers" screen?
A: It's currently not possible. How about I move the "Create Short Bookmark" button to the top of the Bookmark page?

Q: Create shorter bookmarks by default?
A: I think there's a legit use case for the original bookmarks. They're meant to be ephemeral - they can expire after a set number of hours. They're also invalidated if the command is deleted or renamed. Short bookmarks are valid as long as the computer name and command name they refer to exist.

Q: If I delete offline devices will they come back if eventually online again?
A: No, so if you delete a computer, you'll need to re-input a token when the agent runs on it again, and it will create a new computer record for it at that point.