"Enable/disable/configure multiple monitors on Windows"
https://www.nirsoft.net/utils/multi_monitor_tool.html

MultiMonitorTool.exe /disable \.\DISPLAY3

And, for single monitors, my comment from a year ago still works.

@Espino As other threads will tell you, the Token is found when you log into the main site, under Instructions.
https://www.triggercmd.com/user/computer/create

@russ said in Is server down?:

@cris-silva, @DavidPennington , what's not working? I just tested it and it's working for me.

I know AWS (Amazon Web Services) had problems today, so I wonder if that affected Alexa.

It definitely affected Alexa - every literal Smart device became "unresponsive" (about a dozen) so it's not a stretch that all the figurative (I'm blanking on the right word) ones for TriggerCMD would go offline, too.

Create a trigger that calls Nirsoft.net's NirCMD program. It's got a ton of options. I use it to Mute my system but it does have a SetBrightness option.

https://nircmd.nirsoft.net/setbrightness.html

Set your command to ms-settings:

Google can find you a list of sub commands (e.g. ms-settings:network) for any specific sections.

@mikeh_iver After you installed the software on the other PC, copy the commands.json file from the "C:\Users*username*.TRIGGERcmdData" to the it.

In the discussions here, there is one for setting up TriggerCMD with IFTTT. Works like a charm.
"Alexa, trigger Ubuntu" (I find one word triggers work best but experiment).

@Russ NICE FIND! After only a minute of playing with it, it's near perfect. Only hitch is that the window that keeps getting thrown around has 5 pinned tabs and the tool only seems to recognize the 'Title' of the window with the active tab. That's not the end though because I could have the task scheduler run a batch file with a set of five commands so that one of them will work. It's the only window I keep on that monitor.
Now I just need to figure out the event code for when the USB adapter momentarily craps out so I'll just wait for it to happen again.
Bwahaha!

(Only downside might be if I throw another tab into it for temporary usage. The tool probably won't be able to spot that).

Haven't tried this feature myself but Nirsoft's NirCMD has a "sendkeypress" ability.
https://www.nirsoft.net/utils/nircmd2.html#using

Here's my question though -- how does your VBS script send the keypress to the right window or, on your PC, is F7 being recognized by one program no matter what program is in the foreground?

Nircmd has a WIN feature which lets you activate a window so you could use it twice in a new script, once to activate the window and again to send the keypress.

When I say 'good night' to Alexa, I have been having it run my Hibernate command every night to put my PC to sleep. I got to thinking that sometimes I do want certain programs to run backups, etc. so did a little digging and found this script online.
So, every Sunday night, it -won't- hibernate and will run certain tasks.

@echo off
for /f %%i in ('powershell ^(get-date^).DayOfWeek') do set dow=%%i
if %dow% NEQ Sunday goto shutdown

REM in this area, enter commands for things to run Sunday night (backups, updates, etc)

exit
:shutdown
shutdown /h /f

@Russ Yes, just the .json into a clean install. Seemed safest.

I've un/reconnected the Triggercmd Smart home skill. It re-found the triggers on my less-used other computer but nothing from the new one. After some fiddling, it finally kicked in - I think setting a voice name finally did it.

It was just Alexa -- "triggers work on the PC and from the dashboard here" (this site)

Banana set to run notepad was added into Alexa within seconds. Which got me thinking and what I did was Cut out all my content from my .json, saved, ensure that the triggers disappeared from the Alexa app, repasted them back in, saved, and they all showed up ... AND WORKED.

Thanks for your help.
Saying "good night" to Alexa and having her turn off my monitors (smart plug) and hibernate the PC (trigger) is a big part of my routine.

@Russ Been trying that since last night and now the Alexa app won't rediscover them at all now, "organically" or even when I try to force detection.

@Russ Necroposting as this is pretty much on target for me. Replaced my old computer with a newer one, copied everything over ... triggers work on the PC and from the dashboard here. I've made the new one the default and even deleted the old one but the devices in Alexa aren't triggering. I thought I might need to delete them and let them be rediscovered so I tried that and the newly-discovered ones aren't working.

I'm scratching my head here.

@Greg-Larsen Correct. They are optional should someone want to just use the triggercmd site to set off their actions but absolutely needed for Alexa/Google integration.

@Greg-Larsen If you want to add hardware, a $5 smart plug (Aliexpress) would do the job of your $25 (+hub) suggestion. Set the BIOS to turn on when power is provided and you're done.

I have my three monitors on one smart plug so when I say Good Morning to Alexa, she fires them up. I don't really need WoL so pressing the button is fine with me.

@Joao-victor-0 That's not TriggerCMD causing the problem, it's another device connected to your PC that's causing it to power back on. If you run the command outside of TCMD, it will do the same thing.

Try unplugging your USB devices and see which one is reawakening your PC.

"2021-08-26 19:54:08 Program: About to install to: C:\Users\User\AppData\Local\Discord"
"2821-08 1-26 19:54:21) Apply 21 ApplyReleasesImpl: Updating shortcut C:\Users\User\Desktop\Discord.Ink"

@Igor-Marinho Looks like you're installing Discord, not TriggerCMD.

@matheus-venancio What is the actual command that you're using? And does it work from a cmd prompt?

@Bruno-Rafael Look through recent posts for NirCmd instructions. It can simulate key presses but I don't know that a virtual press will suffice.

If it does, simply create an Alexa routine with both actions (and you'd probably want to throw a Wait command in between)

@Russ Sorry for the delayed reply; crazy week.

Background was the problem on the one part.
On the other, for some weird reason, Task Scheduler was renaming the actual .job from "SCoff" to "SC off" so that the path was wrong. Once I spotted that, I got it working.

Just to check - I've been running the x86 version of TCMD on that PC for...years? Other than the updated .js, there's no newer version? The main DL is x64.