DS12a problem

[bradleygarand]

Hi Everyone!

Have a quick question for you. I have some DS12a's covering some windows and doors in a small condo. I've had a couple sensors that have worked fine for a while, (1-3 monnths) and then all of a sudden they stop reporting alert/normal status with my W800. When they stop reporting, I can open a window or door and see the light flash on the DS12a like its reporting, and can see the light on W800 flash like its receiving the signal, but no status change in homeseer.

When they do this, I've tried opening them up and holding down the button inside to reset, changing batteries, and even deleting the device and re-adding with no luck. Just wondering if anyone else has had this happen, and if they have any solutions. I've had 3-4 do it so far at random times.

Thanks for any light you can shed on this!

[Uncle Michael]

I've not had that problem (yet), but if you are using the ACRF2 plug-in, you may be able to get some additional insight by changing the debug level on the plug-in configuration page, then try some of the steps you have tried before to see if the HS log has any additional clues.

[Rotech]

You may want to restart HS, sometime thinks lockup and by restating they reset themselves. Also chk power to your w800. I can see one failing but not all. Also if your using a USB to serial adapter that can also cause issue, I seem people complaining about this also.

[bradleygarand]

Thanks for the replies guys. For some reason I didn't think about restarting Homeseer and server when that happens. I'm going to give that a shot the next time it happens. I've always just replaced the sensor as I have a bunch of them. Guess it's good thing I didnt throw the malfunctioning ones away!

[Rupp]

Thanks for the replies guys. For some reason I didn't think about restarting Homeseer and server when that happens. I'm going to give that a shot the next time it happens. I've always just replaced the sensor as I have a bunch of them. Guess it's good thing I didnt throw the malfunctioning ones away!

Next time this happens, check the HomeSeer log file and see if HomeSeer is "seeing" the sensor. If not the plugin may have gone south.

[bradleygarand]

Hey guys!

Had two more sensors stop working tonight. Have tried everything from above and they still aren't working. The DS12 blinks when the contact is moved away and brought back, the w800 is blinking each time too. Nothing in the homeseer log that I can see. Open to any suggestions, ans certainly appreciate any help.

Thanks,

Brad

[Steve Q]

Brad, As already suggested, turn on ACRF detailed debugging an see if the W800 is hearing the DS12 messages. I suspect it is not. Perhaps the code being sent by the DS12 has changed because of an intermittent battery connection. I had a lot of problems with the batteries making a good connection in the battery holder of the DS12. I had to trim the plastic with a utility knife in order to allow the + battery terminal to make good contact. I suspect that battery expansion due to the warm weather has created an intermittant connection issue.

Steve Q

[bradleygarand]

I turned on detailed debugging last night, and just caught this blip in the log. This is when I came through the front door moments ago... (Front door unit code is 19130)



5/28/2012 12:24:07 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: F5 FA 04 FB At 37319.93:0:0.1:NA:1

5/28/2012 12:24:07 PM AC-RF2 Processor (RF Decoder)Possible unregistered security device #24495 Cmd:1

5/28/2012 12:24:07 PM AC-RF2 Processor *Message packet was not recognized as actionable. (No action required, bad data, or valid transmission from an unregistered device)

5/28/2012 12:24:07 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: F5 FA 04 FB At 37320.13:0:0.1:1:1

5/28/2012 12:24:08 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: F5 FA 04 FB At 37320.33:10:0.2:2:1

5/28/2012 12:24:08 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: F5 FA 04 FB At 37320.54:0:0.1:3:1

5/28/2012 12:24:09 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: 0D 02 84 7B At 37321.44:9:0.2:NA:1

5/28/2012 12:24:09 PM AC-RF2 Processor (RF Decoder)Possible unregistered security device #16560 Cmd:2

5/28/2012 12:24:09 PM AC-RF2 Processor *Message packet was not recognized as actionable. (No action required, bad data, or valid transmission from an unregistered device)

5/28/2012 12:24:09 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: 0D 02 84 7B At 37321.63:0:0:1:1

5/28/2012 12:24:09 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: 0D 02 84 7B At 37321.83:11:0.1:2:1

5/28/2012 12:24:09 PM AC-RF2 Processor [Rcvr# 1 Type W800] Received RAW Bytes: 0D 02 84 7B At 37322.03:0:0.1:3:1


What's interesting is that when I tried opening the door again to see a new entry in the log, there was nothing there. Almost like its hearing the unit sometimes, and other times not. (And sometimes hearing the right unit code, and sometimes not)

[Wadenut]

Glad I stayed put with the DS10's.
If I'm not mistaken (I thought I was once but I was wrong) the DS12's have two separate addresses.
It looks as if they're both being received but aren't what you expect. It's as if the DS12 has changed it's identity. A loose battery just might cause this.

(Front door unit code is 19130)

5/28/2012 12:24:07 PM AC-RF2 Processor (RF Decoder)Possible unregistered security device #24495 Cmd:1
.
.
.
5/28/2012 12:24:09 PM AC-RF2 Processor (RF Decoder)Possible unregistered security device #16560 Cmd:2