Earlier it was stated that your IQ panel shows this IQ as connected, is that correct?
Can you verify the IP address of the IQ2 as it is listed in the IQ panel and the IQ2 settings?
Are you successfully registering the IQ2 to the IQ panel, then the IQ2 shows a failure to connect and control the IQ after?
On the IQ panel, the IQ2 shows as “active”. When I ping it, and go to the IQ2 and look at it, after a few seconds, the small red error box at the bottom will appear “Error: couldn’t connect to primary.” Currently, the IQ2 shows the correct time and appears to be working normally until you try to take an action, then it pauses for several seconds and the red error box again appears. This happens every time. I’ve tried the steps that Jason mentioned earlier numerous times. 192.168.1.104 is the IP address of the IQ2, which shows on both panels.
Thank you for the additional information.
Do you see any of the same symptoms described here?
If you try the same action from the IQ2 a few times, or try the same action a couple minutes later, does the IQ2 connect?
If you wake up the IQ2 by pressing the power button instead of the screen, do you see any difference in function?
Yes, it does seem that I have many of the same symptoms. However, if I choose syncing on the IQ2, I get the syncing failed message every time. The wake up button had no effect on the function when I tried it just now. If you try the same function a couple minutes later the same couldn’t connect to primary message appears. Also, something interesting, when I access the settings menu, I always have to use code 1234. It will never let me use my user code.
What type of wireless encryption are you using with your router? Have you tried changing this?
When you say you disabled 5ghz, did you hide the SSID, or did you disable the router from transmitting the 5ghz network altogether?
Earlier in this thread it looks like you stated that the IQ2 in question had begun to work properly, but failed again when a second IQ2 was introduced. Were you using this same router when it was working? Do you remember if any changes had been made on the network at that time?
Let me try adjusting some things on the router end and see how that goes. I’m not that familiar with that so I will need to read up on it. I did start out with an Apple Airport Extreme and switched to a Linksys WRT1900ACS after I read that Apple sometimes doesn’t play well with this type of equipment.
I disabled the 5ghz altogether. I don’t remember any other changes to the network during all this.
Finding incompatibilities due to settings limitations, etc., on a particular router is rare but has occurred in the past with some equipment. We have not noticed a specific instance yet with the IQ2, and either of the routers mentioned should likely allow access.
What may be an issue is the wifi network settings, but those can be edited fairly easily to test. After changing security settings, try resetting the IQ2, removing it from the IQ panel, and re-pairing.
Address reservation can be set up for the mac address of the IQ2 as well as a test.
I give up. I just can’t get it to connect effectively. Thank you for all the help.
Did you try changing the wireless security encryption method?
So we can update Qolsys and look into further possibilities, what have you tried as far as troubleshooting goes since the last update?
Yes sir, I tried changing the encryption method to every option I had on the router. I rebooted the IQ panel and the IQ2, removed and readded, pinged, resynced (not in that order). Nothing seemed to work. It looks like I get partial response to the IQ2 but no options will work directly from the IQ2. When I arm the system, the IQ2 will show the panel state and the date and time seems to remain correct and that’s it. The settings menu is accessible using the code 1234 but resync always fails. If you tap on anything else on the IQ2 to try to arm/disarm, check the weather info or home control, it freeze pauses a few seconds, then pops up the can’t connect to the primary error message.
Jason, I got the new panel from you today. I plugged it in and did another update on both the IQ panel and the two IQ2 (appears there was another update around 12/30). Anyhow, both IQ2 took the update (using iq215 patch code), came back up and seem to be working correctly and speedily too. Not sure what changed…I wish I did. Whatever it was, I hope it doesn’t change back. Thank you to you and the team there for helping me with this. Excellent job, as you have always done.
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 you have described. Qolsys has confirmed this new update is available now. It sounds like it did indeed resolve the issue.
I am having similar issues with my IQ2. When hitting the arm button, it would pause, the screen became dimmer, and then returned with the note that it was unable to connect. Eventually, I was able to arm the system from the IQ2 panel. Given that I was just testing the arming functionality, I went to cancel the arming command during the countdown. It requires you to re-enter your access code. When I did that, it said that it was an invalid user code, and continued the arming countdown. Turns out I had to user the master user code to disable the arming sequence.
When I repeat this from the main IQ panel, it allows me to enter the same user code (not the master) to arm the system and then when I go to cancel the arming sequence during the countdown, it will properly cancel when I enter the same code.
I have verified that the IQ2 is connected properly – I am able to enter the settings mode just fine. Why will the IQ2 not allow a regular, authorized user code to cancel the arming sequence where it will from the main IQ panel?
By the way, the IQ2 was not working properly when I first went to use it. Touched the settings button on the IQ2, it brought up the keypad, and then immediately returned to the main screen. I could not access the settings mode as a result. I powered down the IQ2 using the physical power button (not the one on the screen). After I turned the power on, the IQ2 seemed to work as it should as I was now able to access the settings mode and enter my code. However, I still had the disarming issue noted above when trying to abort the arming sequence with a regular, non-master, user code.
What is the firmware version on your IQ panel and your IQ2, respectively?
My IQ Panel is 1.5.1 and my IQ2 is 1.5. I recently updated both systems, including the new patch for the IQ2.
I still had the disarming issue noted above when trying to abort the arming sequence with a regular, non-master, user code
Just to clarify, it sounds like you were able to use a non-master to arm on the IQ2? Are you able to use that non-master to disarm after the countdown has completed?
So I tried a variety of tests with the IQ2. Here are the results.
I armed the IQ2 panel in stay mode with 4 non-master codes and tried to cancel out of arming mode with the same (or any) non-master code. It did not work. In each case, only master code would allow me to cancel out of arming mode during the countdown.
After accepting the fact that the IQ2 would not allow me to abort the arming sequence during countdown, I then let the system arm after the full countdown. When the countdown reached zero, in a few cases, a message popped up on screen saying “network connection failed…” and then eventually the IQ2 panel would go into the armed state. I checked the signal strength of the WIFI signal on the settings screen of IQ2 and it is showing full strength of WIFI network.
When I went to disarm the system, one of the non-master codes would disarm the system and then produce an alert on the IQ2 panel saying “invalid user to disarm” even though that user code did disarm the system. Other non-master codes would successfully disarm without the alert. So I deleted the “problem” user from alarm.com user management interface and re-added it. For now, that seems to have fixed the issue with that user code. I do not get any more “invalid user to disarm” alerts when I disarm with that user.
So I guess that leaves us where we started – the inability to abort the arming sequence once arming countdown has commenced with non-master user codes.
inability to abort the arming sequence once arming countdown has commenced with non-master user codes
Certainly seems strange. It is also just specific enough of a scenario to make me question whether it is intentional. It sounds like one of two things might be happening.
Your IQ2 is not syncing fully with the IQ still and may be having trouble verifying codes/commands it sends to the IQ.
This is a strange security feature of the IQ2.
I’ve sent your description to Qolsys.
Alright, I can report that the issues you are presenting should be expected and have been confirmed by Qolsys.
All user codes should be able to cancel the arming sequence from the IQ2, but Qolsys was able to replicate this. It will be fixed in upcoming updates. At this time, to cancel arming during the countdown from an IQ2 you will need to use the Master Code.
Connection issues are being ironed out. Can you check to make sure whether or not there is a newer version of the IQ2 software? Try patch tag iq215.
“Invalid user to disarm” is a known issue currently, but is only a local alert, and can be safely disregarded when disarming with a valid user code. It may be related to the inability to cancel arming during the countdown. It will also be fixed in upcoming software I am told.