Announcement

Collapse
No announcement yet.

Plugin sometimes doesn't see motion

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

  • Plugin sometimes doesn't see motion

    Really the only issue I have with HS3 is that sometimes my Envisalink DSC events don't see that there has been motion. For instance, lights turn off after a certain amount of inactivity in a room. I will walk into a room, turn the lights on and they immediately turn off again because the plugin hasn't registered motion. I can do a little dance and turn turn the lights on several times before things work. It is possible that the issue is on the DSC/Envisalink end but I don't think so. I used this hardware with a MCV Vera for a while and never once had these issues.

    Also with the Vera if I turned a light off, say on the way out of a room, it would sense my leaving the room and immediately turn the light back on again. Doesn't happen most of the time with this plugin and HS3. This really isn't an issue because it was a problem before. Having to rely on the motion sensor and timers to turn lights off is ridiculous when you have already hit a switch.

    I have tried to set the log to debug but every time I do the events work the next attempt.

    Not sure what to do.
    Originally posted by rprade
    There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

  • #2
    I am not seeing this problem S-F. It must be just you or maybe your imagining the problem. If nobody else is seeing it then why should HS fix it? I mean like the Zwave problems you are not seeing why should this be any different?

    Comment


    • #3
      Wow.

      Stooping to a new low.


      Will a mod (Rupp? Not sure who are the mods. Learning the ropes) please whack this and the preceding post?

      And does this forum have a feature to allow the blocking of posts by specific members? I can't seem to find it.
      Originally posted by rprade
      There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

      Comment


      • #4
        Originally posted by S-F View Post
        Wow.

        Stooping to a new low.


        Will a mod (Rupp? Not sure who are the mods. Learning the ropes) please whack this and the preceding post?

        And does this forum have a feature to allow the blocking of posts by specific members? I can't seem to find it.
        Just a taste of your own medicine. You state my problems are trivial and should be ignored because you are not having them so well yours are trivial to me and others not having them.

        You don't like the feeling of people saying your problem with HS is unimportant well stop saying other peoples problems are insignificant and should be ignored. We all paid a lot of money.

        I hope Rich sees this so he fixes your problem I really do. But you need to respect other people. Had you not done what you did I would have not posted more than 3 times today. Your posts pissed me off because you act like its no big deal to have to constantly redo the whole setup. Well if it ever happens to you like it does to many others you will probably change your mind.

        Comment


        • #5
          Originally posted by S-F View Post
          Really the only issue I have with HS3 is that sometimes my Envisalink DSC events don't see that there has been motion. For instance, lights turn off after a certain amount of inactivity in a room. I will walk into a room, turn the lights on and they immediately turn off again because the plugin hasn't registered motion. I can do a little dance and turn turn the lights on several times before things work. It is possible that the issue is on the DSC/Envisalink end but I don't think so. I used this hardware with a MCV Vera for a while and never once had these issues.

          Also with the Vera if I turned a light off, say on the way out of a room, it would sense my leaving the room and immediately turn the light back on again. Doesn't happen most of the time with this plugin and HS3. This really isn't an issue because it was a problem before. Having to rely on the motion sensor and timers to turn lights off is ridiculous when you have already hit a switch.

          I have tried to set the log to debug but every time I do the events work the next attempt.

          Not sure what to do.
          Can you try to keep the log level to Debug for a while, so that when it happens again we can see if the plugin gets the info about the movement?

          Comment


          • #6
            How do you set the plugin to debug mode? I select debug from the dropdown but the setting doesn't persist after I leave the page. When I navigate back to the config page for the plugin info is set again.
            Originally posted by rprade
            There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

            Comment


            • #7
              Originally posted by S-F View Post
              How do you set the plugin to debug mode? I select debug from the dropdown but the setting doesn't persist after I leave the page. When I navigate back to the config page for the plugin info is set again.
              the log level setting should persist, it is written to the EnvisaLink.ini everytime you change it.
              It works for me with HS version 3.0.0.125, but I know some users have reported some problems when writing to ini files. What version of HS are you running.

              Alternatively you can set the log level to Debug manually by adding the following lines to EnvisaLink.ini and then restart the plugin

              Code:
              [general]
              log_level=Debug

              Comment


              • #8
                Does this help? I turned the light off and then did a little dance. The light didn't come back on.

                Oct-27 2:39:03 PM EnvisaLink DEBUG ZoneRestored 038
                Oct-27 2:39:02 PM EnvisaLink DEBUG ZoneRestored 037
                Oct-27 2:39:02 PM EnvisaLink DEBUG ZoneOpen 038
                Oct-27 2:39:01 PM EnvisaLink DEBUG ZoneRestored 038
                Oct-27 2:39:00 PM EnvisaLink DEBUG ZoneOpen 038
                Oct-27 2:38:55 PM EnvisaLink DEBUG ZoneOpen 037
                Oct-27 2:38:55 PM EnvisaLink DEBUG ZoneRestored 036
                Oct-27 2:38:45 PM EnvisaLink DEBUG ZoneOpen 036
                Oct-27 2:38:44 PM EnvisaLink DEBUG ZoneRestored 036
                Oct-27 2:38:43 PM EnvisaLink DEBUG ZoneOpen 036
                Oct-27 2:38:43 PM EnvisaLink DEBUG ZoneRestored 036
                Oct-27 2:38:39 PM Z-Wave Device: Basement Laundry Area Laundry Area Light Set to Dim 98%
                Oct-27 2:38:37 PM Z-Wave Device: Basement Laundry Area Laundry Area Light Set to Dim 70%
                Oct-27 2:38:35 PM Z-Wave Device: Basement Laundry Area Laundry Area Light Set to 255
                Oct-27 2:38:35 PM Device Control Device: Basement Laundry Area Laundry Area Light to On Last Level (255)
                Oct-27 2:38:35 PM Event Event Trigger "Occupancy Management Laundry Area Motion Regular"
                Oct-27 2:38:35 PM EnvisaLink DEBUG ZoneOpen 036
                Oct-27 2:38:35 PM EnvisaLink DEBUG ZoneRestored 037
                Oct-27 2:38:30 PM EnvisaLink DEBUG ZoneOpen 037
                Oct-27 2:38:29 PM EnvisaLink DEBUG ZoneRestored 037
                Oct-27 2:38:28 PM EnvisaLink DEBUG ZoneRestored 038
                Oct-27 2:38:26 PM EnvisaLink DEBUG ZoneOpen 038
                Oct-27 2:38:26 PM EnvisaLink DEBUG ZoneOpen 037
                Oct-27 2:38:25 PM EnvisaLink DEBUG KeypadLedStatePartition1Only 91
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 8
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 7
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 6
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 5
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 4
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 3
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 2
                Oct-27 2:38:25 PM EnvisaLink DEBUG TroubleLedon 1
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionisBusy 8
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionisBusy 7
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionisBusy 6
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionisBusy 5
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionisBusy 4
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionisBusy 3
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionisBusy 2
                Oct-27 2:38:25 PM EnvisaLink DEBUG PartitionReadyForceArmingEnabled 1
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 064
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 063
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 062
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 061
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 060
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 059
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 058
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 057
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 056
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 055
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 054
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 053
                Oct-27 2:38:24 PM EnvisaLink DEBUG ZoneRestored 052
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 051
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 050
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 049
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 048
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 047
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 046
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 045
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 044
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 043
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneOpen 042
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 041
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 040
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 039
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 038
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 037
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 036
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 035
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 034
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 033
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 032
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 031
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 030
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 029
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 028
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 027
                Oct-27 2:38:23 PM EnvisaLink DEBUG ZoneRestored 026
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 025
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 024
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 023
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 022
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 021
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 020
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 019
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 018
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 017
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 016
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 015
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 014
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 013
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 012
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 011
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 010
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 009
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 008
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 007
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 006
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 005
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 004
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 003
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 002
                Oct-27 2:38:22 PM EnvisaLink DEBUG ZoneRestored 001
                Oct-27 2:38:22 PM EnvisaLink DEBUG CommandAcknowledge 001
                Oct-27 2:38:22 PM EnvisaLink DEBUG CommandAcknowledge 000
                Oct-27 2:38:22 PM EnvisaLink DEBUG CommandAcknowledge 055
                Oct-27 2:38:21 PM EnvisaLink DEBUG LoginInteraction 1
                Oct-27 2:38:21 PM Plug-In Finished initializing plug-in EnvisaLink
                Oct-27 2:38:21 PM EnvisaLink DEBUG CommandAcknowledge 005
                Oct-27 2:38:21 PM EnvisaLink DEBUG LoginInteraction 3
                Oct-27 2:38:21 PM EnvisaLink DEBUG Request: StatusReport
                Oct-27 2:38:21 PM EnvisaLink DEBUG Request: Poll
                Oct-27 2:38:21 PM EnvisaLink DEBUG Request: TimeStampControl 1
                Oct-27 2:38:21 PM EnvisaLink DEBUG Request: NetworkLogin user
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:42
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:41
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:40
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:39
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:38
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:37
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:36
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:35
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:34
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:33
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:32
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:31
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:30
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:29
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:28
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:27
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:26
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:25
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:24
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:23
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:22
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:21
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:20
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:19
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:18
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:17
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:16
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:15
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:14
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:13
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:12
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:11
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:10
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:9
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:8
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:7
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:6
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:5
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:4
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:3
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:2
                Oct-27 2:38:21 PM EnvisaLink DEBUG Zone Device Found: Z:1
                Oct-27 2:38:20 PM EnvisaLink DEBUG Partition Device Found: P:1
                Oct-27 2:38:18 PM EnvisaLink INFO EnvisaLink version 3.0.0.14
                Oct-27 2:38:18 PM Info Plugin EnvisaLink has connected. IP:127.0.0.1:54698
                Oct-27 2:38:09 PM Plug-In Shutting down Plug-In: EnvisaLink
                Originally posted by rprade
                There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                Comment


                • #9
                  Originally posted by S-F View Post
                  Does this help? I turned the light off and then did a little dance. The light didn't come back on.
                  what is the zone number of your motion sensor? Is it zone 36?

                  if so, it looks like the plugin saw your little dance between 2:38:43 and 2:38:55.

                  Oct-27 2:38:55 PM EnvisaLink DEBUG ZoneRestored 036
                  Oct-27 2:38:45 PM EnvisaLink DEBUG ZoneOpen 036
                  Oct-27 2:38:44 PM EnvisaLink DEBUG ZoneRestored 036
                  Oct-27 2:38:43 PM EnvisaLink DEBUG ZoneOpen 036
                  Oct-27 2:38:43 PM EnvisaLink DEBUG ZoneRestored 036

                  How have you defined your event? Do you use the EnvisaLink Trigger "EnvisaLink Receive Message Zone Open" or do you use the native trigger "This device changes and becomes..." ?
                  Last edited by spud; October 27th, 2014, 03:21 PM.

                  Comment


                  • #10
                    Yes it's zone 36. I use EnvisaLink Receives Message: Zone Open as the trigger. So it's looking like this one was a HS3 issue then?

                    Some times though, I will enter a room and HS3 turns the lights off immediately after I turn them on by the switch. It's hard for me to capture this in the log because keeping the Envisalink plugin on debug really fills up the log fast and the issue doesn't occur too frequently. I will keep at it though.

                    Still can't set it to debug without editing the .ini file. I'm on HS3 .130.
                    Originally posted by rprade
                    There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                    Comment


                    • #11
                      Originally posted by S-F View Post
                      Yes it's zone 36. I use EnvisaLink Receives Message: Zone Open as the trigger. So it's looking like this one was a HS3 issue then?

                      Some times though, I will enter a room and HS3 turns the lights off immediately after I turn them on by the switch. It's hard for me to capture this in the log because keeping the Envisalink plugin on debug really fills up the log fast and the issue doesn't occur too frequently. I will keep at it though.

                      Still can't set it to debug without editing the .ini file. I'm on HS3 .130.
                      I will try to replicate this problem on my system. In the meantime could you try to use the trigger "This devices changes and becomes..." instead of the EnvisaLink one, and see if that change anything?

                      Comment


                      • #12
                        Originally posted by spud View Post
                        I will try to replicate this problem on my system. In the meantime could you try to use the trigger "This devices changes and becomes..." instead of the EnvisaLink one, and see if that change anything?

                        It doesn't change anything. I have other events which use that trigger and fail from time to time also. I will continue to try getting a debug log of one of the more pronounced issues.

                        Thanks for looking into it.
                        Originally posted by rprade
                        There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                        Comment


                        • #13
                          @ spud,

                          Could you add a feature to have the plugin create it's own debug log file like Blade's plugins do? I am still experiencing this issue but it only happens a few times a day and keeping debug on creates so much chatter that it makes the log all but useless to me.
                          Originally posted by rprade
                          There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                          Comment

                          Working...
                          X