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.