@Rodney-Mathee, I'm glad you told me it's wifi, not wired ethernet. That changes things. For one, that WakeMeOnLan.exe tool from Nirsoft won't work because it doesn't support wireless networks.

I've never tried "wake-on-wlan" but in theory it's possible with the right hardware.
https://documentation.ubuntu.com/core/explanation/system-snaps/network-manager/how-to-guides/configure-the-snap/wake-on-wlan/

@Jhon-Piñeres
The answer is probably found elsewhere since you asked your question, but because this was the first thread i found i think i post my solution here:

Command for shutting down:
shutdown /s /t 120

I choose 2 Minutes because thats the a longer time i need to leave but so normaly enough time to stop if i forgot something.

Off Command:
shutdown /a

Now i can tell my alexa to shut down my pc, by switching on shutdown, but i have also 2 minutes to cancel the shutdown by telling alexa to turn off shutdown.

@Lokilator nice, I've used the shutdown command in the past. I haven't seen that one.

@Pepe-Tops , good to know. I'll test and fix that if I can reproduce it.

@Matt-Packwood, I thought I did produce an Apple Silicon version. Are you saying this version isn't an Apple Silicon version?

https://agents.triggercmd.com/TRIGGERcmdAgent-arm64.dmg

This is one of those old-fashioned Windows batch bugs that only manifests after interactive operations are discontinued.

Your.bat is launched in a non-interactive session by TRIGGERcmd. Even if you say "foreground," there isn't a true console connected, so anything that thinks it's a tty may silently misbehave. The reason your script gets beyond taskkill but never reaches the restart is because TIMEOUT is infamous for its ability to either quit instantly or block strangely when there is no interactive terminal.

it also explains why there isn't a window: Unless you specifically force a visible cmd.exe session, TRIGGERcmd is not generating one.

Avoiding TIMEOUT in this situation is the solution. It spins up its own process with a suitable wait handle, thus wrapping it with start/wait works. For the same reason, ping 127.0.0.1 -n X works; console state is irrelevant. If you really want to view output, using cmd /c or cmd /k manually is a good alternative.

Additionally, ensure that the program.exe is launched using the whole path rather than just the working directory. Since C:\Windows\System32 is often used as cwd when triggers execute, relative paths will fail silently.

In summary, it's not a TRIGGERcmd problem or a permissions issue. Batch + non-interactive Windows execution is used. It will act the same as if you ran it locally if you change the TIMEOUT and use complete paths.

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

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

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"