HAI Wireless - signal strength indicator? id a bad sensor?

My HAI OPII setup uses mostly wired sensors, but there were a few places (~10) that were inaccessible when the rest were wired (this was a retrofit and walls were closed). My installer encouraged me to use HAI Wireless sensors and receiver for these.

As it turned out, my installer originally placed my wireless receiver close to my panel and I was seeing frequent supervisory failures from all sensors (even the ones that were 15-20 ft away). He relocated it up into the attic and the problems have mostly abated. Since then I have been woken up a few mornings by a wireless sensor that decided to report "not ready".

I have two questions:

1. IIUC, the HAI wireless receiver only reports supervisory failure when the receiver has failed to receive supervisory acknowledgment from a sensor for 6 hours. I'd like to see the # of failures before the 6 hour limit is reached so I can find the best placement of the receiver. Is there any way to see the status / reception of my wireless sensors in real-time?

2. For now I have bypassed the sensor. The physical placement of the sensor seems OK and it seems to have good contact when the window is closed, but I still see it reporting "not ready" from time to time. Would a reception problem cause a "not ready" or do these only manifest as "trouble"? How can I troubleshoot to determine if the sensor is bad?

Digger said:

js19707 said:

My HAI OPII setup uses mostly wired sensors, but there were a few places (~10) that were inaccessible when the rest were wired (this was a retrofit and walls were closed). My installer encouraged me to use HAI Wireless sensors and receiver for these.

As it turned out, my installer originally placed my wireless receiver close to my panel and I was seeing frequent supervisory failures from all sensors (even the ones that were 15-20 ft away). He relocated it up into the attic and the problems have mostly abated. Since then I have been woken up a few mornings by a wireless sensor that decided to report "not ready".

I have two questions:

1. IIUC, the HAI wireless receiver only reports supervisory failure when the receiver has failed to receive supervisory acknowledgment from a sensor for 6 hours. I'd like to see the # of failures before the 6 hour limit is reached so I can find the best placement of the receiver. Is there any way to see the status / reception of my wireless sensors in real-time?

2. For now I have bypassed the sensor. The physical placement of the sensor seems OK and it seems to have good contact when the window is closed, but I still see it reporting "not ready" from time to time. Would a reception problem cause a "not ready" or do these only manifest as "trouble"? How can I troubleshoot to determine if the sensor is bad?

Click to expand...

Not ready seems to indicate that the zone is violated not a lost transmitter so placement of the receiver etc does not seem to apply here. Possibly the magnetic contact gap is to wide or there is a bad connection if it is external?

Click to expand...

I have occasioanlly gotten a "Had Trouble" error from a wireless sensor. I assumed that was from lost signal (it was from the fartherest out sensor in my home). I have only seen a not ready when a door or window are open. ie the sensor was triggered. I hope that helps a little.

I think the answer to my question is here:

http://www.homeauto.com/downloads/Products...SI_Addendum.pdf

What I'm not sure of is whether the RSSI feature is a new one, and if so, how to tell whether my receiver and panel support it. Can anyone from HAI clarify?

Also for someone from HAI: I would like to know whether there is any way to record these loop values so I can look over the results for the past N hours/days. When I see reports of trouble for a sensor, it is usually in the past tense (I don't catch it while it's reporting trouble). Can I set triggers based upon these loop values with the 3.0 firmware?

Also, when I looked earlier today, all the loop values were "30", which the RSSI doc describes as indicating "good signal strength", "secure".

Now, when I'm looking, I see only "0" reported as the loop value for some zones. What does a single value of "0" mean? Is this the same as "00" ("no signal", "secure"), or does it mean something else entirely?

My HAI receiver is in the attic, so I can't easily see whether it's reporting any supervisory failures or other messages for any of the sensors.

A loop reading of "0" is the same as "00" (no signal). If there is currently a “supervisory failure” associated with a transmitter or if the receiver did not receive any RSSI data from a transmitter, the loop reading will display “0”.

The RSSI feature was added in Revision D, which was released in April of 2008. The last digit on the serial number label on the back of the unit indicates the receiver revision. For example:

45A00-1
0816-0001D

The RSSI feature works will all versions of controller firmware.

