@ricardomat, awesome. You're welcome.

@mark-hollis, thanks. I thought I had it fixed this morning and found out just recently it went down again. Working on it again now.

@barry-hamilton, @Ricale-Kincheski, @k8nr, @marcelo-muller, @Moacir-Vilela-Sêga, thank you for reporting the problem. I do see I had a problem in the logs. I'm looking into it now.

@russ goodness! I rest easy knowing that there is no need to log in or issue any commands.
Thank you!!!

@renan-hugo, please try this:

Run which gulp to get the path to the gulp command. Like this:

russ@russmac % which gulp /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp

Then make your shell script something like this:

#!/usr/bin/env bash cd /Applications/XAMPP/xamppfiles/htdocs/cative/wp-content/themes/cative/gulp/ /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp assistir > /tmp/output.txt 2>&1

For some reason you need to specify the full path to the executables you install via npm i -g. That's been my experience on Mac anyways.

If that doesn't work, please try running the gulp script like this:

node /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp

Or even like this:

/Users/russ/.nvm/versions/node/v8.17.0/bin/node /Users/russ/.nvm/versions/node/v8.17.0/bin/gulp

To do that last one, you'll need the full path to your node executable which you can find with this command:

which node

@riccardo-cereser, please try adding this to your script:

SCRIPTDIR=$(dirname "$0") cd $SCRIPTDIR

That way you can specify the full path to your script in the commands.json file, and when your script runs, it will cd to the directory where your script is.

@russ I added the password to pi-hole and generated the token from web API. New URL that appeared with that token has been added to the TriggerCMD. However, this still doesn't resolve the problem, I am receiving the same message with empty token. Can anyone help with the issue? Where to dig further? Thanks

@russ Thank you for that information!

@jakesmith46001
thanks, it worked very well

@alexander-cleary,

I'm trying to reproduce the problem myself. I setup my Windows laptop the same way - to not go to sleep when I close the lid (while plugged in to AC power). Hopefully I can reproduce the problem you see. I'll know in about an hour. So far I know it's working because I see the "Command ran" entries in the runs list.

Also if you haven't already done it, could you see whether leaving the lid open makes a difference?

EDIT:
I waited more than an hour and the TRIGGERcmd agent on my laptop is still responding.
f7c92b55-e3a6-4787-9219-9e280cb52f4a-image.png

My laptop is Windows 10. Is yours Windows 11 by chance?

Thanks for the reply. At first I did have the other skill activated, but then I realized it wasn't that one, and activated the other one. In the end the problem was that I did not have the computer assigned as Administrator, now that I have assigned it, it has detected the devices, thank you so much

@russ thank you for your fast reply. I really appreciate it. The firewall was blocking the commands indeed. If I try use them before login, everything works properly. But after login, when the firewall comes up, every command stop working.

@oscar-mro Hello friend, here on my machine, it is not clicking on Tab and space

@matúš-maron, no problem. I'm glad you figured it out.