The fact you’re seeing “Installer Settings” in your screenshot shows that you have the installer code, not the dealer one!
I was able to get one from the US in the end, and fetch it while on a trip! Price was not great, but at least I have a working panel now. Thanks a lot for your help! Will keep your email and might reach out still 
1 Like
Question for IQ Panel 4 users: besides the steps to enable control4 and get the token, anything you had to do for your panel to accept connections? Mine seems to have the port 12345 closed, so I’m wondering what I’m missing here (my IQ Panel 2+ didn’t have that issue in the past AFAIR)
$ nmap -p12345 192.168.x.x
Starting Nmap 7.70 ( https://nmap.org ) at 2022-12-14 10:55 EST
Nmap scan report for 192.168.x.x
Host is up (0.0020s latency).
PORT STATE SERVICE
12345/tcp closed netbus
Nmap done: 1 IP address (1 host up) scanned in 0.17 seconds
EDIT: after checking again my parameters, for some reason my IQ Panel 4 had disabled Control4 again? But I’m not crazy, I enabled it, since I had the token… Trying to re-enable that now, and will update after.
EDIT 2: after enabling again Control4, the port was still not showing up. I had to regenerate the token a few times, after 1 or 2 times, the port randomly appeared as open, but the token was not working. I regenerated it again, and this time it worked properly! My automation is back to working
Will your integration work with IQ4 panel now (or has been working with)? I’m still using an IQ2 panel and its been rock solid for over 5 years now…but, when the day comes I have to replace it, the next logical choice is the Iq4
It is already working with the IQ panel 4! Following comments from people in this thread, it has been working with it since software update 4.1. And I can confirm with the one freshly installed for me that it’s working well
1 Like
great news all around! This is one of my most important integrations and happy to know this!
after checking again my parameters, for some reason my IQ Panel 4 had disabled Control4 again?
What did you do to get the setting to stick? Every time I enable the third-party option, reboot, grab the token…a few minutes later the option is unchecked. Same thing over and over.
Just re-enabled it, and this time after reboot it was still on! Didn’t have to cycle more times. And after that I had to cycle my token once or twice until getting one that allowed to connect for some reason. But didn’t have to fight that much for the control4 enablement to stick. Are you on the latest version of the panel?
Thanks. I just tried it a few more times, and think I got it to stick. I’m seeing all activity now in the Appdaemon logs. But I can’t get any entities to show up in Homeassistant. Did I miss a step?
Is your MQTT configured properly?
Do you have the MQTT plugin enabled and configured in home assistant?
Do you have MQTT discovery enabled in home assistant? (Should be by default but…)
I had an old MQTT integration that was messing everything up. Deleted
them all. Reinstalled the right one. On my way. Appreciate all the work on this!
Hey there community!
For those of you using qolsysgw, you’ve probably seen that during the holidays, I’ve had the chance to finish working on setting up proper testing, which means that it’s way easier for me now to fix bugs & bring new features to qolsysgw without risking to break what’s working. Even more: I can now make sure that qolsysgw keeps working through updates of AppDaemon and Home Assistant.
The list of issues should be up to date with the features that people have requested, including some sensors (that I am lacking information for at the moment). So if you see this message, please go take a look at what’s currently planned to be worked on at some point (Issues · XaF/qolsysgw · GitHub) and don’t hesitate to add details if you have any, and maybe a 
on the issues that matter to you the most.
Also, if you have examples of interactions with the panel that are not yet listed in qolsysgw/qolsys-panel-interactions.md at 44d29112be699bfbac015be848939997202e0221 · XaF/qolsysgw · GitHub I would love to know about them (even more if those allow us to grab more information on the panel sensors, for instance!)
Until then, hope you still enjoy using qolsysgw, and I wish you happy holidays! 
3 Likes
Thanks for the amazing work XaF! I wanted to share EHylands work, thanks to them there’s another way to integrate Qolsys panels, they wrote this Homebridge plugin, which should allow HASS users to integrate via the HomeKit Controller integration. Best part is no configuring of AppDaemon or MQTT needed, just your access token. I’m so happy to see wonderful devs working on these panels!
Hi @ifeign
Thank you for you kind words.
Please give credit to @dcaton who is the major source of inspiration for my Homebridge plugin.
I know sanjay900 was able to successfully port my Homebridge Bosch plugin to Home Assistant without MQTT. It may be helpfull to look at: GitHub - sanjay900/solution3000-home-assistant: This integration allows for connecting home assistant to a solution 2000 or 3000 panel.
1 Like
Just curious if you figured out the issue here.
When I do voice commands through Google Assistant (Nabu Casa) the actions work but then as you also said, Google immediately says “there was an error”… But it works?
I use Google Assistant without Nabu Casa so I’m not sure if it behaves differently, but yes, the alarm still arms via Google Assistant, but the Google Assistant reports a problem every time.
@duncan.lewis @Asamriaz
I am looking in to (eventually) getting an alarm panel and have been very disappointed with the sort of products available in the UK. However I recently noticed that ADT UK are reselling Qolsys IQ 4 panels to consumers and according to their website picture the Qolsys IQ 2 to business. (The business page may merely have an out of date image.) I also discovered that not only did Johnson Controls buy Qolsys but they also bought Tyco and ADT - hence ADT now reselling Qolsys panels.
As you both appear to be UK users of the Qolsys panel, did you get it via ADT or some other route? I would not have thought ADT would provide you with the dealer and installer codes you need to set it up with Home Assistant.
If your Qolsys panels are UK sourced, do they have the proper EU frequency for Z-Wave devices? A US panel would obviously have the US Z-Wave frequency instead.
One thing I am interested in doing is getting the Qolsys IQ Hardware 16 adapter to allow using wired sensors and a wired external siren. This is not listed on the Qolsys UK website nor on the ADT website although reading between the lines on the ADT UK Business system page they do talk about linking wired sensors to the Qolsys panel. Apart from the IQ Hardware adapter allowing the use of a wired external siren - which does not need a battery, it would also allow using indoor sensors also without needing batteries. (This is more beneficial in terms of the external siren which would be high up an external wall.)
Note: The Qolsys IQ Hardware 16 adapter works by having the wired sensors connected to it and then translating the signals to PowerG wireless signals. This is somewhat clever as it does not have to be connected directly to the Qolsys panel which sees them as PowerG wireless devices.
Anyone any thoughts as to whether Qolsys will eventually support the new Matter standard?
Anyone any more details about what types of ‘smart’ camera can be used with the Qolsys? Is this any Onvif compatible camera? I am wondering if the version of the Skybell Trim sold by Alarm.com and ADT is a special version with Onvif support whereas I believe the normal Skybell version does not.
Dear people,
I got qolsysgw working as far as I can tell. I see it idle in AppDaemon, but my question is. Do the entities get added automatically to Home Assistant or do you have to add them manually in configuration.yaml. I can’t really get that from the documentation.
2023-02-11 09:24:00.879757 INFO AppDaemon: Initializing app hello_world using class HelloWorld from module hello
2023-02-11 09:24:00.882012 INFO AppDaemon: Initializing app qolsys_panel using class QolsysGateway from module gateway
2023-02-11 09:24:00.976207 INFO hello_world: Hello from AppDaemon
2023-02-11 09:24:00.978143 INFO hello_world: You are now ready to run Apps!
2023-02-11 09:24:00.985578 INFO qolsys_panel: Starting
2023-02-11 09:24:00.994667 INFO qolsys_panel: Started
2023-02-11 09:24:00.995701 INFO AppDaemon: App initialization complete
2023-02-11 09:24:01.019381 INFO qolsys_panel: Establishing connection to 192.168.1.139:12345
I apologize in advance for this basic question, but I’m stuck at this point, I also don’t have that much experience with adding sensors manually.
EDIT: I’ve been playing around some more, with the MQTT broker, now it shows the partition and the sensors. So they are added automatically.
By default, MQTT discovery is enabled in Home Assistant. So if you haven’t changed that, it means that the sensors should appear automatically.
To figure out what’s happening, you can:
- Listen to the MQTT topics in Home Assistant to see if messages are received properly
- Set
log_level: DEBUGinapps.yamlforqolsysgwin order to see more logs in AppDaemon
EDIT: just saw your EDIT
1 Like
not sure how to fix these missing files?
i have a telus qolsys 4 panel on 4.2**** control4 enabled and connected to my home wifi, I was able to attempt to connect to the panel via browser
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: AppDaemon
Python Apps and Dashboard using AppDaemon 4.x for Home Assistant
-----------------------------------------------------------
Add-on version: 0.11.0
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (amd64 / qemux86-64)
Home Assistant Core: 2023.2.5
Home Assistant Supervisor: 2023.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-appdaemon: starting
s6-rc: info: service init-appdaemon successfully started
s6-rc: info: service appdaemon: starting
s6-rc: info: service appdaemon successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[23:12:25] INFO: Starting AppDaemon...
2023-02-18 05:12:30.750778 INFO AppDaemon: AppDaemon Version 4.2.1 starting
2023-02-18 05:12:30.751090 INFO AppDaemon: Python version is 3.10.9
2023-02-18 05:12:30.752899 INFO AppDaemon: Configuration read from: /config/appdaemon/appdaemon.yaml
2023-02-18 05:12:30.753099 INFO AppDaemon: Added log: AppDaemon
2023-02-18 05:12:30.754251 INFO AppDaemon: Added log: Error
2023-02-18 05:12:30.754860 INFO AppDaemon: Added log: Access
2023-02-18 05:12:30.755383 INFO AppDaemon: Added log: Diag
2023-02-18 05:12:30.952752 INFO AppDaemon: Loading Plugin HASS using class HassPlugin from module hassplugin
2023-02-18 05:12:31.263625 INFO HASS: HASS Plugin Initializing
2023-02-18 05:12:31.265957 INFO HASS: HASS Plugin initialization complete
2023-02-18 05:12:31.267168 INFO AppDaemon: Loading Plugin MQTT using class MqttPlugin from module mqttplugin
2023-02-18 05:12:31.390853 INFO MQTT: MQTT Plugin Initializing
2023-02-18 05:12:31.394242 INFO MQTT: Using 'mqtt-client/status' as Will Topic
2023-02-18 05:12:31.394739 INFO MQTT: Using 'mqtt-client/status' as Birth Topic
2023-02-18 05:12:31.395001 INFO MQTT: Using appdaemon_mqtt_client as Client ID
2023-02-18 05:12:31.396064 INFO AppDaemon: Initializing HTTP
2023-02-18 05:12:31.398555 INFO AppDaemon: Using 'ws' for event stream
2023-02-18 05:12:31.405360 INFO AppDaemon: Starting API
2023-02-18 05:12:31.417312 INFO AppDaemon: Starting Admin Interface
2023-02-18 05:12:31.420901 INFO AppDaemon: Starting Dashboards
2023-02-18 05:12:31.457089 INFO HASS: Connected to Home Assistant 2023.2.5
2023-02-18 05:12:31.492752 INFO MQTT: Connected to Broker at URL 192.168.1.8:1883
2023-02-18 05:12:31.506188 INFO AppDaemon: App 'hello_world' added
2023-02-18 05:12:31.507841 INFO AppDaemon: Got initial state from namespace mqtt
2023-02-18 05:12:31.508636 INFO MQTT: MQTT Plugin initialization complete
2023-02-18 05:12:31.522461 INFO AppDaemon: App 'qolsys_panel' added
2023-02-18 05:12:31.526768 INFO AppDaemon: Found 2 total apps
2023-02-18 05:12:31.528174 INFO AppDaemon: Starting Apps with 2 workers and 2 pins
2023-02-18 05:12:31.530277 INFO AppDaemon: Running on port 5050
2023-02-18 05:12:31.686071 INFO HASS: Evaluating startup conditions
2023-02-18 05:12:31.709327 INFO HASS: Startup condition met: hass state=RUNNING
2023-02-18 05:12:31.710506 INFO HASS: All startup conditions met
2023-02-18 05:12:31.958546 INFO AppDaemon: Got initial state from namespace default
2023-02-18 05:12:32.182891 INFO MQTT: Unable to decode MQTT message
2023-02-18 05:12:33.542139 INFO AppDaemon: Scheduler running in realtime
2023-02-18 05:12:33.549683 INFO AppDaemon: Adding /config/appdaemon/apps to module import path
2023-02-18 05:12:33.551346 INFO AppDaemon: Adding /config/appdaemon/apps/qolsysgw to module import path
2023-02-18 05:12:33.552681 INFO AppDaemon: Adding /config/appdaemon/apps/qolsysgw/qolsys to module import path
2023-02-18 05:12:33.555570 INFO AppDaemon: Adding /config/appdaemon/apps/qolsysgw/mqtt to module import path
2023-02-18 05:12:33.603075 INFO AppDaemon: Loading App Module: /config/appdaemon/apps/hello.py
2023-02-18 05:12:33.668138 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/gateway.py - ignoring
2023-02-18 05:12:33.670164 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/observable.py - ignoring
2023-02-18 05:12:33.671569 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/state.py - ignoring
2023-02-18 05:12:33.674213 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/partition.py - ignoring
2023-02-18 05:12:33.677441 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/events.py - ignoring
2023-02-18 05:12:33.679231 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/exceptions.py - ignoring
2023-02-18 05:12:33.680688 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/actions.py - ignoring
2023-02-18 05:12:33.682558 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/control.py - ignoring
2023-02-18 05:12:33.684331 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/utils.py - ignoring
2023-02-18 05:12:33.686392 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/socket.py - ignoring
2023-02-18 05:12:33.694431 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/config.py - ignoring
2023-02-18 05:12:33.696835 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/qolsys/sensors.py - ignoring
2023-02-18 05:12:33.698354 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/mqtt/listener.py - ignoring
2023-02-18 05:12:33.700110 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/mqtt/exceptions.py - ignoring
2023-02-18 05:12:33.706954 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/mqtt/utils.py - ignoring
2023-02-18 05:12:33.708500 WARNING AppDaemon: No app description found for: /config/appdaemon/apps/qolsysgw/mqtt/updater.py - ignoring
2023-02-18 05:12:33.710645 INFO AppDaemon: Initializing app hello_world using class HelloWorld from module hello
2023-02-18 05:12:33.864171 INFO hello_world: Hello from AppDaemon
2023-02-18 05:12:33.869588 INFO hello_world: You are now ready to run Apps!
2023-02-18 05:12:33.874025 INFO AppDaemon: App initialization complete