Each time a device transmits a signal (secure, not ready, supervisory report, or battery low) to the receiver, the receiver will store its signal strength in the receiver’s memory. That signal strength value will be retained until the next transmission from the device.

Using Version 3.0 of Controller Firmware and the latest build of PC Access Software (Version 3.0.0.427), you can create programs in the controller to log the RSSI value when the loop reading changes. Here’s an example:

For this example, I am using the following:

Message 1: RSSI = 0
Message 2: RSSI = 1
Message 3: RSSI = 2
Message 4: RSSI = 3
Unit 393 (Flag 1): RSSI FLAG
Zone 49: Front Door

Programs:

The following program blocks are used to check the loop reading of Zone 49 (Front Door) every minute (you can specify a different interval in your program, as desired) and log the RSSI value in the event log if the RSSI value changed from the previous evaluation. To check the RSSI value for additional zones, duplicate the 4 program blocks and change the Zone and use an additional flag (e.g. RSSI FLAG_2) in place of the existing RSSI FLAG.


EVERY MINUTE
AND IF FRONT DOOR LOOP READING IS 0
AND IF RSSI FLAG CURRENT VALUE IS NOT 0
THEN SET RSSI FLAG TO 0
THEN LOG RSSI = 0

EVERY MINUTE
AND IF FRONT DOOR LOOP READING IS GREATER THAN 9
AND IF FRONT DOOR LOOP READING IS LESS THAN 20
AND IF RSSI FLAG CURRENT VALUE IS NOT 1
THEN SET RSSI FLAG TO 1
THEN LOG RSSI = 1

EVERY MINUTE
AND IF FRONT DOOR LOOP READING IS GREATER THAN 19
AND IF FRONT DOOR LOOP READING IS LESS THAN 30
AND IF RSSI FLAG CURRENT VALUE IS NOT 2
THEN SET RSSI FLAG TO 2
THEN LOG RSSI = 2

EVERY MINUTE
AND IF FRONT DOOR LOOP READING IS GREATER THAN 29
AND IF FRONT DOOR LOOP READING IS LESS THAN 40
AND IF RSSI FLAG CURRENT VALUE IS NOT 3
THEN SET RSSI FLAG TO 3
THEN LOG RSSI = 3

Also worth noting, if you see a wireless receiver zone trouble and then immediately clear (within the same minute) in the system event log, then that indicated a “battery low” trouble for that transmitter. If you see a wireless receiver zone trouble and the trouble is not cleared or clears several minutes, hours, or days later, that indicated a “supervisory failure” trouble for that transmitter.

Scott, thanks for the response.

Sorry it's taken me a while to upgrade to the 3.0 firmware, upgrade my PCA, write these rules for each of the 10 wireless sensors that I have, fix the typos, etc.

But now I have ~couple of days worth of data, including from 5:14a this morning when my alarm was tripped by a wireless sensor that was reporting Not Ready (though I am 100% sure the window was not opened and not tampered with).

This makes 3 times in the past couple of months that I have been woken up by false alarms on 2 of my 10 wireless sensors (compared to 0 on a larger number of wired sensors). Unfortunately the system has a knack for going off on the days when I need those last couple of hours of sleep the most, so I am very unhappy.

The maximum straight-line distance from a sensor to the wireless receiver is ~50 ft, and the construction here is wood frame + stucco exterior. The signal strength of the 2 sensors in question are tracked in the logs as RSSI_4 (this morning, ~40 ft from the receiver) RSSI_6 (twice, previously; ~20 ft from the receiver).

