Initially I thought that was the setting I wanted, but that’s for the exit delay. I actually mean disabling the entry delay so that in Arm Stay mode, the panel alarms immediately if a door or window sensor is triggered, rather than allowing 30 seconds to enter the code to disarm. It’s an option you can choose when you arm directly from the panel or a keypad, but it doesn’t look like it can be set programmatically (or at least I haven’t found a way to do it).
Ah, ok. This driver is based on a disassembly of the Control3 driver that this integration is intended for. It's not publicly documented, so if there are other options that can be set in the json message that C3 doesn't use, there's no way to know unless Qolsys decides to publicly document the interface.
Hello, was wondering if anyone who had some success installing this app to point me on how would I install it myself
Basically I have installed it through HPM went through ok yet when I am trying to add it as a user app it is not in the list and I am not sure what am I doing wrong.
For reference I have the Qolsys2 and I have succesfully added it in Homebridge
No luck in HE though
I attached few screenshots to show what I am talking about
Thank you
It's a driver, not a user app. Installation instructions are here:
I was really dumb and didn't read everything in the instructions 
Please ignore
No problem 
I'd like to convert an older DSC (1616) system to use an IQP4 and bring along my 433 wireless contact sensors. Looks like this driver works great. (Thank you) For those using it do you have any feedback on the setup in general? Any reason not to go this way? Anyone know a source to allow me to buy components and DIY the whole thing?
My fallback is maybe Konnected or Invisilink, but they don't look as robust considering my desire to keep my contact sensors.
Sorry if I am hijacking the driver thread for general question.
Overall, I like it. The only downside I've seen is that it does force you to go to 6-digit alarm codes. That may affect your WAF (or not).
I'd also add that if the driver doesn't close the connection nicely, you may have trouble reconnecting to the panel. I've found the only way around this is to reboot the panel. It doesn't happen often, but may happen during setup.
As for DIY, I believe Surety will sell you just the panel (and whatever else you need) for a DIY install. https://suretyhome.com/store/
1 Like
I did that at two other houses (with an IQ2+) and had no issues. You just want to make sure you get the correct variant of the IQ4 that supports 433 mhz sensors.
If you install new sensors, I would recommend using PowerG sensors, but your old ones should work just fine. You also want to get the IQ4 variant that supports the cell network with the strongest signal where you live, either AT&T or Verizon. In most locations it might not make any difference.
No reason you can't DIY. Check out advancedsecurityllc.com or alarmgrid.com, I found they generally have the best prices. This stuff isn't hard to install.
Yeah, there was a workaround for that but they closed that loophole in the current firmware.
Strangely enough though, you can use 4 digit codes if you use Schlage z-wave door locks and program the panel to disarm when you unlock the door with the code. You still need to use 6-digit codes, but only the first four are sent to the lock when programming it (even though the Schlage lock does actually support 6 digit codes). I think this is a bug and pointed it out to both Qolsys and alarm.com but nobody seems to care.
We used 4-digit codes forever, so I just set digits 5 and 6 to zero, which achieved a passing WAF.
I haven't seen this happen in a long time, and never with the IQ4, only the IQ2+. Maybe a firmware issue that was resolved. My IQ4 has been rock solid for nearly a year now.
Thanks. Yea, I'm already in the product ID. IQP4005 for ATT and 433 support.
I wasn't sure about the technical requirement for the driver to work. It states it needs a dealer code so I wasn't sure how that works if you buy the correct product without an installer. Like if I found one on ebay or something. I'm preconditioned after having control4 to always assume there is a hook in every solution. Sort of like smart home PTSD.
1111 is the default installer code and 2222 is the default dealer code (a superset of installer code). Unless you found an incredible deal on ebay, I'd buy new with a warranty.
Also about buying used... there is no factory reset option available unless you can power up the panel and get into installer or dealer mode. There is no reset button or any sequence you can use on the power button to reset these things, no doubt for security purposes. So, if you buy a used unit and you don't get working codes, you bought yourself a doorstop.
Great tip and totally makes sense for this kind of product.
New on ebay is many $150 cheaper. Probably not worth the hassle.
I'm looking at my component options for 3 screens/kaypads, 433 support and less than 12 wired contact sensors. It's not clear to me yet what product I need for the additional screens/keypads.
Do these panels integrate just the same?
I've never seen the IQ Pro, but I'm no expert on this. I used to install alarm systems many years ago when the dinosaurs were still around, but I don't keep on top of any of this stuff anymore except for the things I personally use.
My only concern with the Pro panel would be if the firmware supports the C4 interface. If not, my driver won't work with it. Since it's targeted at commercial installations, it may not but I don't know much about C4.
If you want to keep your hardwire zones, you could use this: IQ HARDWIRE 16 – QOLSYS (although it doesn't specifically state that it works with the IQ4)
or this:
IQ HARDWIRE PowerG – QOLSYS
I'm using the PowerG model with an IQ2+ in an airbnb we have, where city ordinance requires us to have hardwired smoke detectors. But that only has 8 hardwired zones. With either one of those hardwire extender panels, you'd want to get the optional backup battery.
1 Like
I've got the IQ Panel 4. I had the issue when I was first setting up the integration in May. Ran into it again recently when I tried to have both the Hubitat integration and add a Home Assistant one running at the same time.
I suspect it's intentional and an intrusion prevention system. In theory, you'd only have one Control4 system connected to the panel, so running more than one at a time wouldn't be part of the design.
Based on posts on C4 forums it does work with C4.
I was reading through the firmware release notes for the IQ panels and saw there was a firmware update earlier this year that added partition support for control4.
Partitions are when you have one alarm system, but two areas that need separate alarming.
For example, a lock & leave pharmacy where the pharmacy area needs to be alarmed when the pharmacist leaves at 6pm, but the rest of the store doesn't get alarmed until 11pm after the grocers go home.
Or, in the home context, a pantry and fridge that need to be alarmed when the parents aren't home so the teenage boys don't eat all the food.
Yes, this is desirable especially with the distance support for this platform. Arming a detached garage for example.
My driver already does (or should) support partitions, that's why some of the attribute names end in "_Partition_x", The partition number is one of the fields in the data sent by the IQ panel.
However, I've never actually tested this with multiple partitions 
. The only panels I have available for testing are in active use, so I don't want to mess with the configurations too much. Perhaps that field never had anything other than "0" prior to this firmware release, but the driver will update the proper attribute for whatever number is in the partition field (or create a new attribute as needed).
1 Like
