Qolsys IQ Panel 2 and 3rd party integration

Third party integrations
533

Difficult to identify exactly why we don’t know the zone, it could also be caused by something else if we fail loading a zone for some reason.
Adding a “maybe you need to refresh your panel token” message would be doable. Mind opening an issue on GitHub for that? Been quite taken recently for work, but I’m using GitHub to keep track of stuff that needs doing :slight_smile:

That should be “instant”. When adding sensors in the past, I identified there’s a panel event I’m not handling at the moment for a new sensor addition, which justifies why a newly added sensor wouldn’t appear immediately (planned to add that support when I get the chance, I’m waiting to receive my new sensors too so I’ll have means to test that properly). However, the next refresh from the panel should give the info about all the sensors, and have HA pick up on all the sensors (including the newly added). Restarting HA should be triggering that, but you could also try and restart the panel. Another way to make sure you get the newly information would be to force-clear MQTT as to make sure stale INFO results do not stick around (they shouldn’t, but better be safe).

I’d advise to look at the logs also if you’ve already restarted a few times. Do those sensors appear in the logs? What type of sensors are those?

534

Done. Now that I got it working, I love this integration - combined with my MQTT messages from BlueIris, it’s a huge part of my HA setup (and lets me cancel my expensive alarm.com subscription). Thanks for the hard work!

535

@XaF props to you! I finally got around to switching to your integration a couple months back and it’s rock solid! One day I’m gonna comb through your code and learn from you :slight_smile: . I’ve update my repo to point to you and highly recommend everyone on this thread to stop using ad-qolsys and upgrade to qolsysgw!

1 Like
536

@XaF
Ok, I found the issue, it actually did add to my entities, but for some reason I thought it was going to update the entity list automatically!

I do have one minor issue with the sensor that failed and was replaced. It’s a water sensor and it failed in the wet state. When I added the new sensor I named it the same name but it seems the new sensor is still stuck in the wet state.

This is probably an mqtt issue.

You mentioned force clearing mqtt. How do I actually do that?

Is that something I do in AD?

My mqtt broker is a local broker on my home network, same as HA but a ubuntu server.

If I deleted the device in HA would it reappear as the correct State ? Or should I rename the sensor?

537

Your extension is what started this for me, and gave me the will to write qolsysgw, so thanks a lot to you too for all that initial clearing of brushwood!

Oh interesting, upon restart it should have sent the information in the same MQTT topic with the current status as seen by the panel. Are you able to see what messages the panel is sending in the logs? The INFO message as answered by the panel when asked for by the extension should give interesting information as to the sensor status.

For the clearing out, the ways I can think of:

  1. You can manually empty the MQTT cache, which should repopulate things properly. Will most probably need a restart, at least of AppDaemon, and maybe of HA.
  2. You can use the mqtt_retain parameter of the extension and set it to false temporarily. Will definitely need AppDaemon to reload the extension, which should trigger the INFO message and should send all the things in MQTT without any retention flag, hence clearing it out.

It should reappear in the correct state if the name is the same, as it would generate the same unique ID for the entity. Logs would tell if there’s a conflict somewhere, or maybe something’s just stuck in MQTT!

538

@XaF

THanks, I think this is HA side issue. I was using MQTT explorer and I changed the name of the sensor at panel to “Mainfloor Washroon Flood 3” (with the spelling mistake) and indeed I see the correct information being sent to mqtt broker.

{"event": "ZONE_EVENT", "zone_event_type": "ZONE_UPDATE", "zone": {"id": "F2D6A1", "type": "Water", "name": "Mainfloor Washroon Flood 3", "group": "WaterSensor", "status": "Closed", "state": "0", "zone_id": 21, "zone_physical_type": 8, "zone_alarm_type": 0, "zone_type": 15, "partition_id": 0}, "version": 1, "requestID": "59318577-28f8-41b1-ac45-1aaea2379c2e"}

Then, I changed it back to “Mainfloor Washroom Flood” which was the original name, but I also have the alarm.com integration and so HA adds _2 to all duplicate sensors so the qolsysgw sensors have the _2 add to the sensor in HA.

this could be the problem here:

Logger: homeassistant.components.binary_sensor
Source: helpers/entity_platform.py:598
Integration: Binary sensor (documentation, issues)
First occurred: 9:34:51 PM (2 occurrences)
Last logged: 9:34:51 PM

Platform mqtt does not generate unique IDs. ID qolsys_panel_p0z21 already exists - ignoring binary_sensor.mainfloor_bathroom_flood_2

But I know the panel is broadcasting correctly, because I tampered the sensor, and thus is the mqtt explorer sent this entity imediately,