Here's the data:
1 1/22 1:54 PM LOG RSSI_5 = 2
2 1/22 1:42 PM LOG RSSI_3 = 3
3 1/22 1:27 PM LOG RSSI_0 = 3
4 1/22 1:22 PM LOG RSSI_2 = 3
5 1/22 1:02 PM LOG RSSI_9 = 3
6 1/22 12:55 PM LOG RSSI_1 = 3
7 1/22 12:50 PM LOG RSSI_8 = 3
8 1/22 12:44 PM LOG RSSI_5 = 3
9 1/22 12:41 PM LOG RSSI_7 = 3
10 1/22 12:34 PM LOG RSSI_4 = 3
11 1/22 12:32 PM LOG RSSI_9 = 0
12 1/22 12:32 PM LOG RSSI_8 = 0
13 1/22 12:32 PM LOG RSSI_7 = 0
14 1/22 12:32 PM LOG RSSI_4 = 0
15 1/22 12:32 PM LOG RSSI_3 = 0
16 1/22 12:32 PM LOG RSSI_2 = 0
17 1/22 12:32 PM LOG RSSI_1 = 0
18 1/22 12:32 PM LOG RSSI_0 = 0
19 1/22 11:33 AM LOG RSSI_5 = 2
20 1/22 9:06 AM LOG RSSI_8 = 3
24 1/22 8:35 AM LOG RSSI_2 = 3
25 1/22 8:31 AM LOG RSSI_0 = 3
26 1/22 8:16 AM LOG RSSI_9 = 3
27 1/22 8:01 AM LOG RSSI_5 = 3
28 1/22 7:56 AM LOG RSSI_1 = 3
29 1/22 7:49 AM LOG RSSI_7 = 3
30 1/22 7:41 AM LOG RSSI_4 = 3
31 1/22 7:33 AM LOG RSSI_3 = 3
33 1/22 7:26 AM LOG RSSI_9 = 0
34 1/22 7:26 AM LOG RSSI_7 = 0
35 1/22 7:26 AM LOG RSSI_5 = 0
36 1/22 7:26 AM LOG RSSI_4 = 0
37 1/22 7:26 AM LOG RSSI_3 = 0
38 1/22 7:26 AM LOG RSSI_2 = 0
39 1/22 7:26 AM LOG RSSI_1 = 0
40 1/22 7:26 AM LOG RSSI_0 = 0
41 1/22 6:37 AM LOG RSSI_8 = 2
42 1/22 5:22 AM LOG RSSI_8 = 3
44 1/22 5:18 AM Jay BYPASS (sensor_3)
45 1/22 5:18 AM Jay BYPASS (sensor_4)
46 1/22 5:14 AM Jay DISARM
47 1/22 5:14 AM BURGLARY ALARM ACTIVATED
48 1/22 5:14 AM (sensor_4) TRIPPED
49 1/22 3:34 AM LOG RSSI_0 = 3
50 1/22 3:30 AM LOG RSSI_9 = 3
51 1/22 3:20 AM LOG RSSI_5 = 3
52 1/22 2:58 AM LOG RSSI_7 = 3
53 1/22 2:57 AM LOG RSSI_1 = 3
54 1/22 2:53 AM LOG RSSI_8 = 2
55 1/22 2:49 AM LOG RSSI_4 = 3
56 1/22 2:38 AM LOG RSSI_3 = 3
57 1/22 2:37 AM LOG RSSI_2 = 3
58 1/22 2:20 AM LOG RSSI_9 = 0
59 1/22 2:20 AM LOG RSSI_8 = 0
60 1/22 2:20 AM LOG RSSI_7 = 0
61 1/22 2:20 AM LOG RSSI_5 = 0
62 1/22 2:20 AM LOG RSSI_4 = 0
63 1/22 2:20 AM LOG RSSI_3 = 0
64 1/22 2:20 AM LOG RSSI_2 = 0
65 1/22 2:20 AM LOG RSSI_1 = 0
66 1/22 2:20 AM LOG RSSI_0 = 0
67 1/22 1:38 AM LOG RSSI_8 = 3
69 1/22 1:08 AM LOG RSSI_9 = 3
70 1/22 12:23 AM LOG RSSI_8 = 2
71 1/21 10:44 PM LOG RSSI_9 = 2
72 1/21 10:05 PM LOG RSSI_7 = 3
73 1/21 9:56 PM LOG RSSI_4 = 3
74 1/21 9:55 PM LOG RSSI_1 = 3
75 1/21 9:53 PM LOG RSSI_8 = 3
76 1/21 9:50 PM LOG RSSI_2 = 3
77 1/21 9:43 PM LOG RSSI_3 = 3
78 1/21 9:27 PM LOG RSSI_5 = 3
79 1/21 9:21 PM LOG RSSI_0 = 3
80 1/21 9:14 PM LOG RSSI_9 = 0
81 1/21 9:14 PM LOG RSSI_8 = 0
82 1/21 9:14 PM LOG RSSI_7 = 0
83 1/21 9:14 PM LOG RSSI_5 = 0
84 1/21 9:14 PM LOG RSSI_4 = 0
85 1/21 9:14 PM LOG RSSI_3 = 0
86 1/21 9:14 PM LOG RSSI_2 = 0
87 1/21 9:14 PM LOG RSSI_1 = 0
88 1/21 9:14 PM LOG RSSI_0 = 0
89 1/21 8:21 PM LOG RSSI_9 = 3
98 1/21 7:38 PM LOG RSSI_7 = 3
99 1/21 7:10 PM LOG RSSI_9 = 2
100 1/21 6:24 PM LOG RSSI_7 = 2
101 1/21 5:10 PM LOG RSSI_7 = 3
102 1/21 5:02 PM LOG RSSI_4 = 3
103 1/21 5:02 PM LOG RSSI_2 = 3
104 1/21 4:56 PM LOG RSSI_1 = 3
105 1/21 4:53 PM LOG RSSI_8 = 3
106 1/21 4:47 PM LOG RSSI_3 = 3
107 1/21 4:46 PM LOG RSSI_9 = 3
108 1/21 4:44 PM LOG RSSI_5 = 3
109 1/21 4:24 PM LOG RSSI_0 = 3
110 1/21 4:08 PM LOG RSSI_9 = 0
111 1/21 4:08 PM LOG RSSI_7 = 0
112 1/21 4:08 PM LOG RSSI_5 = 0
113 1/21 4:08 PM LOG RSSI_4 = 0
114 1/21 4:08 PM LOG RSSI_3 = 0
115 1/21 4:08 PM LOG RSSI_2 = 0
116 1/21 4:08 PM LOG RSSI_1 = 0
117 1/21 4:08 PM LOG RSSI_0 = 0
118 1/21 1:10 PM LOG RSSI_9 = 3
119 1/21 1:08 PM LOG RSSI_8 = 2
120 1/21 12:13 PM LOG RSSI_2 = 3
121 1/21 12:08 PM LOG RSSI_4 = 3
122 1/21 11:59 AM LOG RSSI_5 = 3
123 1/21 11:58 AM LOG RSSI_9 = 2
124 1/21 11:58 AM LOG RSSI_1 = 3
125 1/21 11:53 AM LOG RSSI_8 = 3
126 1/21 11:49 AM LOG RSSI_3 = 3
127 1/21 11:27 AM LOG RSSI_0 = 3
128 1/21 11:02 AM LOG RSSI_7 = 3
129 1/21 11:01 AM LOG RSSI_9 = 0
130 1/21 11:01 AM LOG RSSI_8 = 0
131 1/21 11:01 AM LOG RSSI_7 = 0
132 1/21 11:01 AM LOG RSSI_4 = 0
133 1/21 11:01 AM LOG RSSI_3 = 0
134 1/21 11:01 AM LOG RSSI_2 = 0
135 1/21 11:01 AM LOG RSSI_1 = 0
136 1/21 11:01 AM LOG RSSI_0 = 0
137 1/21 10:49 AM LOG RSSI_5 = 2
140 1/21 9:35 AM LOG RSSI_9 = 3
141 1/21 8:09 AM LOG RSSI_8 = 3
143 1/21 7:00 AM LOG RSSI_1 = 3
144 1/21 6:55 AM LOG RSSI_8 = 2
145 1/21 6:55 AM LOG RSSI_3 = 3
146 1/21 6:31 AM LOG RSSI_0 = 3
147 1/21 6:15 AM LOG RSSI_2 = 3
148 1/21 6:12 AM LOG RSSI_7 = 3
149 1/21 6:07 AM LOG RSSI_5 = 3
150 1/21 6:03 AM LOG RSSI_4 = 3
151 1/21 5:55 AM LOG RSSI_9 = 0
152 1/21 5:55 AM LOG RSSI_8 = 0
153 1/21 5:55 AM LOG RSSI_7 = 0
154 1/21 5:55 AM LOG RSSI_5 = 0
155 1/21 5:55 AM LOG RSSI_4 = 0
156 1/21 5:55 AM LOG RSSI_3 = 0
157 1/21 5:55 AM LOG RSSI_2 = 0
158 1/21 5:55 AM LOG RSSI_1 = 0
159 1/21 5:55 AM LOG RSSI_0 = 0
160 1/21 4:51 AM LOG RSSI_9 = 2
161 1/21 4:50 AM LOG RSSI_9 = 1
162 1/21 3:39 AM LOG RSSI_9 = 3
164 1/21 2:00 AM LOG RSSI_3 = 3
165 1/21 2:00 AM LOG RSSI_1 = 3
166 1/21 1:56 AM LOG RSSI_8 = 3
167 1/21 1:35 AM LOG RSSI_0 = 3
168 1/21 1:29 AM LOG RSSI_2 = 3
169 1/21 1:26 AM LOG RSSI_5 = 3
170 1/21 1:22 AM LOG RSSI_7 = 3
171 1/21 1:10 AM LOG RSSI_4 = 3
172 1/21 12:49 AM LOG RSSI_8 = 0
173 1/21 12:49 AM LOG RSSI_7 = 0
174 1/21 12:49 AM LOG RSSI_5 = 0
175 1/21 12:49 AM LOG RSSI_4 = 0
176 1/21 12:49 AM LOG RSSI_3 = 0
177 1/21 12:49 AM LOG RSSI_2 = 0
178 1/21 12:49 AM LOG RSSI_1 = 0
179 1/21 12:49 AM LOG RSSI_0 = 0
180 1/20 11:04 PM LOG RSSI_5 = 3
181 1/20 9:53 PM LOG RSSI_5 = 2
182 1/20 9:41 PM LOG RSSI_9 = 2
183 1/20 8:56 PM LOG RSSI_8 = 3
184 1/20 8:42 PM LOG RSSI_5 = 3
185 1/20 8:42 PM LOG RSSI_2 = 3
186 1/20 8:38 PM LOG RSSI_0 = 3
187 1/20 8:30 PM LOG RSSI_7 = 3
188 1/20 8:29 PM LOG RSSI_9 = 3
189 1/20 8:16 PM LOG RSSI_4 = 3
193 1/20 7:50 PM LOG RSSI_3 = 3
194 1/20 7:44 PM LOG RSSI_1 = 3
195 1/20 7:43 PM LOG RSSI_8 = 0
196 1/20 7:43 PM LOG RSSI_7 = 0
197 1/20 7:43 PM LOG RSSI_5 = 0
198 1/20 7:43 PM LOG RSSI_4 = 0
199 1/20 7:43 PM LOG RSSI_2 = 0
200 1/20 7:43 PM LOG RSSI_1 = 0
201 1/20 7:43 PM LOG RSSI_0 = 0
202 1/20 7:30 PM LOG RSSI_9 = 2
203 1/20 7:30 PM LOG RSSI_8 = 3
204 1/20 7:30 PM LOG RSSI_7 = 3
205 1/20 7:30 PM LOG RSSI_6 = 3
206 1/20 7:29 PM LOG RSSI_5 = 3
207 1/20 7:29 PM LOG RSSI_4 = 3
208 1/20 7:29 PM LOG RSSI_3 = 2
209 1/20 7:29 PM LOG RSSI_2 = 3
210 1/20 7:29 PM LOG RSSI_1 = 3
211 1/20 7:29 PM LOG RSSI_0 = 3

