Qolsys suggestions for further troubleshooting in this circumstance:
I tried all of that–to no apparent effect. The IQ2 still works most of the time, but still sometimes I have to select an option a few times before it will pull data from the primary (it gives me 2 or 3 “cannot connect to the primary panel” errors). I cannot figure out much of a pattern. It may be that when the IQ2 goes into “sleep” mode (or whatever it is called when the screen goes blank after a period of no use) that it takes a few tries to reconnect to the IQ. Just a thought.
One other thing to note. When I performed step 4 and repaired the IQ2, it didn’t automatically pair the IQ2. The IQ2 still showed a message that I needed to register the IQ2 with the primary panel. I had to go to Settings->Resync to get it to pair.
It may be that when the IQ2 goes into “sleep” mode (or whatever it is called when the screen goes blank after a period of no use) that it takes a few tries to reconnect to the IQ. Just a thought.
Not a bad thought. Are you only really noticing the slow response after the IQ2 has been woken from sleep mode?
Yes, it appears that way. Once it has connected after 2-3 tries, I havent experienced the error happening again until after it has gone back to sleep.
Another interesting thing I just noticed is that it doesn’t seem to have the problem when I wake it by pushing the power button instead of tapping the screen. At least that just worked for me when I tried it.
That’s some good info. I’ll discuss with Qolsys.
An issue with earlier IQs was that they were not designed to wake on touch. The way it was implemented is likely causing the problems you’re seeing now if these observations hold up.
The IQ2 patch tag: iq215, has been updated and a new version of the IQ2 1.5 update will be downloaded which addresses the issues described. Qolsys has confirmed this new update is available now.
I give up! I’ve gone through two update attempts, the last being a supposed beta (after v1.5) from QOLSYS and they’ve made my panels even less reliable, the symptom being losing connection with the main panel despite meter-pinning WiFi signal strength and no WiFi issues. So, I’ve replaced them with 7" Android tablets (Samsung Tab 3) running the alarm.com app. If you dedicate the tablet to this singular task and setup the tablet properly, the app will be displayed, starting with its user code screen*. The necessity of entering a user code before seeing anything is a small inconvenience, but it also gives security to arming the system. Also, a decent tablet has much better view-ability and ouch response tan the cheaply-made IQ2. There are some downsides: no way to manually initiate an alarm; no way to see the status of all devices (although you can view the changes to device statuses); no audio alerts. But the alarm.com app, with one exception, is bullet-proof and need not be on the same WiFi network as the IQ panel, which opens up a few additional networking opportunities if your remote panels are beyond the range of your WiFi access point.
The exception is that, when setting the alarm via the app, exit delays seem to be ignored. I’m trying to get someone at alarm.com and/or QOLSYS to look into this, as it is a serious issue.
*I’ve set the Android screen timeout to 2 minutes. After the screen blanks (or displays its wallpaper), tapping the “on/off” button will revert the device to the alarm.com app focused on the user code entry screen.
For what it is worth, I think my problem was not due to the firmware, but due to the fact that I have my wifi network transmitted over two different routers (the second is bridged to the first via a hard wired Ethernet connection). They both have the same network ID/name, so you never know exactly the particular router to which a device is connected. A device can move seamlessly between the two and be on the same network. In any case, I think my IQ and IQ2 were connected to different routers and that was causing the issue. I have them connected to the same router now and the IQ2 works perfectly. I didn’t even download the new IQ2 firmware because I tried this solution first and it worked.
A device can move seamlessly between the two and be on the same network. In any case, I think my IQ and IQ2 were connected to different routers and that was causing the issue. I have them connected to the same router now and the IQ2 works perfectly. I didn’t even download the new IQ2 firmware because I tried this solution first and it worked.
Thanks for following up with this.
Cameras can run into similar problems if multiple access points are present for a wifi network. Often you’ll see one connecting to a distant access point instead of the primary router, even if it is closer.
’ve gone through two update attempts, the last being a supposed beta (after v1.5) from QOLSYS and they’ve made my panels even less reliable, the symptom being losing connection with the main panel despite meter-pinning WiFi signal strength and no WiFi issues.
When was the last time you attempted to update? There have been a few patch versions released for the IQ2/IQ in the last few weeks.
Do you happen to have multiple access points in the home?
The exception is that, when setting the alarm via the app, exit delays seem to be ignored. I’m trying to get someone at alarm.com and/or QOLSYS to look into this, as it is a serious issue.
Correct, arming via the Alarm.com app has been designed to arm immediately, as it is assumed you are outside of the home, or settled in the home, when you arm. The app was not specifically designed to replace local controls.
In response to #44131:
Using two routers means using two networks (LANS), which is not good practice for any use, as it opens up huge potential security issues and other problems. It also seems that all the IQ devices have some inherent security tweaks which hide the devices from some network tools and I suspect that further makes multiple network access a bad idea.
I’m using a separate WiFi access point connected to my router and another identical unit configured as a repeater, using the same SSID. This should not cause any problems, but I continue to have connection issues with both IQ2s which appear unrelated to WiFi, even with the latest patch which was installed on 1/16/2016. I was assured that the patch was issued the previous week and was not yet an official release.
To rule out the WiFi issue, I disconnected my repeater and the repeater-dependent IQ2. Within 12 hours I had a cannot connect to main panel error on the active IQ2. In this case. both the IQ and IQ2 panel were within 8 feet of my access point, one separated by a single interior partition and one by a single floor. No other obstructions. Using my phone with the WiFi Analyzer app, the signal strength meter at both panels is pegged at its maximum value, -40 DB. That pretty much proves that WiFi is not the problem.
My alarm service, who provided the IQ2 patches, affirmed that this is a software problem and not WiFi related.
Thanks for the take on the alarm.com app’s insistence on arming with no exit delay. My alarm service confirmed that earlier. It’s unfortunate, because otherwise it’s far more reliable than the IQ2, and gives you an opportunity to use a much better piece of hardware with a bullet-proof app for less $. And, I should add, the alarm.com running devices can be on separate networks. So, until alarm.com adds a delayed entry option, I’m stuck with using a key fob and/or a smartphone to arm the system from the outside, even if it’s raining and my hands are full. I’ve suggested that QOLSYS should dump the IQ2s and just sell a modified version of the alarm.com app to work with any Android device. They could even offer an Apple version, for those users willing to spend $300 on an alarm access point/monitor.
My alarm service, who provided the IQ2 patches, affirmed that this is a software problem and not WiFi related.
This is ultimately true, and there have been three additional patch releases since the software was first available for manual download, but it appears to still be dependent on certain network characteristics. We do not see it in every case.
There have been differing causes found. In one instance at least, the presence of 2.4 and 5ghz networks caused the problem, with the IQ2 able to connect to either, and the IQ only on the 2.4.
Another option is to allow the auto-update function to download new versions when available. This will not grab firmware upon first release, but when it is made available for auto-update (and deemed fully stable)