concord 4 wont arm

[TeleFragger]

ok seperate issue.. seperate thread..

HS is telling me my alarm sensors are all fine. but i cannot arm the alarm. it gives me a back door supervisory.. not sure what that means... i replaced the battery too... just in case.. and no dice.. a quick google said the device lost connection to the alarm.. but that is not true. I can open the door and HS says the door is open... close the door and HS says it is closed.. so the alarm sees the device.. anyone know why one would receive a supervisory and not be allowed to alarm the system?

[TeleFragger]

i am seeing from some people that you can program the device as a supervisory device.. need to go in to that device and make sure it is set to 01.. but it has been running for a few years now... so not sure.. my wife isnt at ease with it not being set...

[TeleFragger]

ok i made sure the device was tmp or tp what ever it is.. set to 1..
for device.. i moved it from 10 to 13 then when you open the door. it auto triggers the alarm... so the device is working...
i dont know what is going on...

i set it back to 10..
it wont let me arm it... says sliding glass door supervisory....

no one?

[mattm55]

Hey Tele,

Sounds strange to me. I have had a sensor go bad and one recently have a battery issue, replaced battery and that battery was bad. I haven't had a "supervisory" issue with any. Has something changed recently? Interference maybe?

Haven't you had some issues with your alarm... can a delete and reinstall of that sensor help with new settings.

Let us all know of your findings, more info too... and maybe it'll trigger some ideas.

Matt

[TeleFragger]

well i got it working..

i deleted, re added it... changed the group type...
weird things is the unit was working fine with the alarm.. example is if you change the device type in the panel.. think it was from a 10 to a 13.. open door and alarm would immediately trigger and go off.. so communication was working.. changed battery and that didnt do it.. so i got mad and just unplugged the alarm from the wall and yanked the battery backup out.. let it sit while i played MWF3... got a few matches in.. plugged it all back in... played a few more matches.. went and looked.. and all i had to do was set the date and time..

im running just fine again..

i do not recall having any issues with my alarm... i really like it... i was going to buy a new sensor but tried this method first and it worked... strange though...

[mattm55]

That is quite strange. I haven't had anything that strange but we'll need some way of debugging, and doc w/images when we go forward. Sometimes the pics are worth , yeah, a 1000+ words. It just sometimes isn't obvious.

Still like my Concord althought I had thought in the past to redo with HAI. I'm sticking it out though... once we get the source code for the plugin and some developers support, I think we could have some awesome features.... I just hate to start from scratch when something is already out there and works well...

Matt

[TeleFragger]

yesterday i was at the kitchen table and i heard the alarm do 3 beeps.. so i walk over to it. Usually just hit status twice and it will say if a battery is low or if alarm memory on a device.. but it said the supervisory again... grrrrrrr i may just replace the device if it does it again...
powered off for 10 minutes and plugged back in. Working fine...

[mattm55]

Hmmm, could there be something "new" blocking the signal at certain times? A new microwave, cordless ph, anything that may have changed. I'd do a swap if you have a similar sensor in another location.

I had my x10 signal/RFXCom blocked by a flat screen TV recently. Argg, the DS10's are nowhere as reliable as a GE sensor for sure...

Just a thought.... Matt

[TeleFragger]

hmm only thing new.. and this is 5-6 months now... is a samsung led 3d tv..
that is it.. nothing else...
yeah ill let it happen again then swap the innerds with the garage door...
if it follows the sensor.. then i will buy a new one..

[TeleFragger]

did it again.. .so i moved it from the back door to the front door..
followed the device...
so now im just going to order a new device.. the sensor is 14 years old...

[mattm55]

Well that sounds like its the device as it followed you by location. I've also replaced batteries with fresh ones only to have those be weak too... I try to eliminate all possibilities before a sensor or major config change.

1. Relearn sensor
2. Swap sensor location
3. Change battery
4. If still failing, swap battery with known good battery for testing
5. Change sensor

Like I say, hasn't happened but 2x so far over 8-10 years or so. Pretty reliable for me.
Matt

[TeleFragger]

these devices are about 12 years old...
new one ordered... nx-650...

[TeleFragger]

new one in.. but first deleted old
then installed new.. and programmed it in..
still did it later that day..
im getting frustrated here.. im most likely gonna do a reset on my alarm this week...

[mattm55]

Sounds strange...

1. You moved the device to the frt door, but forgot to ask if you relearned the 2 sensors. If not, you ruled out interference only but not the sensor or config.

2. Now you have an extra sensor and know the old one is still good.

3. Yes, I would think something is messed up with the alarm config? Not sure if you'll have to do a whole alarm reset and start prg'ing sensors again, kinda like a Windows format. I wouldn't think the plugin would be causing the supervisory error??

I wish we had programming software for the panel so we could save a backup instead of going through naming, tripping and grouping the alarm? I thought there was a tool available but I don't have it...

Keep us updated as I'm sure someday this will happen again and we'll have it doc'ed???

Matt

[mattm55]

Just had to replace another NX-650 sensor today and another one is cycling faulted every hour. I swapped batteries in that one which probable borked that one too.

I think some of the batches of old had bad components from what I've found?

Glad I had the foresight to order extras 9sensors) and have some batteries on-hand too.

Matt