Looking over the data, it appears that the sensors generally oscillate between reporting 0 and 3 for signal strength, and most/all report going to 0 at the same time.

Looking at this another way, here are the loop readings recorded before and after the alarm:
10 1/22 12:34 PM LOG RSSI_4 = 3
14 1/22 12:32 PM LOG RSSI_4 = 0
30 1/22 7:41 AM LOG RSSI_4 = 3
36 1/22 7:26 AM LOG RSSI_4 = 0
55 1/22 2:49 AM LOG RSSI_4 = 3
62 1/22 2:20 AM LOG RSSI_4 = 0
73 1/21 9:56 PM LOG RSSI_4 = 3

That is, signal strength was said to be a 3 at the time it reported being tripped.

At this point the wireless part of the HAI system has very low WAF and I am considering just ripping it all out if I can't find the problem and have it fixed.

Any help or guidance that HAI can provide here would be much appreciated. I really like the rest of the system but I bought this system as an alarm first; if it doesn't work reliably, then it's back to the drawing board.

There is a communications problem between your wireless receiver and your HAI system. The fact that most (if not all) of your monitored sensors went to 0 at the same time shows that the HAI controller lost communication with your wireless receiver. When this happens, the controller sets all burglary zones to "not ready" and zeroes the loop readings. This is treated like someone cut the wire to a hardwired sensor, but here it treats it like someone cut the wire to the receiver. I would check the wiring between the controller and the receiver to make sure that all connections are secure and that there are no intermittent opens or shorts.

