TRIGGERcmd
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Having issues with a new trigger

    Scheduled Pinned Locked Moved General Discussion
    1 Posts 1 Posters 2 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • StrahanS Offline
      Strahan
      last edited by Strahan

      Hello!

      Went to bed last night and realized I left my encrypted drive mounted. Grumbled, got up, turned on monitors, dismounted. Then it hit me when I was back in bed; why not make a dismount trigger so I can have Alexa do it for me? Yay, laziness FTW lol.

      So I just remembered that so I went to implement. I have TC running on my domain controller downstairs but the drive in question is up in my main rig. My encryption software has no remote listening capability so I was going to use psexec but I haven't had great luck with that. So my next thought was make a C# Windows service with a socket server and then serialize a JSON payload and shoot it to the service and it can deserialize that and get the drive info to dismount from the payload and do it.

      Then I said wait wait wait nerd; why not just install TC agent on the rig?? Much easier lol. So I did that and created a new trigger:

      Trigger: dismount drive
      Command: wscript.exe c:\misc\xd.vbs
      Off Command: wscript.exe c:\misc\xd.vbs
      Ground: foreground
      Voice: dismount drive
      Voice/MCP Reply: Drive dismounted
      MCP Tool Description: (not set)
      Allow Parameters: true
      Quote Parameters: false
      Icon: (not set)

      When I saved, 5 seconds later my phone beeps with a notification from Alexa that a new smart home device was discovered. Cool. But then I realized the verbiage will be weird saying to turn on or off a verb so I changed the name to just "drive" and again, I get the alert saying device discovered. So I say "Alexa, turn off drive". I had turned on parms and set the cmd both as on and off because to dismount a drive it felt weird saying turn ON drive lol. But no dice.

      So I tried just c:\misc\xd.vbs since VBS can be launched directly. The only reason I did wscript first was habit from batch files anyway. Still no love. So I made xd.bat which is just:

      @echo off
echo Hi! >c:\misc\debug.log

      Again, no love. Then I realized it has 0 for the run counts so it isn't registering at all. Alexa did detect "drive" though? So my question (if you're still with me after this novel lol) is

      1. Is there any issue having TC agent running on two machines? I would 99.999999999% be sure not since the interface supports showing multiple.
      2. Did renaming it perhaps break something? Can't imagine why though
      3. Any other things you can think of that may be at issue?

      Thanks a lot!

      1 Reply Last reply Reply Quote 0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      • First post
        Last post