Categories

• Announcements

  Announcements regarding TRIGGERcmd

  66
  Topics
  180
  Posts

  

  I'm always looking for new ways to automate my workflows, and this looks like a great way to do it. The ability to create widgets that trigger commands is really cool, and I'm looking forward to trying it out. I'm sure it will make my life a lot easier.

• General Discussion

  A place to talk about TRIGGERcmd

  556
  Topics
  2723
  Posts

  

  @karnold69 I stopped using windows for my X10 control some time ago. But prior to that I know I had disabled windows driver updates and that solved issues with windows updates for me.
  Another option is to use software for X10 that doesn't use X10WTI CM15A drivers.
  Things that use Mochad or Mochad itself, or HomeGenie that has it's own drivers(which I use)

• Example Commands

  A place to share commands you like to trigger remotely.

  Raspberry Pi

  Mac

  Windows

  Linux
  322
  Topics
  1264
  Posts

  

  start Disneyplus:

• Instructions

  Instructions for each operating system, and various scenarios.

  API

  Google Home

  Alexa

  Mac

  Linux

  Raspberry Pi

  Windows
  191
  Topics
  907
  Posts

  

  @Russ That works, thank you!

• Blog
  10
  Topics
  19
  Posts

  

  @Arnold-Martinez-Castillo, I don't have Call Of Duty Warzone, but I did figure it out for World of Warcraft, so I think you could the same method to find the .exe file, and run it directly.

  I opened Task Manager's Details tab and sorted by the CPU column, then I opened World of Warcraft from the Battle.net app. The top CPU user was Wow.exe.

  e7f4d927-3970-4155-b3a2-bfffa228ac2a-image.png

  I right-clicked Wow.exe and clicked Open file location.

  ddc7c038-6f8c-49f6-9b28-d221923b9d36-image.png

  That showed me the full path to Wow.exe.

  bb5ac33b-36a9-471a-9c9e-18890bb04faf-image.png

  Now I can launch it with this command:

  "C:\Program Files (x86)\World of Warcraft\_retail_\Wow.exe"

  9067d346-4f9c-4e28-9d39-985ec887e37c-image.png