Hidden door sensor low batt warning changes status to Open

[mnsandler]

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.

[mrceolla]

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

[mnsandler]

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.

[mrceolla]

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?

[mnsandler]

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

[mrceolla]

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!