Awesome @Vinicius-Gimenez-Figuerola. Thanks for letting me know it's working for you.

You could have Claude run a command each time it finishes a prompt.

One idea: turn a light green when it's finished, and turn it red when it's working on something.

I tend to use the notepad command when I test parameters.

[repo path]\.claude\settings.json:

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "mcp_tool",
            "server": "triggercmd",
            "tool": "run_command",
            "input": {
              "computer": "New Laptop",
              "command": "Notepad",
              "parameters": "started"
            }
          }
        ]
      }
    ],
    "Stop": [
      {
        "hooks": [
          {
            "type": "mcp_tool",
            "server": "triggercmd",
            "tool": "run_command",
            "input": {
              "computer": "New Laptop",
              "command": "Notepad",
              "parameters": "done"
            }
          }
        ]
      }
    ]
  }
}

I updated the Roku app. Now it groups commands by computers, or panel buttons by panel.

Reminder, the app shows computers and commands if this checkbox is unchecked on your profile page:

It shows panels with their panel buttons if you check the checkbox.

FYI @mlabombarda

@Pierce-Ó-Brádaigh the 10 minute delay is a spam prevention mechanism. most spammers will not wait. these are the attempted logins of spammers for the last several days. It's gone as high as 1300 in the past

@Vinicius-Gimenez-Figuerola if you rename your command, and rename it back, it will re-create the Alexa device with this new UI option to disable the doorbell press notifications. Does that solve it? I tried to default it to false, but there doesn't seem to be a way to do that.

@Vinicius-Gimenez-Figuerola , interesting. What triggers that routine? I would think the command couldn't trigger it because it would be too late. I'll try it.

EDIT: I tried it - that works, but I don't want everyone to have to do that for every command, so I'm still looking for a solution. Worst case, I could make the doorbell feature (for running routines) a toggle for each command, and default it to false.

EDIT2: I added a feature to each device to allow you to disable the "Doorbell Press Notifications".

@Vinicius-Gimenez-Figuerola, I noticed the same thing yesterday. When I trigger a new or changed command via the virtual Alexa Smart Home device, my Echo device says, "Ding dong, someone is at [voice word]." Old commands are not affected.

For now, I set my Alexa device to "Do Not Disturb" so I don't hear the announcement like this article suggested:
https://www.amazon.com/gp/help/customer/display.html?nodeId=GV7ZJNSWKL8E3D7T

I'm looking into what changed. I think Amazon changed something recently because I didn't change anything related to the doorbell feature. You probably know this, but the doorbell feature is needed to trigger an Alexa routine when a command runs.

It doesn't have anything to do with the Voice/MCP Reply field. The TRIGGERcmd Smart Home Alexa skill doesn't use it. Only the legacy conversational Alexa skills (called TRIGGERcmd, Trigger Command, and TC) use it.

I opened a case with Amazon about it.

@Pierce-Ó-Brádaigh, I'll refund your money. If you use Paddle instead of Paypal to re-subscribe, you can cancel the auto-renewal and it won't immediately stop your subscription benefits.

Use this prompt in claude code to produce a dashboard artifact like this:

Create a claude.ai Artifact that's a control-panel dashboard for my TRIGGERcmd connector — it lists all my TRIGGERcmd commands, grouped by computer, and lets me run any of them with an optional parameter, right from the page.

Before writing any code:
1. Load the artifact-capabilities skill and read the mcp.d.ts type definitions for the current runtime contract — follow that contract exactly, don't rely on remembered API shape.
2. Find my TRIGGERcmd MCP tools (they'll appear as mcp__<connector>__list_commands and mcp__<connector>__run_command or similar). Actually call list_commands, and actually call run_command once (e.g. trigger a harmless command like a Calculator command) to observe the REAL response shape — TRIGGERcmd tools return plain text, not JSON, so you'll need to parse that text yourself rather than assume structured JSON.
3. Note: the manifest `capabilities` you pass to the Artifact tool uses the connector name segment from the tool's internal name (e.g. "claude_ai_TRIGGERcmd"), which gets auto-resolved to the display name at publish time. BUT the actual `window.claude.mcp.callTool()` / `watchTool()` calls inside the page's JavaScript must use the connector's real DISPLAY NAME (e.g. "TRIGGERcmd"), not that internal segment — using the segment at runtime causes a `not_in_manifest` error even though the manifest itself is correct. Get this right the first time.

Dashboard requirements:
- Use watchTool for list_commands (it's a read, should stay live/refreshable) and callTool for run_command (it's an action, fire on click).
- Parse the text response into computer → [commands] groups; each command may have a voice-trigger label and/or a description (commands with descriptions typically accept a text parameter).
- Layout: sidebar or nav of computers with command counts, a search box that filters across all commands, collapsible groups per computer, and a Run button + optional parameter input per command.
- Show a live activity log (e.g. fixed panel) of triggered commands with pending/success/error status, since these are fire-and-forget hardware/device triggers with no persistent state to poll.
- Handle MCP failure states distinctly per the type definitions — don't collapse everything into one generic error banner: distinguish "connector not connected/needs reauth" (show a reconnect message) from "temporarily unavailable" (offer retry, keep last-good data visible) from "not available in this context" (full-page fallback, e.g. when window.claude.mcp is undefined).
- Design it as a real control-panel UI (dark/light theme aware, decent typography, not a default Bootstrap-y look) — apply the artifact-design skill's guidance for a UI/dashboard treatment.

Publish it as a shareable Artifact with an appropriate favicon.

Then you'll find this and other artifacts here: https://claude.ai/artifacts

@Hannibal said in Error while installing the triggercmdagent:

Notice: Download is performed unsandboxed as root as file '/home/hannibal/downloads/triggercmdagent_1.0.1_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

Copy/paste that into ChatGPT to know why, but you can safely ignore that "Notice". Basically it means the _apt user doesn't have access to your user's home directory where the .deb file is, so it's using root to access it instead.

It looks like the agent is installed now, so you can move on to the next step:

node /usr/lib/triggercmdagent/resources/app/src/agent.js --console

It should prompt you for a token which you can copy/paste from the Instructions page while logged in at https://www.triggercmd.com