04-25-2016, 02:30 PM
Hi all.
Just lately I\'ve had a number of occasions where I have had problems arming comfort to away/vacation mode.
My arm confirmation is by final exit door (my front door), and I have this zone set to announce, so I\'m very precisely aware of the front door zone activation (I can hear the announcement from my home office). And I can confidently say that there is NOT any problem with detection of this this zone activation, either open or close.
However, on more than one occasion lately, I hit the arm button on my way out, the countdown beeps start, as does the \"Please exit\" warning, and I exit the premises... I hear the announcements for triggered zones as I do so - I have a hall PIR that covers the area inside the door, so that zone activates and announces as I walk out the door. I also hear the front door zone announce. But after exiting & closing the door, this does not seem to be acknowledged, the countdown beeps continue, comfort continues to repeat \"Please exit\", until eventually the exit time expires and an arm fail alarm is triggered. I have to re-enter the premises, and sign in to cancel the arm fail alarm.
On the latest occasion - this morning, after having signed in & cancelled the arm fail alarm, I immediately tried to arm again; the countdown beeps started, but there was no voice at all... no \"Please Exit\" and no zone announcements as I exited the building. However, as soon as I closed the front door, the beeps stopped, the system armed \'successfully\' - but there was no announcement of \"Away\" or \"Vacation\" mode... just no voice at all, on either the keypad used to arm, or the external doorstation...
On other occasions, the behaviour can vary very slightly, but mostly it follows a very similar pattern; the first arm attempt fails, the 2nd attempt arms OK, and it is always accompanied by some element of voice inconsistency...
This behaviour has only been noticeable fairly recently - say the last month or two, and is intermittent... many times arming works perfectly, first time.
I have also not noticed any issues arming to Night mode, although I have only started to regularly arm at night fairly recently - probably also only in the last couple of months.
Roughly the same period - the last 2 months or so, I have become aware of voice inconsistencies both as described above, but also unrelated to arming... primarily this has been a significant delay of announcement of zones that I have set to announce (both ground floor doors basically) - I have been aware of opening a door, and some 20-30 seconds later I hear the announcement of that zone. I have a couple of responses that also I have programmed words to be spoken so I\'m aware of it running, and again I am aware that occasionally those words are spoken way after the response is triggered - despite being the first action in the response... my night mode response is where I notice this most, the first action in that is \"Announce Night Mode Response\" - I arm to night mode from a keypad (ID3) beside my bed, I\'m aware of the response running as I can see lights all over the house going off, but again some 20 or so seconds later I hear the announcement spoken...
Lastly, on numerous occasions when arming, I have observed the announcement of the arm mode get truncated... I frequently hear \"tion mode\" on the external voice station instead of \"Vacation mode\", sometimes the whole first word is \'lost\' and I just hear \"mode\" announced.
Note that I don\'t tend to use \"away\" mode... I have reprogrammed the primary one touch arm buttons on my keypads to arm to vacation mode or night mode dependent on the keypad ID, - this keeps things simpler to explain to all users, and removes the possibility of inadvertently trying to arm to away/vacation mode when arming from the bedroom keypad.
Oh, and possibly (or not) related, on a couple of occasions I\'ve had false intruder alarms when armed to vacation mode, and I think it\'s always the same zone (hall PIR, the one that covers inside the front door) that causes it.
The system is brand new, has been installed for about as year, and there have been no hardware changes in the timeframe that these anomalies have started to occur.
Any thoughts on what is going one here? - it is causing quite a lot of concern, - Comfort is one of the very few totally essential systems in the house, it just *has* to work first time, every time, and give close to 100% reliability...
Just lately I\'ve had a number of occasions where I have had problems arming comfort to away/vacation mode.
My arm confirmation is by final exit door (my front door), and I have this zone set to announce, so I\'m very precisely aware of the front door zone activation (I can hear the announcement from my home office). And I can confidently say that there is NOT any problem with detection of this this zone activation, either open or close.
However, on more than one occasion lately, I hit the arm button on my way out, the countdown beeps start, as does the \"Please exit\" warning, and I exit the premises... I hear the announcements for triggered zones as I do so - I have a hall PIR that covers the area inside the door, so that zone activates and announces as I walk out the door. I also hear the front door zone announce. But after exiting & closing the door, this does not seem to be acknowledged, the countdown beeps continue, comfort continues to repeat \"Please exit\", until eventually the exit time expires and an arm fail alarm is triggered. I have to re-enter the premises, and sign in to cancel the arm fail alarm.
On the latest occasion - this morning, after having signed in & cancelled the arm fail alarm, I immediately tried to arm again; the countdown beeps started, but there was no voice at all... no \"Please Exit\" and no zone announcements as I exited the building. However, as soon as I closed the front door, the beeps stopped, the system armed \'successfully\' - but there was no announcement of \"Away\" or \"Vacation\" mode... just no voice at all, on either the keypad used to arm, or the external doorstation...
On other occasions, the behaviour can vary very slightly, but mostly it follows a very similar pattern; the first arm attempt fails, the 2nd attempt arms OK, and it is always accompanied by some element of voice inconsistency...
This behaviour has only been noticeable fairly recently - say the last month or two, and is intermittent... many times arming works perfectly, first time.
I have also not noticed any issues arming to Night mode, although I have only started to regularly arm at night fairly recently - probably also only in the last couple of months.
Roughly the same period - the last 2 months or so, I have become aware of voice inconsistencies both as described above, but also unrelated to arming... primarily this has been a significant delay of announcement of zones that I have set to announce (both ground floor doors basically) - I have been aware of opening a door, and some 20-30 seconds later I hear the announcement of that zone. I have a couple of responses that also I have programmed words to be spoken so I\'m aware of it running, and again I am aware that occasionally those words are spoken way after the response is triggered - despite being the first action in the response... my night mode response is where I notice this most, the first action in that is \"Announce Night Mode Response\" - I arm to night mode from a keypad (ID3) beside my bed, I\'m aware of the response running as I can see lights all over the house going off, but again some 20 or so seconds later I hear the announcement spoken...
Lastly, on numerous occasions when arming, I have observed the announcement of the arm mode get truncated... I frequently hear \"tion mode\" on the external voice station instead of \"Vacation mode\", sometimes the whole first word is \'lost\' and I just hear \"mode\" announced.
Note that I don\'t tend to use \"away\" mode... I have reprogrammed the primary one touch arm buttons on my keypads to arm to vacation mode or night mode dependent on the keypad ID, - this keeps things simpler to explain to all users, and removes the possibility of inadvertently trying to arm to away/vacation mode when arming from the bedroom keypad.
Oh, and possibly (or not) related, on a couple of occasions I\'ve had false intruder alarms when armed to vacation mode, and I think it\'s always the same zone (hall PIR, the one that covers inside the front door) that causes it.
The system is brand new, has been installed for about as year, and there have been no hardware changes in the timeframe that these anomalies have started to occur.
Any thoughts on what is going one here? - it is causing quite a lot of concern, - Comfort is one of the very few totally essential systems in the house, it just *has* to work first time, every time, and give close to 100% reliability...
