Comfort 2 5.054 Diallout

[rodime]

Hello,

I am using comfort 2 5.054 and have a DP02 doorphone with a PIR above it in the porch.  The idea was for the PIR to raise the porch light on visitor approach.  The PIR is set up as PerimNightAway (zone type 14).  I have disabled the default dialout on PerimNightAway also.

The problem (bug?) is that when a person rings the doorbell in away or vacation mode, instead of comfort dialling out with the doorbell alert, comfort instead dials out and announces the permiter breach, even though I disabled the dialout for perimNightAway.  I have tested to make sure perimnightaway really is disabled by triggering the PIR and not ringing the doorbell and correctly, no diallout.

If I disconnect the PIR, comfort correctly dials out with the door phone message.

In addition although I have only just seen this and not tested properly but was worth a mention in case related, if I get an intruder alert comfort seems only to be dialling out the subsequent sign in and security off, not the intruder alert itself.  I checked log remotely via sidekick and it states that comfort did dialout on both the intruder and the sign in, but only the sign in was ever received.  In this case the sign in was a good 5 minutes after the intruder. 

Any ideas?

[slychiu]

When Comfort dials out, it will announce the last alarm activated if you have several alarms active around the same time

Hence in your door station PIR case, when the doorbell is pressed, Comfort dials out, but the PIR has detected motion subsequently while dialing out. Hence the announcement is Permieter alart. Disabling the dial out on The Perimeter alarm means that the alarm wiill not initiate a dial out, but does not mean that the alarm is not reported, as the doorbell causes a dial out

You should configure the PIR as Normally Closed Switch if this has no alarm function, not Perimeter. This will only actibve its zone response but will have no alarm function

When You set off an alarm Comfort dials out. If you disarm it before the call is answered, then the current \"alarm\" is Securirty OFF which is what is announved. Once you sign in, Comfort plays the alarm history so you will hear the sequence of events leading to the alarm and disarm

[rodime]

Understood.  I\'ll change the PIR zone type.

On the last point however, the intruder alarm was around 5 minutes before the security off.  I only received the security off call and only security off was announced, not the intruder alarm.  As I said I\'m not 100% on this, specifically as the log indicates that the intruder call was made (it could have been a lost call by my mobile provider) it has happened only once.  I\'ll test properly and get back to you.

Thanks

[adlim]

Could there be any other issues that could have disrupted the dialout? For example, someone pressing on the keypad? Or a dial delay implemented?

[slychiu]

The event log records each attempt to call the phone. when you sign in it says Phone Call sign in OK or something similar
Hence if you see several events for dial out it means that it has dialed your phone several times but you did not answer perhaps out of coverage

This is a good feature to prove that Comfort did make the call

[rodime]

OK, I got round to testing this properly today.

On the first point, the SwitchNC sorted the problem with the porch PIR so all done there.

But on the intruder diallout issue, comfort really was not dialling out on the intruder event.  After much testing I managed to nail it down to the High level setting on the siren type.  On the intruder siren type the High Level setting is set to yes by default, as is the bell and keypad.    Whenever the high level speakers were activated (fire or intruder), comfort was not dialling out, hence why I was only getting a call on security off, when the speakers had stopped.  I have set the high level to off for the fire and intruder sirens and I am now getting the dialouts just fine.  It\'s not an ideal solution.  The speakers are still audible and probably just high enough to wake someone in an alarm, but with the high level there is no way anyone could sleep through it.  I would like to still use the high level setting.

Any ideas?  Perhaps this is a bug.

[slychiu]

I find it difficult to understand why High Level would prevent dial-out as it is not related in any way.
Does the event log record any dial out attempts?
Is the battery connected during this sequence, when the siren goes off?

[rodime]

Unfortunately the log only goes back as far as since I turned high level off.  I\'ll have to test again to see if the diallout appears in the log, but from the previous time, I\'m 99% certain there were diallout attempts on the intruder alarm in the log.  The battery is attached.

It is strange, but this is definitely happening.  The system is working ok now the high level is turned off.

[slychiu]

High Level siren is set by default, so if this were to prevent dial out then there wold be many similar reports.

Can you disconnect the siren and activate an intruder alarm and see what happens.

If you do not have a battery connected, the siren may be drawung too much current and causing the voltage to drop disripting the dialout. Check that you have a battery connected

[rodime]

After further tests it looks like your theory about voltage drop disrupting diallout may be correct.

I tested with high level and only 1 (of 2) speakers attached and the diallout occured ok.  Setting high level to no with both speakers connected dials out ok as well as per previous post.  Only when both speakers are attached and are set to high level does the diallout fail.

In all cases the diallout is recorded in the log whether it failed or not.

The comfort battery is connected and battery check passes.

Perhaps there are not many people with comfort2 yet using more than one speaker and that do not have a supp power supply, I don\'t know but perhaps this issue should be noted and documented in some way.