Announcement

Collapse
No announcement yet.

Would like to trigger an event through the power off button

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Would like to trigger an event through the power off button

    Dear all,

    I have had the plug-in for about three weeks and I am happy with the way it works. I have created a few events that are triggered by an activity and that works well.

    However, I can't seem to setup an event that is triggered when the power off button is pressed on the remote (I basically want to cut the power to one of the devices when the power off button is pressed).

    Does anyone know how to poll this power off to trigger an event?

    #2
    You should be able to do the basic homeseer event: "If [device] changes and becomes [value]" trigger to do this.

    So, for mine it would be "If Living Room Harmony changes and becomes PowerOff"

    I have built in a special trigger as well which lets you chose when the power off begins or when it is completed (see screenshot).

    The trigger is called "MeiHarmonyHub: Power Off.." and the two sub triggers are "Power off is starting" (as soon as you press the button) and "Power Off is complete" (when the hub reports everything is off).

    If these aren't working for you, let me know and I'll double check them.
    Attached Files

    Comment


      #3
      Hi Frank, thanks for the quick reply. Can you tell me how you created this special trigger? Looks good and I'd like to use it like you do

      Comment


        #4
        Originally posted by mroovers View Post
        Hi Frank, thanks for the quick reply. Can you tell me how you created this special trigger? Looks good and I'd like to use it like you do
        I added it to the plugin (i'm the Author of the plugin).

        If you go to your events page and when you select a trigger, you should see one called "MeiHarmonyHub: Power Off.." next to the "IF" (or "AND IF").

        If you don't let me know what version of hte plugin you are running. It might be that you need to run the beta. If you don't want to run the beta, you can still do my first suggestion of using the built in trigger and sub trigger "A devices values is..."->"A devices value changes and becomes"

        Comment


          #5
          Hi Frank,

          I just upgraded to version 3.0.3.12 and I can see the trigger now, thanks!
          However I noticed that whenever I click on power off on the app on my smartphone, the hub disconnects:

          Jun-01 17:01:29 Warning I/O interface MeiHarmonyHub is down, executable is not running, restarting ...
          Jun-01 17:01:04 Info Plugin MeiHarmonyHub with instance: has disconnected

          Any idea how that could happen?

          Comment


            #6
            Originally posted by mroovers View Post
            Hi Frank,

            I just upgraded to version 3.0.3.12 and I can see the trigger now, thanks!
            However I noticed that whenever I click on power off on the app on my smartphone, the hub disconnects:

            Jun-01 17:01:29 Warning I/O interface MeiHarmonyHub is down, executable is not running, restarting ...
            Jun-01 17:01:04 Info Plugin MeiHarmonyHub with instance: has disconnected

            Any idea how that could happen?
            Go to the settings for the plugin and on the last tab check "Debug logging". Try and reproduce it and once you have you can go to

            /Logs in your HS install directory and get the MeiHarmonyHub.log file. Then just post it here and I'll see what it says.

            Comment


              #7
              Hi Frank,

              This is the contents of the log file:

              2018-06-01 17:20:28,063 DEBUG [4] HSPI - Settings changed. Saving settings
              2018-06-01 17:20:28,078 DEBUG [4] HSPI - It took 2ms to save the settings (HSPI_MeiHarmonyHub.Classes.Settings) to file
              2018-06-01 17:20:30,688 DEBUG [11] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Heartbeat success for hub 63aaded0-75df-4288-3b91-baf8e550ab95
              2018-06-01 17:21:00,703 DEBUG [11] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Heartbeat success for hub 63aaded0-75df-4288-3b91-baf8e550ab95
              2018-06-01 17:21:30,721 DEBUG [11] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Heartbeat success for hub 63aaded0-75df-4288-3b91-baf8e550ab95
              2018-06-01 17:21:32,136 DEBUG [17] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Hub 63aaded0-75df-4288-3b91-baf8e550ab95 had its sleep timer updated from -1 to -1
              2018-06-01 17:21:32,141 DEBUG [17] HSPI - Hub with ID 63aaded0-75df-4288-3b91-baf8e550ab95 has started activity 25832479
              2018-06-01 17:21:38,612 DEBUG [13] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Hub 63aaded0-75df-4288-3b91-baf8e550ab95 had its sleep timer updated from -1 to -1
              2018-06-01 17:21:38,617 DEBUG [17] HSPI - Hub with ID 63aaded0-75df-4288-3b91-baf8e550ab95 is starting activity 25832479
              2018-06-01 17:21:38,632 DEBUG [11] HSPI - Hub with ID 63aaded0-75df-4288-3b91-baf8e550ab95 had it's activity updated to 25832479
              2018-06-01 17:21:39,520 DEBUG [13] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Hub 63aaded0-75df-4288-3b91-baf8e550ab95 had its sleep timer updated from -1 to -1
              2018-06-01 17:21:57,210 DEBUG [17] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Hub 63aaded0-75df-4288-3b91-baf8e550ab95 had its sleep timer updated from -1 to -1
              2018-06-01 17:21:57,215 DEBUG [12] HSPI - Hub with ID 63aaded0-75df-4288-3b91-baf8e550ab95 is turning Off
              2018-06-01 17:22:01,083 DEBUG [4] HSPI - It took 35ms to load the knownDevices file into memory.
              2018-06-01 17:22:01,103 INFO [4] HSPI - Updating new settings with defaults. Previous version: 3.0.3.12; Current Version: 3.0.3.12
              2018-06-01 17:22:01,103 DEBUG [4] HSPI - Settings changed. Saving settings
              2018-06-01 17:22:01,143 DEBUG [4] HSPI - It took 35ms to save the settings (HSPI_MeiHarmonyHub.Classes.Settings) to file
              2018-06-01 17:22:01,143 INFO [4] HSPI - Initializing Clients.
              2018-06-01 17:22:01,153 INFO [4] HSPI - Registering Triggers.
              2018-06-01 17:22:01,153 DEBUG [10] HSPI - Hub: 63aaded0-75df-4288-3b91-baf8e550ab95 Connection Attempt 1
              2018-06-01 17:22:01,158 DEBUG [4] HSPI - Registering Triggers
              2018-06-01 17:22:01,158 DEBUG [10] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Attempting to connect to IP: 192.168.1.136 on port 5222
              2018-06-01 17:22:01,158 INFO [4] HSPI - Registering Actions.
              2018-06-01 17:22:01,158 DEBUG [10] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Attempting to get stream on IP: 192.168.1.136 on port 5222.
              2018-06-01 17:22:01,163 DEBUG [10] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Opening stream on IP: 192.168.1.136 on port 5222.
              2018-06-01 17:22:01,163 DEBUG [4] HSPI - Registering Actions
              2018-06-01 17:22:01,163 DEBUG [4] HSPI - Polling Timers: adding timer: DeviceStatusUpdate at pollInterval: 86400000
              2018-06-01 17:22:01,163 DEBUG [4] HSPI - Polling Timers: timer: DeviceStatusUpdate Started
              2018-06-01 17:22:01,163 DEBUG [4] HSPI - Polling Timers: adding timer: SleepTimerUpdate at pollInterval: 0
              2018-06-01 17:22:01,178 DEBUG [10] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Authenticating on IP: 192.168.1.136 on port 5222.
              2018-06-01 17:22:01,508 DEBUG [10] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Initiating Listener on IP: 192.168.1.136 on port 5222.
              2018-06-01 17:22:01,508 INFO [10] HSPI - The Conection to Hub with ID 63aaded0-75df-4288-3b91-baf8e550ab95 was opened
              2018-06-01 17:22:02,503 DEBUG [10] HSPI - Checking if we have a Root device for hub with ID: 63aaded0-75df-4288-3b91-baf8e550ab95
              2018-06-01 17:22:02,503 DEBUG [10] HSPI - Found Root Device for hub with ID: 63aaded0-75df-4288-3b91-baf8e550ab95
              2018-06-01 17:22:03,463 DEBUG [10] HSPI - Found 0 missing statuses
              2018-06-01 17:22:03,558 DEBUG [10] HSPI - Creating Device Devices
              2018-06-01 17:22:03,583 DEBUG [10] HSPI - Found 0 missing statuses
              2018-06-01 17:22:03,598 DEBUG [10] HSPI - Found 0 missing statuses
              2018-06-01 17:22:03,608 DEBUG [10] HSPI - Found 0 missing statuses
              2018-06-01 17:22:03,618 DEBUG [10] HSPI - Found 0 missing statuses
              2018-06-01 17:22:03,623 DEBUG [10] HSPI - Found 0 missing statuses
              2018-06-01 17:22:03,628 DEBUG [10] HSPI - Found 0 missing statuses
              2018-06-01 17:22:03,628 DEBUG [10] HSPI - Generic Known Hub change
              2018-06-01 17:22:03,638 DEBUG [10] HSPI - It took 12ms to save the settings (HSPI_MeiHarmonyHub.Classes.KnownDevices) to file
              2018-06-01 17:22:07,736 DEBUG [13] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Hub 63aaded0-75df-4288-3b91-baf8e550ab95 had its sleep timer updated from -1 to -1
              2018-06-01 17:22:07,761 DEBUG [11] HSPI - Hub with ID 63aaded0-75df-4288-3b91-baf8e550ab95 had it's activity updated to -1
              2018-06-01 17:22:08,536 DEBUG [13] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Hub 63aaded0-75df-4288-3b91-baf8e550ab95 had its sleep timer updated from -1 to -1
              2018-06-01 17:22:31,207 DEBUG [11] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Heartbeat success for hub 63aaded0-75df-4288-3b91-baf8e550ab95
              2018-06-01 17:23:01,216 DEBUG [11] HSPI - Debug Message for Hub 63aaded0-75df-4288-3b91-baf8e550ab95: Heartbeat success for hub 63aaded0-75df-4288-3b91-baf8e550ab95

              Comment


                #8
                And that last line is the last line after the crash?

                Can you tell me what Hub you are using, what version of HomeSeer, and if after the plugin is "disconnected" from HS, if it is actually still running or of the app has completely crashed (it is HSPI_MeiHarmonyHub.exe in task manager).

                I'ave had some users who had crashes, but they've all stopped with the recent version (the version you are running). Also I will send you a PM so you can email me your config files.

                Comment

                Working...
                X