Announcement

Collapse
No announcement yet.

mcsMovement Updates

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

    #61
    The attached reenables the early debug. Can you enable debug, change your door position, and then post the segment of the log that shows this activity. Disable debug after then test. I do not have an HS2 running now to test myself.
    Attached Files

    Comment


      #62
      Originally posted by Michael McSharry View Post
      The attached reenables the early debug. Can you enable debug, change your door position, and then post the segment of the log that shows this activity. Disable debug after then test. I do not have an HS2 running now to test myself.
      Below is the log entries between my closing the door which set the device value to 1 to it changing back to 0 again when the status value got updated. Which in this instance was only a matter of seconds !

      19/10/2009 13:44:27 mcsMovement Debug Status Change 4, %12=17, Value=1
      19/10/2009 13:44:27 mcsMovement Debug Value Change 1, Value Parm=1, CurrentValue=0
      19/10/2009 13:44:27 mcsMovement Debug Status Change Event for %12 To 2, Ignore=True, offTime=0, onTime=0, status=3, changed=False, ValueEvent=True, HS2=True
      19/10/2009 13:44:27 mcsMovement Debug Status Change 1024, %12=1, Value=0
      19/10/2009 13:44:27 mcsMovement Debug Value Change 1, Value Parm=0, CurrentValue=1
      19/10/2009 13:44:27 mcsMovement Debug Status Change Event for %12 To 1, Ignore=False, offTime=0, onTime=0, status=3, changed=False, ValueEvent=True, HS2=True
      19/10/2009 13:44:27 DI Debug Generic USB Joystick - Button 8 : 1
      19/10/2009 13:44:27 Event Event Trigger "Inner Porch Door Sensor"
      19/10/2009 13:44:27 Event Running script in background: RFXCOM_Input_Sensors.vb("Porch_Door_Sensor")
      19/10/2009 13:44:27 Inner Porch Door Inner Porch Door Sensor Status = 1
      19/10/2009 13:44:27 Inner Porch Door Front Door Last Changed = 19/10/2009 13:11:38
      19/10/2009 13:44:27 Inner Porch Door Current Time = 19/10/2009 13:44:27
      19/10/2009 13:44:27 Inner Porch Door Difference = 1969
      19/10/2009 13:44:27 Inner Porch Door Sunset Status = 0
      19/10/2009 13:44:27 Porch Door Sensor Porch Door Closed
      19/10/2009 13:44:29 mcsMovement Debug Status Change 4, #8=17, Value=4866685
      19/10/2009 13:44:29 mcsMovement Debug Status Change 1024, #8=4866685, Value=4866677
      19/10/2009 13:44:29 mcsMovement Debug Status Change 4, ^2=17, Value=8205
      19/10/2009 13:44:29 mcsMovement Debug Status Change 1024, ^2=8205, Value=8197
      19/10/2009 13:44:29 mcsMovement Debug Status Change 4, #9=17, Value=2267
      19/10/2009 13:44:29 mcsMovement Debug Status Change 1024, #9=2267, Value=2299
      19/10/2009 13:44:35 mcsMovement Debug Status Change 4, #8=17, Value=4866689
      19/10/2009 13:44:35 mcsMovement Debug Status Change 1024, #8=4866689, Value=4866685
      19/10/2009 13:44:35 mcsMovement Debug Status Change 4, ^2=17, Value=8209
      19/10/2009 13:44:35 mcsMovement Debug Status Change 1024, ^2=8209, Value=8205
      19/10/2009 13:44:35 mcsMovement Debug Status Change 4, #9=17, Value=2299
      19/10/2009 13:44:35 mcsMovement Debug Status Change 1024, #9=2299, Value=2267
      19/10/2009 13:44:38 mcsMovement Debug Area Device V3 to status=ON, DeviceStatus=2, DeviceOnEventTime=19/10/2009 13:44:22, DeviceMaxOnTime=0
      19/10/2009 13:44:38 mcsMovement Debug V3 DeviceStatus (prior, current, new)=2,2,2, hs Status=2, LastChange=19/10/2009 13:11:48, hsLast=19/10/2009 13:11:48,EventType=0
      19/10/2009 13:44:41 mcsMovement Debug Status Change 4, #8=17, Value=4866693
      19/10/2009 13:44:41 mcsMovement Debug Status Change 1024, #8=4866693, Value=4866689
      19/10/2009 13:44:41 mcsMovement Debug Status Change 4, ^2=17, Value=8213
      19/10/2009 13:44:41 mcsMovement Debug Status Change 1024, ^2=8213, Value=8209
      19/10/2009 13:44:41 mcsMovement Debug Status Change 4, #9=17, Value=2267
      19/10/2009 13:44:41 mcsMovement Debug Status Change 1024, #9=2267, Value=2299
      19/10/2009 13:44:42 mcsMovement Debug Status Change 4, [11=17, Value=32
      19/10/2009 13:44:42 mcsMovement Debug Status Change 1024, [11=32, Value=33
      19/10/2009 13:44:42 mcsMovement Debug Status Change 4, [12=17, Value=35
      19/10/2009 13:44:42 mcsMovement Debug Status Change 1024, [12=35, Value=36
      19/10/2009 13:44:42 mcsMovement Debug Status Change 4, [16=17, Value=4085
      19/10/2009 13:44:42 mcsMovement Debug Status Change 1024, [16=4085, Value=4075

      Comment


        #63
        it appears that it resets the device value back to zero at the same time as the 2 lines below appear in the log :

        19/10/2009 13:44:38 mcsMovement Debug Area Device V3 to status=ON, DeviceStatus=2, DeviceOnEventTime=19/10/2009 13:44:22, DeviceMaxOnTime=0
        19/10/2009 13:44:38 mcsMovement Debug V3 DeviceStatus (prior, current, new)=2,2,2, hs Status=2, LastChange=19/10/2009 13:11:48, hsLast=19/10/2009 13:11:48,EventType=0

        Comment


          #64
          This part of the processing was handled as exoected as it looks as if the prior value was 1 and the current value is 1 so no value change was detected. If you provide a full transaction where the door goes between both states then I should be able to figure out how to accomodate for HS2. I need to understand why the Value is retained as 1 when the door is in the off state.

          Comment


            #65
            I thought that I would start from scratch with the mcsMOvements plugin and see if the problem remains, so I disabled mcsMovements and removed the dll and accompanying files and folders. Restarted HS and then ran the install from the updater again, shut down HS copied in the new dll from the above post, restarted HS and enabled the plugin.

            However the log shows that mcsMovement plugin is found and the Setup->Interfaces shows the plugin as installed and enabled but I'm not getting the mcsMovement menu on the HS GUI.

            21/10/2009 20:15:40 - Plug-In - Found plug-in: mcsMovement, version: 1.14.0.2

            What have I done !?

            Comment


              #66
              Originally posted by Simonk View Post
              I thought that I would start from scratch with the mcsMOvements plugin and see if the problem remains, so I disabled mcsMovements and removed the dll and accompanying files and folders. Restarted HS and then ran the install from the updater again, shut down HS copied in the new dll from the above post, restarted HS and enabled the plugin.

              However the log shows that mcsMovement plugin is found and the Setup->Interfaces shows the plugin as installed and enabled but I'm not getting the mcsMovement menu on the HS GUI.

              21/10/2009 20:15:40 - Plug-In - Found plug-in: mcsMovement, version: 1.14.0.2

              What have I done !?
              Anyone any ideas how I can resolve whatever it is that I've done ?

              Comment


                #67
                Look in your Config\mcsMovement.ini file for a key setting of "InMenu". In should be in the [Movement] section. It should be set to 1 such as InMenu=1

                Comment


                  #68
                  Originally posted by Michael McSharry View Post
                  Look in your Config\mcsMovement.ini file for a key setting of "InMenu". In should be in the [Movement] section. It should be set to 1 such as InMenu=1
                  That got the menu back

                  Thanks
                  Simon

                  Comment


                    #69
                    Originally posted by Michael McSharry View Post
                    This part of the processing was handled as exoected as it looks as if the prior value was 1 and the current value is 1 so no value change was detected. If you provide a full transaction where the door goes between both states then I should be able to figure out how to accomodate for HS2. I need to understand why the Value is retained as 1 when the door is in the off state.
                    What happens with the sensors on the door is when open the sensor is Off and value of 0 when the door is closed it goes to On and value of 1.
                    However what I am seeing is that when the door is closed the status changes correctly from 0 to 1 however if I have the 'Update Device String' enabled the status is set back to 0 after a short while which I beleive to be when the Device String is actually updated by the plugin.

                    In the log entry below the door is already open and I close the door at 17:57:14 and sometime between 17:57:40 and 17:57:47 the value is changed back to 0, however there is no entry in the log when this happens.

                    24/10/2009 17:57:14 mcsMovement Debug Status Change 4, %12=3, Value=1
                    24/10/2009 17:57:14 mcsMovement Debug Status Change Event for %12 To 3, Ignore=True, offTime=0, onTime=0, status=3, changed=True, ValueEvent=True, HS2=True
                    24/10/2009 17:57:14 mcsMovement Debug Status Change 1024, %12=1, Value=0
                    24/10/2009 17:57:14 mcsMovement Debug Value Change 1, Value Parm=0, CurrentValue=0
                    24/10/2009 17:57:14 mcsMovement Debug Status Change Event for %12 To 2, Ignore=False, offTime=0, onTime=0, status=3, changed=True, ValueEvent=True, HS2=True
                    24/10/2009 17:57:14 mcsMovement Debug %12 DeviceStatus (prior, current, new)=2,3,2, hs Status=3, LastChange=24/10/2009 17:56:44, hsLast=24/10/2009 17:57:14,EventType=1024
                    24/10/2009 17:57:14 DI Debug Generic USB Joystick - Button 8 : 1
                    24/10/2009 17:57:14 Event Event Trigger "Inner Porch Door Sensor"
                    24/10/2009 17:57:14 Event Running script in background: RFXCOM_Input_Sensors.vb("Porch_Door_Sensor")
                    24/10/2009 17:57:14 Inner Porch Door Inner Porch Door Sensor Status Value = 1
                    24/10/2009 17:57:14 Inner Porch Door Front Door Last Changed = 24/10/2009 17:44:07
                    24/10/2009 17:57:14 Inner Porch Door Current Time = 24/10/2009 17:57:14
                    24/10/2009 17:57:14 Inner Porch Door Difference = 787
                    24/10/2009 17:57:14 Inner Porch Door Sunset Status = 100
                    24/10/2009 17:57:14 Inner Porch Door Sensor Inner Porch Door Closed
                    24/10/2009 17:57:16 mcsMovement Debug Status Change 4, #8=17, Value=4948928
                    24/10/2009 17:57:16 mcsMovement Debug Status Change 1024, #8=4948928, Value=4948918
                    24/10/2009 17:57:16 mcsMovement Debug Status Change 4, ^2=17, Value=13493
                    24/10/2009 17:57:16 mcsMovement Debug Status Change 1024, ^2=13493, Value=13483
                    24/10/2009 17:57:16 mcsMovement Debug Status Change 4, #9=17, Value=3035
                    24/10/2009 17:57:16 mcsMovement Debug Status Change 1024, #9=3035, Value=3067
                    24/10/2009 17:57:20 mcsMovement Debug Status Change 4, Z42=17, Value=43
                    24/10/2009 17:57:20 mcsMovement Debug Status Change 1024, Z42=43, Value=44
                    24/10/2009 17:57:21 mcsMovement Debug Status Change 4, Z43=17, Value=127
                    24/10/2009 17:57:21 mcsMovement Debug Status Change 1024, Z43=127, Value=125
                    24/10/2009 17:57:21 mcsMovement Debug Status Change 4, Z44=17, Value=710
                    24/10/2009 17:57:21 mcsMovement Debug Status Change 1024, Z44=710, Value=714
                    24/10/2009 17:57:21 mcsMovement Debug Status Change 4, Z45=17, Value=132
                    24/10/2009 17:57:21 mcsMovement Debug Status Change 1024, Z45=132, Value=130
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 4, Z46=17, Value=89
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 1024, Z46=89, Value=92
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 4, Z47=17, Value=252
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 1024, Z47=252, Value=251
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 4, #8=17, Value=4948933
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 1024, #8=4948933, Value=4948928
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 4, ^2=17, Value=13498
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 1024, ^2=13498, Value=13493
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 4, #9=17, Value=3067
                    24/10/2009 17:57:22 mcsMovement Debug Status Change 1024, #9=3067, Value=3035
                    24/10/2009 17:57:28 mcsMovement Debug Status Change 4, #8=17, Value=4948938
                    24/10/2009 17:57:28 mcsMovement Debug Status Change 1024, #8=4948938, Value=4948933
                    24/10/2009 17:57:28 mcsMovement Debug Status Change 4, ^2=17, Value=13503
                    24/10/2009 17:57:28 mcsMovement Debug Status Change 1024, ^2=13503, Value=13498
                    24/10/2009 17:57:28 mcsMovement Debug Status Change 4, #9=17, Value=3019
                    24/10/2009 17:57:28 mcsMovement Debug Status Change 1024, #9=3019, Value=3067
                    24/10/2009 17:57:29 mcsMovement Debug Status Change 4, Z20=17, Value=45
                    24/10/2009 17:57:29 mcsMovement Debug Status Change 1024, Z20=45, Value=44
                    24/10/2009 17:57:34 mcsMovement Debug Status Change 4, #8=17, Value=4948943
                    24/10/2009 17:57:34 mcsMovement Debug Status Change 1024, #8=4948943, Value=4948938
                    24/10/2009 17:57:34 mcsMovement Debug Status Change 4, ^2=17, Value=13508
                    24/10/2009 17:57:34 mcsMovement Debug Status Change 1024, ^2=13508, Value=13503
                    24/10/2009 17:57:34 mcsMovement Debug Status Change 4, #9=17, Value=2987
                    24/10/2009 17:57:34 mcsMovement Debug Status Change 1024, #9=2987, Value=3019
                    24/10/2009 17:57:40 mcsMovement Debug Status Change 4, #8=17, Value=4948948
                    24/10/2009 17:57:40 mcsMovement Debug Status Change 1024, #8=4948948, Value=4948943
                    24/10/2009 17:57:40 mcsMovement Debug Status Change 4, ^2=17, Value=13513
                    24/10/2009 17:57:40 mcsMovement Debug Status Change 1024, ^2=13513, Value=13508
                    24/10/2009 17:57:40 mcsMovement Debug Status Change 4, #9=17, Value=3035
                    24/10/2009 17:57:40 mcsMovement Debug Status Change 1024, #9=3035, Value=2987
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 4, Z40=17, Value=24
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 1024, Z40=24, Value=28
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 4, [11=17, Value=38
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 1024, [11=38, Value=39
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 4, [12=17, Value=42
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 1024, [12=42, Value=45
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 4, [16=17, Value=5433
                    24/10/2009 17:57:47 mcsMovement Debug Status Change 1024, [16=5433, Value=5416
                    24/10/2009 17:57:52 mcsMovement Debug Status Change 4, #8=17, Value=4948958
                    24/10/2009 17:57:52 mcsMovement Debug Status Change 1024, #8=4948958, Value=4948948
                    24/10/2009 17:57:52 mcsMovement Debug Status Change 4, ^2=17, Value=13523
                    24/10/2009 17:57:52 mcsMovement Debug Status Change 1024, ^2=13523, Value=13513
                    24/10/2009 17:57:52 mcsMovement Debug Status Change 4, #9=17, Value=3003
                    24/10/2009 17:57:52 mcsMovement Debug Status Change 1024, #9=3003, Value=3035
                    Attached Files

                    Comment


                      #70
                      The place where mcsMovement changes its internal status is the procedure that has the debug output containg "(prior, current, new)". It looks to me as you provided the same door motion transition that you provided earlier where the DeviceValue goes from 0 to 1 and this results in mcsMovement changing its internal status to ON. In this sequence the internal status shows in the debug as being ON.

                      Code:
                      24/10/2009 17:57:14 mcsMovement Debug Status Change 4, %12=3, Value=1 – HS giving DeviceStatus = OFF change
                      24/10/2009 17:57:14 mcsMovement Debug Status Change Event for %12 To 3, Ignore=True, offTime=0, onTime=0, status=3, changed=True, ValueEvent=True, HS2=True – mcsMovement ignores because status change and not value change event
                      24/10/2009 17:57:14 mcsMovement Debug Status Change 1024, %12=1, Value=0 – HS giving DeviceValue = 1 (from 0) chg
                      24/10/2009 17:57:14 mcsMovement Debug Value Change 1, Value Parm=0, CurrentValue=0 mcsMovement agrees 0 to 1 chg
                      24/10/2009 17:57:14 mcsMovement Debug Status Change Event for %12 To 2, Ignore=False, offTime=0, onTime=0, status=3, changed=True, ValueEvent=True, HS2=True – mcsMovement New Status = 2, Prior Status = 3
                      24/10/2009 17:57:14 mcsMovement Debug %12 DeviceStatus (prior, current, new)=2,3,2, hs Status=3, LastChange=24/10/2009 17:56:44, hsLast=24/10/2009 17:57:14,EventType=1024 – mcsMovement record change from OFF to ON (3 to 2)
                      Each minute mcsMovement will look at this internal status and format the DeviceString. In this case the "Now Closed" is what is expected. It also update the DeviceString in response to an event that changes the ON/OFF internal status.

                      The other ways that the internal status is changed is during intialization where it looks at the HS state and replicates it.

                      You indicated the value changed to 0 between 17:57:40 and 17:57:47. What are you looking at that you are calling a "value"? The HS display will be the DeviceString which should reflect the mcsMovement internal status property for the device. The HS DeviceValue is not normally visible unless there are special browser pages developed. The plugin that produces %12 may show it in one of its status displays, but only when HS is updated will it reflect in HS/mcsMovement.

                      The debug code produces output on events. Since you only provided one transition in the debug it is not possible to know what the state really was at the end of this event. It will only show in the log at the start of the next event.

                      Comment


                        #71
                        Originally posted by Michael McSharry View Post
                        You indicated the value changed to 0 between 17:57:40 and 17:57:47. What are you looking at that you are calling a "value"? The HS display will be the DeviceString which should reflect the mcsMovement internal status property for the device. The HS DeviceValue is not normally visible unless there are special browser pages developed. The plugin that produces %12 may show it in one of its status displays, but only when HS is updated will it reflect in HS/mcsMovement.

                        The debug code produces output on events. Since you only provided one transition in the debug it is not possible to know what the state really was at the end of this event. It will only show in the log at the start of the next event.
                        To determine the current Device Value I had added the Device Value to a screen in HSTouch so that I could see the actual value live as it changes. I've now determined by adding a reoccuring event every second to log the device value of the door that the value is not actualy changing to a 0 when it shouldn't, however in HSTouch it shows that it has changed back to a 0 when mcsMovements is set to update device status. I'm not particularly worried about this though as I wouldn't normally show a device value in HSTouch anyway.

                        So the initial problem which caused me to look at the device value was the device string not showing correctly the status and time, however I've now changed the Value Change Triggering to Value Change Event and it appears to be working.

                        Thanks for you time and input, hopefully I shouldn't need to trouble you again.

                        And thanks for a great plugin.

                        Simon

                        Comment


                          #72
                          It would seem that HST should be made aware that by writing something to DeviceString the DeviceValue is changed.

                          Comment


                            #73
                            Error

                            I've installed mcsMovement and this is all I get</PRE>

                            Script error: Type mismatch: 'CustomHeader'

                            response.write CustomHeader(Array(fs4.Value, "", gBackgroundColor, "", gStyleSheet))
                            Else</PRE>
                            </PRE>
                            Please Help,</PRE>
                            Charles</PRE>

                            Comment


                              #74
                              The Includes package used to be in the Updater, but no longer is. I posted the set of files included in this package as a zip at the top of this subforum. When they are unzipped you will want to assure they are in the path such as Homseerxxx\HTML\Includes\CustomerHeader.asp where Homeseerxxx is where Homeseer is installed.

                              Comment


                                #75
                                I had the same error as Charles. I Moved the Includes folder as you note above but have the following error now.

                                Script error: Type mismatch: 'pagerefr' XAxisDivisions = Int(TotalTime + 6) / 12 XAxisIncrement = 1

                                Comment

                                Working...
                                X