@Frank-Malczewski For anyone reading this post, we solved the problem.

Before I followed the instructions above for sharing my computer with my wife (creating a triggercmd account for her and sharing my computer), I had tried to add her to MY triggercmd account by going on HER phone to HOME / SETUP DEVICE / WORKS WITH GOOGLE and linked to TriggerCMD Smart Home, which it accepted. But after following Russ' process for sharing the computer, neither of us could use Google to turn stuff on or off.

What I had to do is DISCONNECT TriggerCMD Smart Home on HER phone, then reconnect it so it picked up her new triggercmd.com account. You cannot have two people trying to access the same account.

Problem solved and now we both can talk to Google to turn lights on and off.

Thanks Russ for working with me on this...

EDIT: I see that Russ also posted that we solved this! We must have been typing at the same time...

@Russ Just an update - I have not 'noticed' TRIGGERcmd failing since I started running the script daily. I do occasionally see multiple icons in the system tray that vanish if I hover over them - not sure if they stay after I run the script or if TRIGGERcmd crashed, then my script ran within that 24 hr window and started TRIGGERcmd back up but whichever it is, it has not been an inconvenience .

Thanks.

@Russ OK. Thanks. As previously mentioned, I am now running that script nightly. Hopefully, even if I get a failure it will be short-lived.

@Russ Well, for some odd reason Triggercmd stopped today and I found the following error message which was nothing like the previous failures:

Might this have been a fluke with Triggercmd stopping or is it related?

I also think I am going to increase my task scheduler (to stop and restart TRIGGERcmd) to run every day instead of once per week...

@Russ Will see if that helped. Thanks.

@Russ results:

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\windows\system32>

@Russ Use that command where? In the scheduled task?

UPDATE - never mind - you meant to run it from a CMD prompt

@Russ Hi Russ. Well, its been a couple of months without any issues UNTIL yesterday, when I noticed I couldn't trigger any lights and checked my server to find:
If you remember, I set it up to restart every week on Sunday.

I also saw that multiple (3) TRIGGERcmdAGents were showing in the system tray. I had to acknowledge the error and manually restart it.
Was wondering if you had any other users seeing this happen since spring.

Thanks

Frank

@Russ OK. I just made that change. Lets see if the recent changes helps. I'll be in touch...

@Russ Hi Russ. Yes, we did that a while back.
This is under the AntiVirus scan section. Is there another area to look as well?

@Russ Hi Russ,

I have not changed any setting for page file. When I go to that setting location for Virtual Memory, it was set to AUTO, so I turned it off and set 2048 as the initial size and 8192 as the MAX.

I am running Norton 360 Premium.

And I will add that task.

Thanks, and sorry again for the delay. Been very busy.

Frank