{"event": "ZONE_EVENT", "zone_event_type": "ZONE_UPDATE", "zone": {"id": "F2D6A1", "type": "Water", "name": "Mainfloor Washroom Flood", "group": "WaterSensor", "status": "Closed", "state": "0", "zone_id": 21, "zone_physical_type": 8, "zone_alarm_type": 0, "zone_type": 15, "partition_id": 0}, "version": 1, "requestID": "84224312-292a-4de8-88de-be78da5bd642"}

So, now, im not sure what to do. I could delete the sensor from the panel, add it again with a completely different name (Mudroom Washroom Flood), that should show up as a different sensor, and then eventually the the old “Mainfloor Washroon Flood” I can delete (but there is no option to delete it, which is strange).

In MQTT explorer, there is an option to “clear this topic” but everytime I press it, it says “make sure you know what you are doing”…which I don’t so I don’t press. But I think the issue lies in the HA environment.

UPDATE: Problem is solved. I followed these instructions using MQTT Explorer and delete the actual sensor from:

homeassistant/sensor/name_of_your_sensor/config

With MQTT Explorer I noticed there were duplicate names and the other variations of the same sensor. I deleted all of them by pressing the “Clear this topic”, and that deletes the sensor in HA after restart. This then cleared the error in the log file, and then I tampered the sensor and it eventually showed up, reporting correctly in HA.

Long story short, MQTT Explorer is a nice tool to have if you are having issues with MQTT sensors.

539

@XaF this intergration has been working rock solid. Thanks for your work on this.

Could you please add a battery status attribute? 100% = normal 10% = low battery warning.

Thanks. Thats the only thing I am missing from this intergration that I got from the nodered

540

Have you seen that information in payload messages sent from the panel? If so, please open an issue in github with all the example messages containing that information!

541

Hoping someone can help me. I’ve been struggling with the integration of Home Assistant and my IQ Pro+ panel for the last two days.

Fresh install of HA (RPI4)
Fresh install of HACS
Installed Mosquito MQTT
Installed qolsysgw with HACS
Added app.yaml in the /config/appdaemon/apps folder
Enabled control4 on the panel (and remote access, not sure if it makes a difference)
Populated app.yaml with the secure code and IP address of my panel

I noticed that I cannot ping the panel on the IP - assume this a security thing

I cannot access http ipaddress:12345 but I did get a browser warning about insecure certificate, but now I cannot reproduce it

I can access http ipaddress:8883 and it prompts for a certificate (expected?)

So… not sure if the panel is responding to TCP properly or not. Alarm system is fully functional, and I can access my security system with alarm.com

What am I missing?

542

Newbie here - I hadn’t installed appdaemon app, getting further now.

Seeing the error:

NamespaceException: (‘Unknown namespace (%s) in call_service from %s’, ‘mqtt’, ‘qolsys_panel’)

543

Anyone using the telus panel? Having an issue where I set the Control4 setting on the panel. It restarts and then after the restart the setting is still set. But if I check after a couple mins, its disabled. Not sure if this is a Telus specific issue or anyone else see this

544

Hey, I have an IQ Panel 2, not Plus too and I’m struggling with the same, can you help me?

545

Hey, I have an IQ Panel 2, not Plus, I can’t follow the instructions because, when I put the 1111 or 2222 code it says its wrong, with the master account I can access but there’s no Installation section or something else…that way I can’t enable 3rd party connections.
Any help please?

546

@ojoaosemtil Yes you definitely need to contact your dealer to give you the dealer code. Once you get that you’ll definitely be able to get this to work with your iq2 panel.

547

Hi were you able to figure this out? I am experiencing the same issue with Telus IQ Panel

548

Unfortunately not, I tried contacting support but they were no help. Putting it on hold for now until I can figure it out

549

I had inquired with TELUS and was told they will not release the dealer code, so if you’re able to get it that’s awesome. I went with another local company instead for that reason.

550

Actually, I noticed if you configure HA with the token, and starts showing in HA, even if you see the control3 checkbox is disabled you still can communicate with the panel. I can still see the entities active and up-to-date since I configured it the first-time. I hope this helps.

551

@XaF Is it possible from Home Assistant to delay trigger the alarm? Maybe I’m missing something, but when I trigger the alarm from Home Assistant, it goes straight to sounding the alarm without a chance to input a pin to stop it.

552

Yes that’s what triggering does, it does not switch to “pending” (which is the delay before alarm is triggered) but it triggers immediately. I have not found any way to ask the panel to beep and ask for the code unfortunately!