Announcement

Collapse
No announcement yet.

New Insteon Motion Sensor II...beta support available in the Updater

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by mnsandler View Post
    try programming a couple of different timeout settings and see if you see msgs in your log similar to the following:

    ID ID ID ID ID ID 1F 2E 00 01 06 10 00 03 00 00 00 00 00 00 00 00 B8 (30 sec)
    ID ID ID ID ID ID 1F 2E 00 01 06 10 00 FF 00 00 00 00 00 00 00 00 BC (42 mins)

    i bolded the byte that should change based on your setting
    My findings for Occupancy II mode:
    • Setting the Timeout (m:s) in the dialog to 30 secs will send that byte as '02', 20 secs as '01', 10 secs as '00'
    • Strangely, setting to 42 mins results in 'FB'
    • Setting the timeout 20 secs or more does activate the timeout of this mode (will send an 'On' every 20 secs while motion detected)
    • Setting the timeout to 10 secs has the effect of a considerably long delay: tested up to about 90 mins
    • No 'Off' sent for this mode
    • While set at 20 secs and when motion is continuous, the log shows timestamps every 12 or 14 secs

    The byte value you had said to expect is in reality offset by -1 in my testing, at least for the first few values.

    There is also a discrepancy with the 42 mins value (should be 'FF' ?) and the actual elapsed time between 'On's.

    Comment


      BTW, the same issue occurs when in Occupancy (I) mode.

      Comment


        MS light level discrepancy

        I'm getting different MS II light levels from the plugin's logging and my own. My logging uses the device values in an event (see after log). The log entries have identical timestamps.

        Any insights?

        Jan-22 16:44:17 CVlog MS2 Heartbeat - Light level: 0, Temperature: 24, Battery level: 3
        Jan-22 16:44:17 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=0
        Jan-22 16:31:56 CVlog MS3 Heartbeat - Light level: 0, Temperature: 22, Battery level: 3
        Jan-22 16:31:56 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=22.3333333333333, Light=0
        Jan-22 16:23:23 CVlog MS2 Heartbeat - Light level: 1, Temperature: 24, Battery level: 3
        Jan-22 16:23:23 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=0
        Jan-22 16:11:30 CVlog MS3 Heartbeat - Light level: 5, Temperature: 22, Battery level: 3
        Jan-22 16:11:30 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=22.3333333333333, Light=0
        Jan-22 16:02:28 CVlog MS2 Heartbeat - Light level: 9, Temperature: 24, Battery level: 3
        Jan-22 16:02:28 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=1
        Jan-22 15:51:05 CVlog MS3 Heartbeat - Light level: 12, Temperature: 23, Battery level: 3
        Jan-22 15:51:05 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=22.3333333333333, Light=5
        Jan-22 15:41:32 CVlog MS2 Heartbeat - Light level: 13, Temperature: 24, Battery level: 3
        Jan-22 15:41:32 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=9
        Jan-22 15:30:37 CVlog MS3 Heartbeat - Light level: 13, Temperature: 23, Battery level: 3
        Jan-22 15:30:37 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=22.7222222222222, Light=12
        Jan-22 15:20:30 CVlog MS2 Heartbeat - Light level: 19, Temperature: 24, Battery level: 3
        Jan-22 15:20:30 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=13
        Jan-22 15:10:14 CVlog MS3 Heartbeat - Light level: 18, Temperature: 23, Battery level: 3
        Jan-22 15:10:14 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=22.7222222222222, Light=13
        Jan-22 14:59:31 CVlog MS2 Heartbeat - Light level: 18, Temperature: 23, Battery level: 3
        Jan-22 14:59:31 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=19
        Jan-22 14:49:52 CVlog MS3 Heartbeat - Light level: 22, Temperature: 23, Battery level: 3
        Jan-22 14:49:52 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=18
        Jan-22 14:38:33 CVlog MS2 Heartbeat - Light level: 34, Temperature: 23, Battery level: 3
        Jan-22 14:38:33 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=18
        Jan-22 14:29:30 CVlog MS3 Heartbeat - Light level: 44, Temperature: 23, Battery level: 3
        Jan-22 14:29:30 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=22
        Jan-22 14:17:41 CVlog MS2 Heartbeat - Light level: 51, Temperature: 24, Battery level: 3
        Jan-22 14:17:41 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=34
        Jan-22 14:09:11 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=44
        Jan-22 14:09:09 CVlog MS3 Heartbeat - Light level: 47, Temperature: 23, Battery level: 3
        Jan-22 14:09:09 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=44
        Jan-22 13:56:46 CVlog MS2 Heartbeat - Light level: 47, Temperature: 24, Battery level: 3
        Jan-22 13:56:46 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=51
        Jan-22 13:48:47 CVlog MS3 Heartbeat - Light level: 58, Temperature: 24, Battery level: 3
        Jan-22 13:48:47 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=47
        Jan-22 13:35:44 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=47
        Jan-22 13:35:42 CVlog MS2 Heartbeat - Light level: 51, Temperature: 24, Battery level: 3
        Jan-22 13:35:42 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=47
        Jan-22 13:28:26 CVlog MS3 Heartbeat - Light level: 57, Temperature: 23, Battery level: 3
        Jan-22 13:28:25 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=58
        Jan-22 13:14:46 CVlog MS2 Heartbeat - Light level: 75, Temperature: 24, Battery level: 3
        Jan-22 13:14:46 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=77
        Jan-22 13:08:04 CVlog MS3 Heartbeat - Light level: 92, Temperature: 23, Battery level: 3
        Jan-22 13:08:04 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=97
        Jan-22 12:53:55 CVlog MS2 Heartbeat - Light level: 95, Temperature: 24, Battery level: 3
        Jan-22 12:53:55 Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: Battery=Good, Temp=23.5555555555556, Light=75
        Jan-22 12:47:46 CVlog MS3 Heartbeat - Light level: 91, Temperature: 24, Battery level: 3
        Jan-22 12:47:46 Insteon Device Motion sensor [3:S. TV] MS3 (41.6A.AB) sent a heartbeat: Battery=Good, Temp=23.1111111111111, Light=92
        Attached Files

        Comment


          claude,

          i log the message before setting the device values (which is what is triggering your logging)

          can you include the action insteon messages in your log
          Mark

          HS3 Pro 4.2.19.5
          Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
          Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
          Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

          Comment


            Originally posted by mnsandler View Post
            ...can you include the action insteon messages in your log
            Not sure what you mean. Aren't those the entries above like "Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: ..." ?
            Originally posted by mnsandler View Post
            ...i log the message before setting the device values (which is what is triggering your logging)...
            But shouldn't the 2 values then be equal?

            Comment


              Originally posted by claude View Post
              Not sure what you mean. Aren't those the entries above like "Insteon Device Motion sensor [2:Cuisine] MS2 (41.5C.CC) sent a heartbeat: ..." ?

              But shouldn't the 2 values then be equal?
              i am referring to the raw insteon message received like the example i posted above. the message you posted is my interpretation

              try changing your trigger to when the light level value changes and see if the values are match
              Mark

              HS3 Pro 4.2.19.5
              Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
              Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
              Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

              Comment


                MS light level discrepancy: SOLVED

                Originally posted by mnsandler View Post
                i am referring to the raw insteon message received like the example i posted above. the message you posted is my interpretation

                try changing your trigger to when the light level value changes and see if the values are match
                I changed the trigger for the light level instead of the heartbeat and now both the plugin and my event report the same light level.

                I'm guessing here, but the only explanation making sense to me is that the plugin first updates the heartbeat and very soon after the light level, so my event squeezes in between those two actions and actually picks up the previous light level value.

                Comment


                  Originally posted by claude View Post
                  My findings for Occupancy II mode:
                  • Setting the Timeout (m:s) in the dialog to 30 secs will send that byte as '02', 20 secs as '01', 10 secs as '00'
                  • Strangely, setting to 42 mins results in 'FB'
                  • Setting the timeout 20 secs or more does activate the timeout of this mode (will send an 'On' every 20 secs while motion detected)
                  • Setting the timeout to 10 secs has the effect of a considerably long delay: tested up to about 90 mins
                  • No 'Off' sent for this mode
                  • While set at 20 secs and when motion is continuous, the log shows timestamps every 12 or 14 secs

                  The byte value you had said to expect is in reality offset by -1 in my testing, at least for the first few values.

                  There is also a discrepancy with the 42 mins value (should be 'FF' ?) and the actual elapsed time between 'On's.
                  Mark,

                  Have you had time to look into this one?

                  Comment


                    Originally posted by claude View Post
                    Mark,

                    Have you had time to look into this one?
                    claude,

                    all the timing is an approximation.

                    i updated the timeout option list based on some of your findings.

                    please give beta .27 a try and see what you think
                    Mark

                    HS3 Pro 4.2.19.5
                    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                    Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                    Comment


                      Originally posted by mnsandler View Post
                      claude,

                      all the timing is an approximation.

                      i updated the timeout option list based on some of your findings.

                      please give beta .27 a try and see what you think
                      So far so good on .27, thanks.

                      Comment


                        How to add Motion Sensor ?

                        I have the latest beta but still dont seem to be able to add the motion sensor. It works ok on the Insteon App.

                        I tried adding manually by entering the address. I tried tapping on Set and Motion and that didnt seem to connect.

                        Guessing I dont know what I am doing. Can anyone help?

                        Comment


                          Originally posted by mworsnop View Post
                          I have the latest beta but still dont seem to be able to add the motion sensor. It works ok on the Insteon App.

                          I tried adding manually by entering the address. I tried tapping on Set and Motion and that didnt seem to connect.

                          Guessing I dont know what I am doing. Can anyone help?
                          all rf/battery devices are about the same...you need to put the device into linking mode. hold set btn for about 3 secs

                          then register with the plugin manually by entering insteon id
                          Mark

                          HS3 Pro 4.2.19.5
                          Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                          Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                          Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                          Comment


                            The manual add is what I was looking for. I wasn't sure if it would read the Insteon hub and load automatically or what.

                            Thank you Mark!
                            Take care

                            Comment


                              how long is your battery lasting in the Insteon MS II

                              i'm only getting about a month or two with the following settings. I should mention i have the unit mounted outside
                              Attached Files
                              Last edited by mnsandler; April 10, 2018, 12:16 PM. Reason: I should mention i have the unit mounted outside
                              Mark

                              HS3 Pro 4.2.19.5
                              Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway | Tuya Smart Plugs
                              Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 | Ultra1Wire3 | RFXCOM | HS MyQ | BLRadar | BLDenon | Tuya | Jon00 Charting | Jon00 Links
                              Platform: Windows Server 2022 Standard, i5-12600K/3.7GHz/10 core, 16GB RAM, 500GB SSD

                              Comment


                                My MS has to be at least 6 months old and its still on original battery. I am a bachelor living mostly alone, vs a family constantly triggering. My other MS II, with same settings currently, I had to replace the battery after 15 days, but it was my first one and I was playing a lot with settings. After that 15 day replacement, its been steady on same battery. Also at least 6 months old.
                                Attached Files

                                Comment

                                Working...
                                X