As Scott showed, I'd also check the revision of your wireless receiver to make sure it has the latest firmware. If the wiring checks out you may want to contact HAI technical support about swapping out the receiver.

Brian, thanks for the fast reply! Your suggestion to check the wiring btwn the panel and the receiver is a great one. Other than visually inspecting the connections on both ends, are there other things you would recommend that I check, e.g. continuity check, etc?

Sometimes wiring problems can be difficult to track down, particularly if it's something like a staple piercing the insulation. You can disconnect the wires at both ends then check for any continuity between pairs of conductors. Also check for any continuity between each conductor and earth ground. Sometimes just reconnecting the wires will clear up the problem. Sometimes the terminal blocks aren't tightened sufficiently or there may be wire whiskers that can short between adjacent terminals.

Hi Brian-
I just wanted to provide you with an update. My installer replaced the wire btwn my panel and my receiver today, but i'm still seeing the same behavior in the logs (all wireless sensors go to 0 at the same time). My wireless receiver is revision D. Should I contact HAI technical support directly, or should I contact my vendor (I bought it from Martin at AO)?

Send an email to [email protected] and they'll contact you with the necessary information to get a replacement.

sigh, so I just put a (new) replacement 45a00-1 in place yesterday, and have accumulated about 20 hours of runtime and rssi logging, and i'm seeing the same behavior (strength for all sensors goes to 0 all at once, but strength is mostly at 3 for all sensors immediately prior)

