@Brad-Magri-Olson, thank you for reporting the issue. I'm on version 1.0.54 and so far I'm not able to reproduce the issue. Can you try upgrading to 1.0.54? I tried downgrading my agent and I still couldn't reproduce it. Also, can you tell me what background command you're running? Also, what antivirus software do you use? I wonder if that's killing the service.

@David-Coulson, I fixed it. Now you won't get these "TRIGGERcmd - Your command didn't run" emails if the trigger was from Home Assistant. [image: 1767926942339-05213127-87ef-4be4-8f7a-ca4b3ae145f3-image.png] Thanks again for reporting the problem.

@Russ Thanks!

@Yoni, thanks for letting me know. I'll make it case-insensitive in the next version.

I use CMDNOWND for this. https://dennisbabkin.com/cmdnownd/ You pop it in the cmd line like this: cmdnownd "D:\Libraries\Documents\batchfile.bat" and it suppresses the appearance of the cmd window. Just place the exe in your path. I keep it in the Windows folder itself. [image: 1767628367785-scrsht_cmdnownd.png]

@Russ Awesome! Thank you so much. Hopefully OpenAI will support your submitted app!

@Russ Done - works like a champ now - thanks again!

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. [image: 1766530798934-0cde63ea-3d0e-4b4a-b6e0-13c398ae26ef-image.png] 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"

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

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

@Russ because I never clicked that and had no idea what it does. It worked. Now it shows the full name of the PC and the indicator is black. I appreciate the help Russ. Have a good weekend and a happy Thanksgiving.

@JRSF-Home, sorry, I forgot (again) that timeout command doesn't wait if the script is running in a context that doesn't have a console, like when the TRIGGERcmd agent runs it. It just moves on immediately. This chatgpt session explains it: https://chatgpt.com/share/691cf13c-2f64-8004-8b12-78dd516285a9 You can see here that another user had the same problem. My suggestion is to use the ping command like this: ping 127.0.0.1 -n 3 Adjust that 3 number depending on how long you want to wait. Here's my improved script that uses ping to wait, and it uses CTRL-SHIFT-J to go directly to the Console tab: "C:\Program Files\Google\Chrome\Application\chrome.exe" --new-window https://www.youtube.com/watch?v=1I9qC0Zo_PM ping 127.0.0.1 -n 5 REM x y width height nircmd win setsize stitle "Allow friends to control Spotify" 200 100 800 1000 nircmd win activate stitle "Allow friends to control Spotify" REM open dev tools to the Console tab nircmd sendkeypress ctrl+shift+j ping 127.0.0.1 -n 3 REM type document.querySelector('like-button-view-model button[aria-label*="like"]').click() nircmd sendkeypress d o c u m e n t 0xBE q u e r y Shift+s e l e c t o r Shift+0x39 0xDE l i k e 0xBD b u t t o n 0xBD v i e w 0xBD m o d e l spc b u t t o n 0xDB nircmd sendkeypress a r i a 0xBD l a b e l Shift+0x38 0xBB Shift+0xDE l i k e Shift+0xDE 0xDD 0xDE Shift+0x30 0xBE c l i c k Shift+0x39 Shift+0x30 REM press enter nircmd sendkeypress 0x0D ping 127.0.0.1 -n 2 REM close dev tools nircmd sendkeypress F12 Here's a video of it working on my laptop: https://youtu.be/p-uJ8j1__zw

@hondaru2004, here's a powershell script that will create a new computer in your TRIGGERcmd account. It assumes you installed the agent on the master PC you cloned because it uses the token.tkn file from that install for authentication. It writes the computer ID and computer name to the config files in the user's home directory. I hope this helps. # === Configuration === $urlprefix = "https://triggercmd.com" $computername = $env:COMPUTERNAME # Read token from TRIGGERcmd token file $tokenPath = Join-Path $env:USERPROFILE ".TRIGGERcmdData\token.tkn" if (Test-Path $tokenPath) { $token = Get-Content $tokenPath -Raw | ForEach-Object { $_.Trim() } Write-Host "Token loaded from: $tokenPath" -ForegroundColor Green } else { Write-Host "Error: Token file not found at $tokenPath" -ForegroundColor Red Read-Host "Press Enter to exit" exit 1 } # === Perform the POST request === Write-Host "Making API request..." -ForegroundColor Green $headers = @{ "Authorization" = "Bearer $token" "Content-Type" = "application/x-www-form-urlencoded" } $body = "name=$computername" try { $response = Invoke-RestMethod -Uri "$urlprefix/api/computer/save" -Method POST -Headers $headers -Body $body # === Display the full response === Write-Host "`nAPI Response:" -ForegroundColor Yellow $response | ConvertTo-Json -Depth 10 | Write-Host # === Extract and save the ID === $computerId = $response.data.id if ($computerId) { # Save ID to TRIGGERcmd config file $computerIdPath = Join-Path $env:USERPROFILE ".TRIGGERcmdData\computerid.cfg" $computerNamePath = Join-Path $env:USERPROFILE ".TRIGGERcmdData\computername.cfg" # Ensure the directory exists $triggerCmdDir = Split-Path $computerIdPath -Parent if (!(Test-Path $triggerCmdDir)) { New-Item -ItemType Directory -Path $triggerCmdDir -Force | Out-Null } # Save ID to file $computerId | Out-File -FilePath $computerIdPath -Encoding ASCII -NoNewline # Save computer name to file $computername | Out-File -FilePath $computerNamePath -Encoding ASCII -NoNewline Write-Host "`nExtracted ID: $computerId" -ForegroundColor Cyan Write-Host "ID saved to: $computerIdPath" -ForegroundColor Green Write-Host "Computer name saved to: $computerNamePath" -ForegroundColor Green } else { Write-Host "`nError: Could not find ID in response" -ForegroundColor Red } } catch { Write-Host "`nError making API request:" -ForegroundColor Red Write-Host $_.Exception.Message -ForegroundColor Red } Write-Host "`nRequest completed." -ForegroundColor Green Run the script with a command like this: powershell -ExecutionPolicy Bypass -File .\change_tcmd_id.ps1 Or, you could just delete the computerid.cfg file and it will prompt you for the token like when you first install the agent.

@Simon thanks again for reporting the error. I'll see if I can reproduce it. It looks like it's in the Home Assistant integration. Sorry about the trouble. EDIT: I see from your screenshot that this.computer_name was null for some reason, so I added code to prevent a crash when that happens. I'll produce a new version soon. https://github.com/rvmey/TRIGGERcmd-Agent/commit/b54e988e7d251105bc6faa8c3fa6a5240644cbef EDIT2: Done - please upgrade to the current version (v1.0.52) to avoid that error in the future.

Thanks @Xander .

@Zaydel-Jiménez, please confirm, you're seeing the "A break point has been reached" error during Windows shutdown? If so, can you get a picture of that error like Furkan did, it might help me. Also, if it happens every time or only once in a while it would also help me to know that. I couldn't find the old 1.0.48 version but I don't think it will be any better in terms of that error than the latest version 1.0.50 because it contains the same code I thought would fix it. It's a tricky problem to fix because I can't reproduce it myself. FYI, these are the version notes: https://www.triggercmd.com/forum/topic/14/triggercmd-agent-versions

Thanks @Frederick1337 !