Announcement

Collapse
No announcement yet.

Hidden door sensor low batt warning changes status to Open

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

    Hidden door sensor low batt warning changes status to Open

    Hi Mark,

    I have an event that fired in the middle of the night at the same time this hidden door sensor's low battery warning was changed to On.

    The even that triggered is based on this:

    Door Sensor: Status has been Open for exactly 2s

    The door was closed and locked. HS must have thought it was closed prior to this low batt warning given the "exactly 2s", right?

    I know we've had conversations about this and regular open/close sensors in the past. This issue seems similar to a different issue I had but I thought I should start a new thread.

    I don't know how to capture logs and troubleshoot something like this given how long it takes for batteries to die. Are there any tricks to get that signal to fire repeatedly?

    Thanks!
    HomeSeer 3, Insteon, Z-wave, USB-UIRT, Google Hub/Chromecasts/Smart Speakers, Foscam cameras, Amcrest camera, RCA HSDB2a doorbell
    Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Insteon, Jon00 Homeseer/Echo Skill Helper, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

    #2
    can post a pic of the event definition?
    do you have a old battery you can install?
    Mark

    HS3 Pro 3.0.0.534
    Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
    Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
    Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

    Comment


      #3
      Event screen shot attached.

      Well, I have at least one battery low enough to trigger the low batt signal and it is in the sensor now. If I reset the low batt device in HS, then remove/re-insert the battery, will the low batt message get sent to HS again?
      Attached Files
      HomeSeer 3, Insteon, Z-wave, USB-UIRT, Google Hub/Chromecasts/Smart Speakers, Foscam cameras, Amcrest camera, RCA HSDB2a doorbell
      Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Insteon, Jon00 Homeseer/Echo Skill Helper, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

      Comment


        #4
        the reset btn only affects the hs devices but not the actual insteon device. put in a new battery and wait for it to read the new voltage and then put in the old battery. this should trigger the low battery sensor.
        Mark

        HS3 Pro 3.0.0.534
        Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
        Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
        Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

        Comment


          #5
          Hi Mark,

          Sorry for the delay. I tried putting in a new battery, resetting the low battery warning, and then placing in the old battery again. Unfortunately the low batt signal seems to be sent right away, before I have a chance to replace the hidden door sensor in the door frame. Therefore the sensor is open at the time of the transmissions below, but I'm hoping you can make sense of what is happening anyway. If you really need me to try to have the sensor closed when this signal is sent, please let me know.

          I should also add that it appears the heartbeat may also be sending an Open signal even when it is closed, but only when there is a low battery. The event I posted above had been firing incorrectly ever since the low battery warning has been triggered, but before that, worked as expected.

          I'll save this old battery in case you'd like me to run any more tests. Thanks!

          Jun-13 7:52:12 PM Insteon Submit Changes Selected

          Jun-13 7:51:56 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 11 00 03 C7 06 00 Debouncing repeat.

          Jun-13 7:51:55 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 11 00 03 C7 06 00

          Jun-13 7:51:55 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 01 03 C7 11 03

          Jun-13 7:51:55 PM email Email successfully sent to mike@encompassmp.com

          Jun-13 7:51:55 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 03 C7 11 03 Debouncing repeat.

          Jun-13 7:51:54 PM Event Event Trigger "Status Checks Sensor Low Battery"

          Jun-13 7:51:54 PM Insteon Setting status and value for device 32.7E.AF:3. Old status:0 Old Value:0, New Status:2 New Value:100

          Jun-13 7:51:54 PM Insteon Setting status and value for device 32.7E.AF:1. Old status:100 Old Value:100, New Status:2 New Value:100

          Jun-13 7:51:54 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 03 C7 11 03

          Jun-13 7:51:54 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 11 00 01 C7 06 00

          Jun-13 7:51:53 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 01 C7 11 01 Debouncing repeat.

          Jun-13 7:51:53 PM Insteon Setting status and value for device 32.7E.AF:1. Old status:100 Old Value:100, New Status:2 New Value:100

          Jun-13 7:51:53 PM Insteon ProcessGroupBroadcast: Device Front Entry Door Sensor (32.7E.AF) is group broadcast source (tgt group/button:1) sending cmd 11

          Jun-13 7:51:53 PM Insteon Received 32.7E.AF:1 (Front Entry Door Sensor: Status) Go ON

          Jun-13 7:51:53 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 01 C7 11 01
          HomeSeer 3, Insteon, Z-wave, USB-UIRT, Google Hub/Chromecasts/Smart Speakers, Foscam cameras, Amcrest camera, RCA HSDB2a doorbell
          Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Insteon, Jon00 Homeseer/Echo Skill Helper, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

          Comment


            #6
            According to the documentation, when the device sends a low battery msg like the following, the second to last byte (in this case 0x11) is supposed to indicate the sensor status (11 = on, 13 = off). Thus i update the status when necessary.

            Obviously this is not the case in your situation

            Jun-13 7:51:54 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 03 C7 11 03
            Please tell me the fw version of your sensor, and i will update the code as necessary.
            Mark

            HS3 Pro 3.0.0.534
            Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
            Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
            Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

            Comment


              #7
              I have FW version 44. What is the latest?

              I did another test. I installed the old battery while holding the plunger in. The log snippet is below.

              In my previous log snippet the sensor was actually in the open state when I installed the battery. In this snippet, I first held down the plunger before I uninstalled the good battery so HS saw the sensor as Closed. I then held it closed when I inserted the bad battery. This is where the log snippet below starts. The transmission appears the same as my previous snippet. The door status was set to Open even though I was holding it closed and the last status in HS was Closed. I then released the plunger, and then pressed it again before removing the battery. That is where the log snippet below ends.

              Firmware issue or bad firmware documentation?

              On a side-note, is there any flag to disable the LED on the device? Seems a bit pointless since it is not normally able to be seen and it would be nice to save any battery life possible.

              Jun-15 10:08:49 PM Event Event Trigger "Action Triggers Multi-Sensor Status LED Update"

              Jun-15 10:08:49 PM Insteon Setting status and value for device 32.7E.AF:1. Old status:100 Old Value:100, New Status:3 New Value:0

              Jun-15 10:08:49 PM Insteon ProcessGroupBroadcast: Device Front Entry Door Sensor (32.7E.AF) is group broadcast source (tgt group/button:1) sending cmd 13

              Jun-15 10:08:49 PM Insteon Received 32.7E.AF:1 (Front Entry Door Sensor: Status) Go OFF

              Jun-15 10:08:49 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 01 C7 13 01

              Jun-15 10:08:42 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 11 00 01 C7 06 00 Debouncing repeat.

              Jun-15 10:08:41 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 11 00 01 C7 06 00

              Jun-15 10:08:41 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 01 C7 11 01 Debouncing repeat.

              Jun-15 10:08:40 PM Insteon Setting status and value for device 32.7E.AF:1. Old status:100 Old Value:100, New Status:2 New Value:100

              Jun-15 10:08:40 PM Insteon ProcessGroupBroadcast: Device Front Entry Door Sensor (32.7E.AF) is group broadcast source (tgt group/button:1) sending cmd 11

              Jun-15 10:08:40 PM Insteon Received 32.7E.AF:1 (Front Entry Door Sensor: Status) Go ON

              Jun-15 10:08:40 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 01 C7 11 01

              Jun-15 10:08:36 PM Insteon Received STX 0x50 (Raw Insteon Rec):31 F4 38 13 00 01 CB 06 00 Debouncing repeat.

              Jun-15 10:08:35 PM Insteon Received STX 0x50 (Raw Insteon Rec):31 F4 38 13 00 01 CB 06 00

              Jun-15 10:08:35 PM Insteon Received STX 0x50 (Raw Insteon Rec):31 F4 38 00 01 01 CB 13 01

              Jun-15 10:08:35 PM Insteon Received STX 0x50 (Raw Insteon Rec):31 F4 38 00 00 01 CB 13 01 Debouncing repeat.

              Jun-15 10:08:35 PM Insteon Setting status and value for device 31.F4.38:1. Old status:100 Old Value:100, New Status:3 New Value:0

              Jun-15 10:08:35 PM Insteon ProcessGroupBroadcast: Device Kitchen Motion Sensor (31.F4.38) is group broadcast source (tgt group/button:1) sending cmd 13

              Jun-15 10:08:35 PM Insteon Received 31.F4.38:1 (Kitchen Motion Sensor: Status) Go OFF

              Jun-15 10:08:35 PM Insteon Received STX 0x50 (Raw Insteon Rec):31 F4 38 00 00 01 CB 13 01

              Jun-15 10:08:25 PM SendEmail Email successfully sent to mike@encompassmp.com;mrceolla@gmail.....sprintpcs.com; Subject: Front Door Lock - Communication Issue

              Jun-15 10:08:24 PM Insteon Received a Direct ACK from Living Room Keypad (2F.BB.A9): 2F BB A9 2C 07 7D 2B 2E 00

              Jun-15 10:08:24 PM Insteon Received STX 0x50 (Raw Insteon Rec):2F BB A9 2C 07 7D 2B 2E 00

              Jun-15 10:08:24 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/SendEmail.vb

              Jun-15 10:08:24 PM Event Event Trigger "Status Checks Front Door Lock - Communication Issue"

              Jun-15 10:08:23 PM Insteon ..Got RF PLM Response 02 62 2F BB A9 1F 2E 00 00 09 21 00 00 00 00 00 00 00 00 00 00 A8 06

              Jun-15 10:08:23 PM Insteon Sending command 02 62 2F BB A9 1F 2E 00 00 09 21 00 00 00 00 00 00 00 00 00 00 A8 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False

              Jun-15 10:08:23 PM Insteon Checking for keypadlinc button sync on device 2F.BB.A9 src index 6, SrcIsSyncTarget=True...

              Jun-15 10:08:23 PM Insteon Setting status and value for device 2F.BB.A9:6. Old status:100 Old Value:100, New Status:2 New Value:100

              Jun-15 10:08:23 PM Insteon Received a Direct ACK from Living Room Keypad (2F.BB.A9): 2F BB A9 2C 07 7D 2B 00 21

              Jun-15 10:08:23 PM Insteon Received STX 0x50 (Raw Insteon Rec):2F BB A9 2C 07 7D 2B 00 21

              Jun-15 10:08:22 PM Insteon ..Got RF PLM Response 02 62 2F BB A9 0F 19 01 06

              Jun-15 10:08:22 PM email Email successfully sent to mike@encompassmp.com

              Jun-15 10:08:22 PM Insteon Sending command 02 62 2F BB A9 0F 19 01 to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False

              Jun-15 10:08:22 PM Insteon Attempting to get a KPL LED status response from Insteon device 2F.BB.A9

              Jun-15 10:08:22 PM Insteon Sending sync command to linked responder device: Living Room Keypad Button F: Keypad: Front Lights (2F.BB.A9)

              Jun-15 10:08:22 PM Insteon SyncResponderDevices called for device code: 33.4E.4D:1

              Jun-15 10:08:22 PM Insteon Checking for keypadlinc button sync on device 33.4E.4D src index 1, SrcIsSyncTarget=True...

              Jun-15 10:08:22 PM Insteon Setting status and value for device 33.4E.4D:1. Old status:100 Old Value:100, New Status:2 New Value:100

              Jun-15 10:08:22 PM Insteon Received a Direct ACK from Front Entry Keypad (33.4E.4D): 33 4E 4D 2C 07 7D 2B 11 FF

              Jun-15 10:08:22 PM Insteon Received STX 0x50 (Raw Insteon Rec):33 4E 4D 2C 07 7D 2B 11 FF

              Jun-15 10:08:22 PM Insteon ..Got RF PLM Response 02 62 33 4E 4D 0F 11 FF 06

              Jun-15 10:08:22 PM Z-Wave Device: Lower Living Room Color Control Set to 1

              Jun-15 10:08:22 PM Z-Wave Device: Upper Kitchen Color Control Set to 1

              Jun-15 10:08:22 PM Event Event Trigger "Status Checks Sensor Low Battery"

              Jun-15 10:08:22 PM Insteon Setting status and value for device 32.7E.AF:3. Old status:0 Old Value:0, New Status:2 New Value:100

              Jun-15 10:08:22 PM Insteon Sending command 02 62 33 4E 4D 0F 11 FF to RF PLM, (Expecting 0 bytes extra back) Pre-Payload ACK:False, NAK is ok:False

              Jun-15 10:08:22 PM Insteon CAPIControl: Label=On, Value=100, ControlType=Button

              Jun-15 10:08:22 PM Device Control Device: Lower Living Room Color Control to Red (1) by/from: CAPI Control Handler

              Jun-15 10:08:22 PM Device Control Device: Upper Kitchen Color Control to Red (1) by/from: CAPI Control Handler

              Jun-15 10:08:22 PM here 70

              Jun-15 10:08:22 PM Device Control Device: Upper Front Entry Keypad: Front Lights (Load) to On (100)

              Jun-15 10:08:22 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/UpdateMultiSensorLEDs.vb

              Jun-15 10:08:22 PM Event Event Trigger "Lighting Events Activity On - Front Entry"

              Jun-15 10:08:22 PM Event Event Trigger "Action Triggers Multi-Sensor Status LED Update"

              Jun-15 10:08:22 PM Insteon Setting status and value for device 32.7E.AF:1. Old status:0 Old Value:0, New Status:2 New Value:100

              Jun-15 10:08:22 PM Insteon Received STX 0x50 (Raw Insteon Rec):32 7E AF 00 00 03 C7 11 03
              HomeSeer 3, Insteon, Z-wave, USB-UIRT, Google Hub/Chromecasts/Smart Speakers, Foscam cameras, Amcrest camera, RCA HSDB2a doorbell
              Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Insteon, Jon00 Homeseer/Echo Skill Helper, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

              Comment


                #8
                Mike,
                not sure what the latest fw version is but i'll update the code based on your version. No one else has reported this issue so it may be limited to fw 44.

                i'll reply here when i post the revised version
                Mark

                HS3 Pro 3.0.0.534
                Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                Comment


                  #9
                  I've posted .86 in the Updater in the beta section. please install and give it a try, and report back when you have a chance.
                  Mark

                  HS3 Pro 3.0.0.534
                  Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                  Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                  Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                  Comment


                    #10
                    I finally had a chance to get back to this tonight. .86 achieves the desired results! Thank you very much!

                    I first reproduced the issue before installing the update to make sure I still could. After the update everything worked as expected. While holding down the plunger I installed the dead battery. The low batt warning was triggered but the status remained Closed.

                    Thanks again for your great work and being so attentive!
                    HomeSeer 3, Insteon, Z-wave, USB-UIRT, Google Hub/Chromecasts/Smart Speakers, Foscam cameras, Amcrest camera, RCA HSDB2a doorbell
                    Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Insteon, Jon00 Homeseer/Echo Skill Helper, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

                    Comment


                      #11
                      Originally posted by mrceolla View Post
                      I finally had a chance to get back to this tonight. .86 achieves the desired results! Thank you very much!

                      I first reproduced the issue before installing the update to make sure I still could. After the update everything worked as expected. While holding down the plunger I installed the dead battery. The low batt warning was triggered but the status remained Closed.

                      Thanks again for your great work and being so attentive!
                      You're welcome. thanks for reporting back.
                      Mark

                      HS3 Pro 3.0.0.534
                      Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                      Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                      Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                      Comment


                        #12
                        I forgot to ask one more question about this device. I added it to HS3 before you added the Reset button for the low batt warning. Is there ANY way to get that button to appear short of deleting and re-adding the device? The device and device refId is used in many events and scripts. I'd really hate to have to go through and edit them all.

                        Thanks!
                        HomeSeer 3, Insteon, Z-wave, USB-UIRT, Google Hub/Chromecasts/Smart Speakers, Foscam cameras, Amcrest camera, RCA HSDB2a doorbell
                        Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Insteon, Jon00 Homeseer/Echo Skill Helper, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

                        Comment


                          #13
                          Originally posted by mrceolla View Post
                          I forgot to ask one more question about this device. I added it to HS3 before you added the Reset button for the low batt warning. Is there ANY way to get that button to appear short of deleting and re-adding the device? The device and device refId is used in many events and scripts. I'd really hate to have to go through and edit them all.

                          Thanks!
                          shutdown hs
                          add the following to the [device x] section of the ini
                          RecreateDevice=True
                          restart hs

                          this should rebuild the properties of the device without changing the dev ref number.
                          Mark

                          HS3 Pro 3.0.0.534
                          Hardware: Insteon Serial PLM | AD2USB for Vista Alarm | HAI Omnistat2 | 1-Wire HA7E | RFXrec433 | Dahua Cameras | LiftMaster Internet Gateway
                          Plugins: Insteon (mine) | Vista Alarm (mine) | Omnistat 3 (by Kirby) | Ultra1Wire3 | RFXCOM | NetCAM | MyQ | BLRadar | BLDenon | Jon00 Charting
                          Platform: HP h8-1360t, Windows Server 2012 R2, i7-3.4GHz, 16GB memory

                          Comment


                            #14
                            It looks like that worked perfectly. Thank you!

                            In case this is helpful to someone else, I needed to run Notepad as Administrator before I could save changes to Insteon.ini. That parameter is removed after the next start, so no need to look for it like I did.
                            HomeSeer 3, Insteon, Z-wave, USB-UIRT, Google Hub/Chromecasts/Smart Speakers, Foscam cameras, Amcrest camera, RCA HSDB2a doorbell
                            Plugins: BLLAN, BLOccupied, BLUSBUIRT, Chromecast, Insteon, Jon00 Homeseer/Echo Skill Helper, Jon00 DB Charting, MediaController, NetCAM, PHLocation2, Pushover 3P, weatherXML, Z-wave

                            Comment


                              #15
                              Originally posted by mnsandler View Post
                              can post a pic of the event definition?
                              do you have a old battery you can install?
                              Hi Mark, Looking through the old threads and I seem to have a similar (not sure if same) situation that has been happening with my hidden door sensors. An example event log snippet is shown below:
                              Mar-30 9:25:14 AM Event Event Trigger "SECURITY SECURITY - Basement Door OPEN"
                              Mar-30 9:25:14 AM Insteon Setting status and value for device 45.CF.3E:1. Old status:0 Old Value:0, New Status:2 New Value:100
                              Mar-30 9:25:14 AM Insteon Received STX 0x50 (Raw Insteon Rec):45 CF 3E 00 00 03 CB 11 03
                              Mar-30 9:25:14 AM Insteon Received STX 0x50 (Raw Insteon Rec):45 CF 3E 13 00 04 CB 06 00 Debouncing repeat.
                              Mar-30 9:25:13 AM Insteon Received STX 0x50 (Raw Insteon Rec):45 CF 3E 13 00 04 CB 06 00
                              Mar-30 9:25:13 AM Insteon Received STX 0x50 (Raw Insteon Rec):45 CF 3E 00 00 04 CB 13 04 Debouncing repeat.
                              Mar-30 9:25:12 AM Insteon Setting status and value for device 45.CF.3E:4. Old status:100 Old Value:100, New Status:3 New Value:0
                              Mar-30 9:25:12 AM Insteon Setting status and value for device 45.CF.3E:4. Old status:0 Old Value:0, New Status:2 New Value:100
                              Mar-30 9:25:12 AM Insteon Setting status and value for device 45.CF.3E:1. Old status:0 Old Value:0, New Status:3 New Value:0
                              Mar-30 9:25:12 AM Insteon ProcessGroupBroadcast: Device Sensors Door Basement Door (45.CF.3E) sent heartbeat with cmd 13

                              What seems to be happening is when the battery of the device gets low (I'm assuming below the low batt threshhold), then during the heartbeat they throw an update that shows the device opens.

                              This seems to be happening with all of my hidden door sensors not just this one.

                              Stats of the Device above from your plugin are:
                              Device Address Type Firmware Poll Inv. Protocol Comm Reliability % 1 Hop 2 Hops 3 Hops Msg Quality
                              Sensors Door Basement Door Click to edit device links 45.CF.3E Hidden Door Sensor 45 3 i2CS 90% (46 failed out of 475 cmds) 4829 292 108 Excellent
                              Curious if you see this is just how the sensors work? Or if there should be a different interpretation of the message that it is sending during the heartbeat?

                              Thanks in advance,
                              Lee III

                              Comment

                              Working...
                              X