the wiring between the panel and the receiver is new (and secure), and the receiver is new. any further ideas or guidance you can provide?

log data:
1 3/15 2:16 PM LOG RSSI_9 = 3
2 3/15 1:23 PM LOG RSSI_8 = 3
3 3/15 1:10 PM LOG RSSI_7 = 3
4 3/15 1:08 PM LOG RSSI_4 = 3
5 3/15 1:02 PM LOG RSSI_9 = 2
6 3/15 1:01 PM LOG RSSI_6 = 3
7 3/15 12:54 PM LOG RSSI_3 = 3
8 3/15 12:50 PM LOG RSSI_2 = 3
9 3/15 12:48 PM LOG RSSI_0 = 3
10 3/15 12:44 PM LOG RSSI_1 = 3
11 3/15 12:12 PM LOG RSSI_5 = 3
12 3/15 12:10 PM LOG RSSI_9 = 0
13 3/15 12:10 PM LOG RSSI_8 = 0
14 3/15 12:10 PM LOG RSSI_7 = 0
15 3/15 12:10 PM LOG RSSI_6 = 0
16 3/15 12:10 PM LOG RSSI_5 = 0
17 3/15 12:10 PM LOG RSSI_4 = 0
18 3/15 12:10 PM LOG RSSI_3 = 0
19 3/15 12:10 PM LOG RSSI_2 = 0
20 3/15 12:10 PM LOG RSSI_1 = 0
21 3/15 12:10 PM LOG RSSI_0 = 0
35 3/15 11:49 AM LOG RSSI_9 = 3
36 3/15 10:37 AM LOG RSSI_9 = 2
37 3/15 9:26 AM LOG RSSI_9 = 1
38 3/15 8:15 AM LOG RSSI_9 = 3
39 3/15 8:14 AM LOG RSSI_4 = 3
40 3/15 8:09 AM LOG RSSI_6 = 3
41 3/15 8:02 AM LOG RSSI_2 = 3
55 3/15 7:58 AM LOG RSSI_3 = 3
56 3/15 7:50 AM LOG RSSI_0 = 3
57 3/15 7:46 AM LOG RSSI_1 = 3
59 3/15 7:30 AM LOG RSSI_5 = 3
60 3/15 7:09 AM LOG RSSI_8 = 3
61 3/15 7:05 AM LOG RSSI_7 = 3
62 3/15 7:04 AM LOG RSSI_9 = 0
63 3/15 7:04 AM LOG RSSI_8 = 0
64 3/15 7:04 AM LOG RSSI_7 = 0
65 3/15 7:04 AM LOG RSSI_6 = 0
66 3/15 7:04 AM LOG RSSI_5 = 0
67 3/15 7:04 AM LOG RSSI_4 = 0
68 3/15 7:04 AM LOG RSSI_3 = 0
69 3/15 7:04 AM LOG RSSI_2 = 0
70 3/15 7:04 AM LOG RSSI_1 = 0
71 3/15 7:04 AM LOG RSSI_0 = 0
72 3/15 5:52 AM LOG RSSI_9 = 3
86 3/15 3:04 AM LOG RSSI_3 = 3
87 3/15 2:54 AM LOG RSSI_0 = 3
88 3/15 2:49 AM LOG RSSI_5 = 3
89 3/15 2:48 AM LOG RSSI_1 = 3
90 3/15 2:19 AM LOG RSSI_9 = 2
91 3/15 2:12 AM LOG RSSI_7 = 3
92 3/15 2:11 AM LOG RSSI_8 = 3
93 3/15 2:10 AM LOG RSSI_4 = 3
94 3/15 2:07 AM LOG RSSI_6 = 3
95 3/15 2:05 AM LOG RSSI_2 = 3
96 3/15 1:58 AM LOG RSSI_9 = 0
97 3/15 1:58 AM LOG RSSI_8 = 0
98 3/15 1:58 AM LOG RSSI_7 = 0
99 3/15 1:58 AM LOG RSSI_6 = 0
100 3/15 1:58 AM LOG RSSI_5 = 0
101 3/15 1:58 AM LOG RSSI_4 = 0
102 3/15 1:58 AM LOG RSSI_3 = 0
103 3/15 1:58 AM LOG RSSI_2 = 0
104 3/15 1:58 AM LOG RSSI_1 = 0
105 3/15 1:58 AM LOG RSSI_0 = 0
171 3/14 8:23 PM LOG RSSI_9 = 3
185 3/14 7:59 PM LOG RSSI_8 = 3
186 3/14 7:12 PM LOG RSSI_9 = 2
188 3/14 7:05 PM LOG RSSI_2 = 3
202 3/14 7:00 PM LOG RSSI_2 = 2
203 3/14 6:58 PM LOG RSSI_8 = 2
212 3/14 6:13 PM LOG RSSI_2 = 3
216 3/14 6:04 PM LOG RSSI_9 = 3
217 3/14 6:04 PM LOG RSSI_8 = 3
218 3/14 6:04 PM LOG RSSI_7 = 3
219 3/14 6:04 PM LOG RSSI_6 = 3
220 3/14 6:04 PM LOG RSSI_5 = 3
221 3/14 6:04 PM LOG RSSI_4 = 3
222 3/14 6:04 PM LOG RSSI_3 = 3
223 3/14 6:04 PM LOG RSSI_2 = 2
224 3/14 6:04 PM LOG RSSI_1 = 3
225 3/14 6:04 PM LOG RSSI_0 = 3

this behavior is still occurring. one thing i had not realized previously: the dropouts occur with great regularity, i.e. every 5 hours and 6 minutes (and have been since my earlier post in January). i don't have any automation which runs with that frequency. is there some internal operation in the OP2 which corresponds to this observed timing?

We are currently looking into what is causing the issue that you reported; however, we do not believe that it is related to the false alarm issue that you initially reported. I’ll let you know what we find.

Have you experienced any false alarms since you replaced the receiver?

Hi Scott-
thanks for the reply. I actually don't know about the false alarm issue, as I've left all my wireless zones bypassed.

Would it be sufficient for me to simply write a program to log if/when these wireless zones show "Not Ready", or do I need to restore these zones and watch for an actual false alarm?

Scott D said:

We are currently looking into what is causing the issue that you reported; however, we do not believe that it is related to the false alarm issue that you initially reported. I’ll let you know what we find.

Have you experienced any false alarms since you replaced the receiver?

Click to expand...