Hello! I was using this script on my laptop and it was working normally. After formatting it this afternoon, I reinstalled everything again and got tcmd to work as it was before, but now it is not reading the battery %, it just keeps activating plugOn all the time regardless of how much battery is left. I don't understand scripts, so I apologize in advance for not being able to provide more information or details. If anyone can help me, I would be grateful. Just to let you know, I followed all the steps described here. I have tcmd utility in the C:\Windows folder, I downloaded BatteryInfoView.exe, I configured plugOn and plugOff in trigger_cmd and in Alexa and even so only plugOn is activated in a loop with Alexa's routines. Oh, and I apologize for having revived the topic. I thought it best to leave everything in the same place.

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

IMPORTANT NOTE on above you must make the sendresult.sh bash script executable. go to terminal and: cd ~/.TRIGGERcmdData/ chmod +x sendresult.sh

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

@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

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

@Al-S, great. Glad that was it.

Calculadora Alicia es una herramienta increíblemente útil para realizar cálculos rápidos y precisos, perfecta para tareas financieras, matemáticas y más. Su diseño intuitivo permite a los usuarios resolver problemas complejos sin complicaciones, ahorrando tiempo y esfuerzo. Si estás buscando una solución confiable, te invito a visitar Calculadora Alicia para explorar todas sus funciones y beneficios.

@Ego95, wakeonlan send a "magic packet" to power on a seperate computer across the same local area network. It does not turn a computer off or suspend it. I think you meant the shutdown command, not wakeonlan because this command would shutdown a Windows computer in 30 seconds: shutdown /s /t 30

@Russ the shutdown comand doesnt work

@gajahduduk, changing the command's voice word might be what fixed it. That deletes and recreates the Alexa device.

@Russ Many thanks. Unfortunately I don't own an Alexa so I'm going to need to find an alternative. I can get GH to speak custom phrases on command using "assistant.command.Broadcast" with Google's Web based Automations script editor but that is just a fixed phrase. Guess I'm going back to Gemini for more ideas! Good to see TC still going strong - I first used it 5 years ago!

@Adroit-Tester2, the background agent on Windows is meant to run commands that don't do anything with the GUI, like this reboot command: shutdown /r /t 1 One benefit is the TRIGGERcmdAgent Windows service runs before you login, so you could reboot the PC even if it's not logged in. Background commands run in the context of the TRIGGERcmdAgent Windows service that runs as Local System, which can be of benefit too because it has full access to your PC and it bypasses UAC. Here's a test command you use try in background mode to verify it's working: echo testing > c:\folder\log.txt I just tried that and it produced the log.txt file when I ran it in background mode. If you want to see the processes run, I suggest you leave them in foreground mode. You could still lock the PC after logging it on if you don't want the developers to mess with them.

@Russ yes it was down for about 2 hours yesterday, now work correctly