@tigor, great. I'm glad it's working.

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

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

@tigor, I cut my command down to just this, and tested.

I wasn't able to reproduce the issue. Alexa stopped listening right after she spoke that short sentence.

@davidcook, let's focus on making commands sync with your Raspberry Pi first.

Did you use these instructions when you setup your Raspberry Pi?

If you install the background service with this command:

/usr/share/triggercmdagent/app/src/installdaemon.sh

... it runs as root, and reads /root/.TRIGGERcmdData/commands.json, and it will only sync your background commands (ground = background) not foreground commands.

If you're editing your /home/pi/.TRIGGERcmdData/commands.json that could be the problem.

Please show me the output of this command: systemctl status triggercmdagent
I'd like to confirm it's running.

Also, do you see the your Raspberry Pi listed on your "Your Computers" page? If not, maybe it didn't create a computer because you're not subscribed. You can only have one computer if you're not subscribed.

@tigor, How long is your sentence?

I tested this command with the conversational skills (TC, TRIGGERcmd, and Trigger Command) and it said all 56 of these sentences:

Here's my command if you want to test it yourself:

%USERPROFILE%\.TRIGGERcmdData\sendresult.bat "This is a lot of words 1. This is a lot of words 2. This is a lot of words 3. This is a lot of words 4. This is a lot of words 5. This is a lot of words 6. This is a lot of words 7. This is a lot of words 8. This is a lot of words 9. This is a lot of words 10. This is a lot of words 11. This is a lot of words 12. This is a lot of words 13. This is a lot of words 14. This is a lot of words 15. This is a lot of words 16. This is a lot of words 17. This is a lot of words 18. This is a lot of words 19. This is a lot of words 20. This is a lot of words 21. This is a lot of words 22. This is a lot of words 23. This is a lot of words 24. This is a lot of words 25. This is a lot of words 26. This is a lot of words 27. This is a lot of words 28. This is a lot of words 29. This is a lot of words 30. This is a lot of words 31. This is a lot of words 32. This is a lot of words 33. This is a lot of words 34. This is a lot of words 35. This is a lot of words 36. This is a lot of words 37. This is a lot of words 38. This is a lot of words 39. This is a lot of words 40. This is a lot of words 41. This is a lot of words 42. This is a lot of words 43. This is a lot of words 44. This is a lot of words 45. This is a lot of words 46. This is a lot of words 47. This is a lot of words 48. This is a lot of words 49. This is a lot of words 50. This is a lot of words 51. This is a lot of words 52. This is a lot of words 53. This is a lot of words 54. This is a lot of words 55. This is a lot of words 56."

Do you see your whole sentence in the Runs list for your command?

@Gustavo-Rios, you can't run any commands on a computer that's suspended because it's not connected to the Internet.

You might be able to wake it up from a separate computer on your network though.

Thanks @tigor

@tigor, thank you for reporting this. I was able to reproduce the issue.

I fixed it just now. Please try again.

@jett, no there's no lag - the changes should show up immediately. I think you're running the foreground agent, so make sure your commands are foreground commands. They'll disapear if you make them background commands and you're not running the background agent.

Thanks for telling me about the Google Sign-in button not working on that phone. I just tried it on mine and it worked. I'll research that phone, but in the meantime, did you get it logged in using one of the other methods like a password or a pair code?