Qolsys IQ Panel 2 and 3rd party integration

Third party integrations
149

Got it

image

150

That worked.

151

Nice!

I have orderd a new alarm system with this panel, hopefully it will arrive in the comming weeks so that I can try this app.

152

It works!!! Now to write some sensors in home assistant…

root@pi3:~ # mosquitto_sub -h hassio -u hassio -P <removed> -v -t "qolsys/#"
qolsys/panel/zone_event {"event":"ZONE_EVENT","zone_event_type":"ZONE_ACTIVE","version":1,"zone":{"status":"Open","zone_id":8},"requestID":"2150deb9-0d21-4381-8b22-64f674497c17"}
qolsys/panel/zone_event {"event":"ZONE_EVENT","zone_event_type":"ZONE_ACTIVE","version":1,"zone":{"status":"Closed","zone_id":8},"requestID":"2829aee0-52a3-447b-ba23-b965611d854f"}
153

If you use mqtt doesn’t this automatically create the sensors?

154

Thank you @Atliant!

yes. @mzac did you disable mqtt discovery?

155

Yep it did, but it didn’t create all of them. Only the door sensors showed up. Here are others I have that didn’t show up:

{
    "id": "xxx",
    "type": "GlassBreak",
    "name": "Kitchen Glass Break",
    "group": "glassbreak",
    "status": "Closed",
    "state": "0",
    "zone_id": 4,
    "zone_physical_type": 12,
    "zone_alarm_type": 0,
    "zone_type": 19,
    "partition_id": 0
},
{
    "id": "xxx",
    "type": "SmokeDetector",
    "name": "Basement Smoke Detector",
    "group": "smoke_heat",
    "status": "Closed",
    "state": "0",
    "zone_id": 5,
    "zone_physical_type": 9,
    "zone_alarm_type": 9,
    "zone_type": 5,
    "partition_id": 0
},
{
    "id": "xxx",
    "type": "Motion",
    "name": "Upstairs Motion Detector",
    "group": "awayinstantmotion",
    "status": "Closed",
    "state": "0",
    "zone_id": 8,
    "zone_physical_type": 2,
    "zone_alarm_type": 3,
    "zone_type": 2,
    "partition_id": 0
},
{
    "id": "xxx",
    "type": "Water",
    "name": "Water",
    "group": "WaterSensor",
    "status": "Closed",
    "state": "0",
    "zone_id": 14,
    "zone_physical_type": 8,
    "zone_alarm_type": 0,
    "zone_type": 15,
    "partition_id": 0
},
156

Added sensor types in v1.2 (see Other zone types · Issue #2 · roopesh/ad-qolsys · GitHub)

157

I still haven’t even gotten mine to work yet. lol Might be because I don’t know much about mqtt

158

Do you have an MQTT broker already? If not, the Add-on works fine.

159

Well that’s a good sign, I got a topic for the appdaemon now. lol

160

So I am seeing this in the logs of appdeamon.

2021-04-08 16:21:10.413824 WARNING qolsys_panel: ------------------------------------------------------------


2021-04-08 16:21:10.414829 WARNING qolsys_panel: Unexpected error in worker for App qolsys_panel:


2021-04-08 16:21:10.415818 WARNING qolsys_panel: Worker Ags: {'id': '3216028e7f9b4f6dba70de4de7d53770', 'name': 'qolsys_panel', 'objectid': 'b3fa10c4654445349b5f93e1ba192a93', 'type': 'event', 'event': 'MQTT_MESSAGE', 'function': <bound method MQTTSubscriber.mqtt_zone_event_event_received of <qolsys_requests.MQTTSubscriber object at 0x7faf35be20>>, 'data': {'topic': 'qolsys/panel/zone_event', 'wildcard': '#', 'payload': ''}, 'pin_app': True, 'pin_thread': 0, 'kwargs': {'topic': 'qolsys/panel/zone_event', '__thread_id': 'thread-0'}}


2021-04-08 16:21:10.416637 WARNING qolsys_panel: ------------------------------------------------------------


2021-04-08 16:21:10.417801 WARNING qolsys_panel: Traceback (most recent call last):


  File "/usr/lib/python3.8/site-packages/appdaemon/threading.py", line 936, in worker


    funcref(args["event"], data, self.AD.events.sanitize_event_kwargs(app, args["kwargs"]))


  File "/config/appdaemon/apps/ad-qolsys/qolsys_requests.py", line 57, in mqtt_zone_event_event_received


    self.mqtt_zone_update_event_received(event_name, data, kwargs)


  File "/config/appdaemon/apps/ad-qolsys/qolsys_requests.py", line 29, in mqtt_zone_update_event_received


    zone = payload_json["zone"]


KeyError: 'zone'


2021-04-08 16:21:10.418659 WARNING qolsys_panel: ------------------------------------------------------------
161

Do you have mqtt configured? Are all the topics discreet?

162

I do have mqtt configured. The zigbee2mqtt and zwavejs2mqtt are showing up.

What do you mean discrete?

163

Can you post the config from apps.yaml?

164

Anyone using this in the UK ? (or EU)

I’m interested in if the panels are locked to an LTE carrier - they seem to be sold as AT&T Verizon etc. Would like it to work with a UK carrier obviously.

I have the AppDaemon integration running but no panel yet! Should it publish anything to MQTT in that scenario (I see the socket fail) - perhaps an LWT message…

165

I mean each of the topics configured in apps.yaml must be distinct from any other topic. That’s the first reason i’d imagine you’d have that error.

166

no it would not. it needs the panel config to do anything.

167

Give me a bit. I’m having some weird issues with the mqtt broker.

168

qolsys_panel:
module: qolsys_client
class: QolsysClient
mqtt_namespace: mqtt
qolsys_host: 192.168.7.1
qolsys_token: ABCDEF
qolsys_port: 12345 # Optional
request_topic: qolsys/requests # Optional
qolsys_info_topic: qolsys/panel/info # Optional
qolsys_zone_update_topic: qolsys/panel/zone_update # Optional
qolsys_zone_event_topic: qolsys/panel/zone_event # Optional
qolsys_alarming_event_topic: qolsys/panel/alarming # Optional
qolsys_disarming_event_topic: qolsys/panel/disarm # Optional
qolsys_disarm_code: 1111 # Optional - Required if you want to disarm the panel
qolsys_confirm_arm_code: False
qolsys_confirm_disarm_code: False