@gajahduduk, thank you for testing it.

What MacOS version do you have? I suspect it's v15 (aka Sequoia) because they've made it a little harder to run apps like this.

Fortunately you can work around it with these steps:

Try to run TRIGGERcmdAgent, and click Cancel. Open Security and Privacy in Settings. Scroll down and click Open Anyway next to TRIGGERcmdAgent.

8d330481-1ff6-4f91-a1d8-db92c81036ad-image.png

@Ben-Klinger Awesome. Thanks.

@James-Clark, great! Thanks for confirming you're all set.

@abaratz, you're welcome. I'm glad that worked as a work-around. Thank you for reporting the problem too.

If anyone else experiences this problem, please tell me.

@Russ Sure.

Here is the shell script:

#!/bin/bash
if [ "$1" == "start" ]
then
open -a "Slack"
open -a "Microsoft Outlook"
open -a "Safari"
else
osascript ~/Smarthome/Closeallapps.scpt
pmset sleepnow
fi

And here is the AppleScript for Closeallapps:

tell application "Shortcuts Events"
set theResult to run shortcut "Quit All Applications"
end tell

@Matt-Packwood, in this post you solved it by excluding the /Applications/TRIGGERcmdAgent.app folder from the Sophos scans.

Did that stop working?

@Russ I delete my computer from the trigger and then works the agente but I dont know anycommand not works if you can help me please

Hi @Russ, thanks for your feedback.

I had already read these articles, but I read them again and I didn't get any progress in the sense that I can turn on my macbook screen by sending a magic packet. I saw in this link that it is possible to turn on the screen using SSH, and I even bought an Android app that sends SSH commands, but since I have no experience with scripts, I couldn't make it work either.

I'm using the WolOn app on Android to send wake-on-lan and SSH commands. I am attaching screenshots of the app to shed light on the problem.

Thanks!

photo_2022-12-01 14.09.21.jpeg
photo_2022-12-01 14.09.08.jpeg
photo_2022-12-01 14.22.40.jpeg
photo_2022-12-01 14.09.17.jpeg
photo_2022-12-01 14.09.14.jpeg
photo_2022-12-01 14.09.01.jpeg
photo_2022-12-01 14.08.55.jpeg

Nice job @garym77. I guess it makes sense you'd have to escape the spaces with backslashes.

@Borbo-Letu, you're welcome. If you're still having problems, let me know if I can help.

@juan-carlos-aguilar-marchena, I looked at your account and you don't have any computers associated with it. Maybe you deleted it.

If you close and re-open the agent it would prompt you again for your token, then it will re-create your computer in your account.

After that, please try running the commands using the web interface. You'll want to make sure that works before trying Alexa.

On your cell phone, are you trying to log in with email/password or are you trying to use the Pair code to log it in?

Please try linking the TRIGGERcmd Smart Home skill to your account using this page:
https://alexa.amazon.com/spa/index.html#skills/search/triggercmd smart home/?&ref-suffix=iss_gw

@russ I saw that, many thanks!

@Mike, good, I'm glad you knew to do that. I forget to tell people to change the permissions on bash scripts to make them executable.

I've worked it out... Making an account on the forums is not the same as making an account to use TriggerCMD... Once I realised that then everything fell into place.

@kbnetguy, I answered here:

https://www.triggercmd.com/forum/topic/821/create-trigger-to-use-macos-terminal-to-ping-domain

@Ignacio-Charro, you can select the token and copy it with Cmd + C, and paste it with Cmd + V.

The Cmd button looks like this.