[RELEASE] QolSys IQ Alarm Panel Drivers

Thanks that worked great. Is there anyway to change the background color of the tile based on what state the alarm is in?

Honestly I have no idea as I really don't use dashboards very much. Maybe not with the built-in dashboards, but probably is doable with a third-party dashboard or via CSS somehow. I just never personally found much use for dashboards.

I just bought a house with a a Qolsys IQ4 and decided to combine it with hubitat. I have a C7 hub. Anyway, it seems ive done everything successfully to this point. I installed the packet manager and the drivers for the alarm system/ monitors. However, now that i see my alarm system in the device list, it isn't showing the child devices that are linked with the panel. I thought they would appear automatically, am i missing something?

Did you enable the Control4 interface and retrieve the token? Instructions are in the Github link of the first post.

I believe i enabled the C4 interface.. i did get the token.. i switched back to 4 digit code though. Thanks for the speedy response!

Pretty sure that is your issue. Re-enable the 6 digit code. Check the token to see if has changed.

Yep, that's the problem. For whatever reason, you are forced to use 6-digit user codes if you enable the C4 interface. Switching back to 4-digit codes turns off the C4 interface.

On the older IQ2+ panels, you used to be able to switch back to 4-digit codes and the C4 interface would remain enabled, but that was changed in a subsequent firmware update. That was never possible with the IQ4 though.

Yes! After re-enabling 6 digit codes, I now have the child devices showing. Thanks for your help!

Still working out kinks though.. I am able to arm the HSM through the device page, but when attempting to disarm, it states invalid code? Also unable to arm/disarm through the dashboard.

One other "gotcha" is that you can only have one device talking to the C4 interface, it seems.

I had Hubitat and HomeBridge both trying to use it, and periodically the panel would decide to just not talk to either of them without a reboot. Rebooting solved it (for a while), as did changing to only having one of the two talking to the panel.

@dcaton1220 just needed to come here and say you are a lifesaver with these drivers. It took some time to figure out how Hubitat wanted the variables mapped but the Qolsys drivers you built for the integration are working great for us.

Does anyone know if this supports the IQ Pro?

Yes it does.

Just an fyi in the event anyone experiences this. I don't know if it has anything to do with connecting to Hubitat (yet), but over the past two months I have experienced two events where the IQ4 panel becomes non-responsive on certain alarm screens during part of the arming process and then on the home screen to disarm. Perhaps my panel is going bad, but perhaps not.

If this happens to you, you will need to call your home security providers technical people (in my case Brinks). I needed third level tech support. They need to do a hard reset on the device. (this of course is after a long time trying other things.) This cannot be done via the panel. (according to them)

This first happened after incorporating the panel into Hubitat. Was fixed by the hard reset, and then within 24hrs of me re-adding the integration this week. So, perhaps my panel. I will not longer be integrating it if I don't have the problem for a month.

Just wanted to let people know of my experience.

Can't say I've ever seen or heard of that before. If your screen becomes unresponsive, yet it can be reset remotely by Brinks, then clearly it still is operational at some level and is able to communicate by cell and/or internet.

Sounds like a problem with the panel itself. The HE integration for the most part just listens to status reports sent out by the panel. Only if there's no incoming data for a certain time will the driver it close and re-open the connection.

Is your panel on the latest firmware?

4.4.2.2 with a whole bunch of numbers and then rc0013

Has anyone had success in getting an IQ Lock (Qolsys IQ Lock-PGK) setup as a child device in HE?

I have been using this driver for quite some time (huge thanks to @dcaton1220). All of the functionality has worked flawlessly. However, I have two Qolsys IQ Lock-PGK connected to my IQP4 via PowerG that I have never been able to see in HE.

I realize that this driver is designed to support “most commonly used alarm sensors such as door contacts, motion sensors, smoke and CO detectors, etc” and “z-wave devices are not exposed by the interface these drivers use” which is one of the reasons I’ve waited so long to ask this question.

Given that these locks are connected directly to the panel in the same way the contact and motion sensors are connected (PowerG), I’ve been holding out hope that there would be a way to integrate with Hubitat. Is this or will this be possible or should I start looking to replace the IQ Locks?

All of the devices exposed so far by the C3 interface have been status-only. Of course, there's really no commands you can send to an alarm sensor anyhow.

Turn on debug logging for the panel driver, then do a refresh and see if the lock shows up in the list of sensors returned. Even if it does however, there may be no way to control it, just detect its status.

Direct message with screenshot of log sent.

Sorry but that's making me cross-eyed. Can you copy and paste that into a text editor, then search for whatever name you've given the door lock in the alarm panel setup?

Sure thing. But, before I ask you to go through any more brain damage, I'll let you know that there is no sign of the locks in the logs.