Qolsys IQ Panel 2 - Alarm goes off during ARMING AWAY

Support
, , , , , , ,
21

Yes, this is related to supervision and according to Qolsys this is due to how the translator is learned in via the tamper terminals. If the terminals are shorted again after installation, you will need a jumper in between the tamper terminals.

In this case it is recommended to use a normal short piece of wire (zero resistance effectively).

Do you already have a jumper wire between the terminals? If so, power cycle the translator, does that resolve the issue? And does the issue return after a period of time?

22

Tamper wire is installed, always has been. It was power cycled last night, same question mark appeared. It doesn’t seem that the hardwire translator maintains very near real time comms with the panel during power cycle.

23

Alright thank you. I am forwarding this to Qolsys to look into. We will post follow up here. Just to clarify in case they ask, have you also power cycled your IQ Panel 2 after adding the device?

24

I should clarify, it was rebooted but never power cycled. Power cycling, I would need to remove the battery to do that. Is that what you want me to do? Thanks.

25

Yes, you’ll want to fully power down the Hardwire 16, then power back up. If this has not been done since the tamper wire was added and left in place, that might be the issue.

If you are referring to the panel itself, a reboot is fine. You’ll want to power cycle the hardwire 16 fully though.

26
Yes, you’ll want to fully power down the Hardwire 16, then power back up. If this has not been done since the tamper wire was added and left in place, that might be the issue.

If you are referring to the panel itself, a reboot is fine. You’ll want to power cycle the hardwire 16 fully though.

Ok, Jason is talking about the panel and you’re talking about the Hardwire. The hardwire translator has been power cycled over 30x since I received it, after moving, testing wires etc. I added another zone and power cycled it again last night and just did it again just now.

Btw, when power is removed from the hardwire, the Qolsys IQ Panel 2 NEVER says it’s offline or anything. It’s almost as if there no STATE being MONITORED in NEAR REAL-TIME. I read in an earlier thread that the HEARTBEAT/CHECK-IN can be up to 75 minutes? If so, let’s see if the status changes in the morning.

I was expecting that unplugging the hardwire translator would have generated a tamper/loss of supervision or some other signalling in near real-time – that part bothers me and indicates this might be a bug in the software?

27
Btw, when power is removed from the hardwire, the Qolsys IQ Panel 2 NEVER says it’s offline or anything. It’s almost as if there no STATE being MONITORED in NEAR REAL-TIME. I read in an earlier thread that the HEARTBEAT/CHECK-IN can be up to 75 minutes? If so, let’s see if the status changes in the morning.

I was expecting that unplugging the hardwire translator would have generated a tamper/loss of supervision or some other signalling in near real-time — that part bothers me and indicates this might be a bug in the software?

Ah, no you would not have a real time update when power cycling the Hardwire 16, only if the Hardwire 16 sends a signal, and the Hardwire 16 translator zone is just used for battery supervision. That zone is not indicative of the hardwire sensor zones.

Unplugging and leaving the translator powered down would indeed result in a supervision error at the supervision interval, but not right away.

If there isn’t a separate issue and you’re experiencing a supervision error the only time you should be able to clear that question mark would be relearning the Hardwire 16 into the panel, or rebooting the panel. You might be able to clear it by removing the tamper jumper temporarily. However, the supervision fault would likely then return after the supervision interval, based on what you are describing.

Power cycling the Hardwire 16 is recommended by Qolsys, but is not intended to see an immediate change. If it had a positive impact the zone status would clear at the next supervision interval.

Sensors do not update the panel unless there is a change in status or during a supervision interval.

Ultimately, to clarify everything, the issue that is occurring is that the tamper/battery supervisory zone of the translator is not sending a heartbeat signal, but the other zones are.

So, to verify because I don’t see it above, if you remove and relearn that translator zone, do you see the zone act normally for a time and then revert to unknown status?

Keep in mind since the Translator zone is not technically functional other than battery supervision, that zone should be fine to actually leave out of panel programming, optionally.

28

Thanks Jason, a lot of what you said makes sense. I did re-learn it in the past which seemed to clear the question mark and then it comes back after a few days. I will try that again tonight.

I noticed that whenever I arm the system, the Qolsys will “bypass the hardwire” translator. All the sensors work perfectly so perhaps this is intended by design but it just doesn’t feel right to me to function in such a manner.

Also, after every arming, I will receive an email, see below (is that expected behavior)? Even though nothing is selected in the panel for bypass, it still does it on every ARM operation.

PRAdTo0.png806×698

QeGoOJS.jpg3264×2448

TvHicEB.jpg2611×1958

29

It is reporting as a failed zone, and would be force-bypassed when armed.

The bypass would not be in effect when the system is disarmed.

30

Ok… and this is what we want, yes or no?

If no, how do you suggest I resolve, attempt the deletion of the hardwire sensor tonight and re-adding it back in?

31

Well, no, that is simply how it will treat an open or failed zone.

There are two options to resolve:

  1. Removal and re-addition of the zone is a troubleshooting step that should resolve the supervision error temporarily, if not resolve the issue entirely if other steps have been followed and nothing else is at fault. However, this would at least verify that the panel is acting as we would expect.

You would want to see it report normally for a while, then it will likely revert to an error during supervision time.

I may be missing it above, but can you confirm whether you have a short piece of wire connected to the tamper terminals or is it a resistor?

  1. Optionally the zone can just be removed and left out of programming as it does not have a function other than supervision.
32

I have a resistor connected as that was the guidance provided in the forums by another Surety tech employee. Do you think that could be causing a problem?

Understood about point #2 as well, thank you.

33
I have a resistor connected as that was the guidance provided in the forums by another Surety tech employee. Do you think that could be causing a problem?

The Qolsys instructional video looks like it has a resistor connected, however Qolsys support has suggested that just a 0 resistance jumper wire should be tried.

See here earlier in the thread.

"If the terminals are shorted again after installation, you will need a jumper in between the tamper terminals.

In this case it is recommended to use a normal short piece of wire (zero resistance effectively)."

34

Thanks Jason, I will try that tonight and come back with any additional findings.

35

Sometimes applying Ocamm’s razor is usually the easiest — I just deleted the hardwire translator out and all of the sensors are still working, not sure why I didn’t do that initially.