were you able to get to working? I’m struggling with mine… sort of a beginner thou… when I arm and disarm alarm I get msgs in MQTT when I listen to the topic… I moved the folder to the root folder like someone stated above… and still I can’t see the app loaded in appdaemon… can someone help?
@bumpyj38 @bcre3306 #FriedCheese
I also can’t find /hass/config/appdaemon/apps/apps.yaml. It goes to a blank page. How did you find where the apps.yaml is?
Mine was located in /addon_configs/a0d7b954_appdaemon/apps/apps.yaml.
I found this by searching the filesystem because it wasn’t located where the documentation mentioned. Note I think the a0d7b954 directory may be random directory but not 100% sure but it should be in the same /addon_configs directory.
Hope that helps
Oh It’s not a random directory. It’s the same!
I found it from the terminal using find / -name “apps.yaml” 2>/dev/null
Thank you!
I was going to tell you to do it that route but wasn’t sure if you had it installed so didn’t want to add more confusion! Glad you found it
Can anyone help me out? I can’t seem to connect to Mosquitto/MQTT Broker. This is what I get in the logs:
New connection from 172.30.32.1:35518 on port 1883.
error: received null username or password for unpwd check
Client appdaemon_mqtt_client disconnected, not authorised.
New connection from 172.30.32.1:52966 on port 1883.
error: received null username or password for unpwd check
Client appdaemon_mqtt_client disconnected, not authorised.
I’m not sure what 172.30.32.1 is coming from and the port changes.
In AppDaemon logs I get:
CRITICAL MQTT: Could not complete MQTT Plugin initialization, trying again in 5 seconds
CRITICAL MQTT: Could not Complete Connection to Broker, please Ensure Broker at URL 192.168.x.xx:1883 is correct and broker is not down and restart Appdaemon
Would something like this work to bypass a specific zone ? Aka stop a door from making a sound when opening. This is when the system is NOT armed.
service: mqtt.publish
data:
topic: "qolsys/command"
payload: >
{
"event": "BYPASS_ZONE",
"zone_id": "your_zone_id_here",
"panel_code": "your_panel_code_here"
}
I believe the user/pass should be your HA user/pass as I assume the MQTT service you’re running is in HA addons. The 172 IP is the container that MQTT is running in within the HA.
Has anyone ever got silent arming working on home stay? If so how did you do that ? It works via alarm.com
While struggling to get qolsysgw to see my IQ2, I decided to start from scratch with a fresh install of HAOS. Setup of each individual part (MQTT Broker, AppDaemon, HACS, Qolsys Gateway, and the MQTT integration) all went very smoothly but none of my panel sensors would show up.
I finally realized that I was seeing different file paths during the Configuring Qolsys Gateway step. The documentation says I should edit the /hass/config/appdaemon/apps/apps.yaml file, but my apps.yaml was located at /addon_configs/a0d7b954_appdaemon/apps/apps.yaml.
HACS was putting the qolsysgw/ directory in /hass/config/appdaemon/apps/ but my AppDaemon seems to be unable to see that directory. The fix was to copy the qolsysgw/ directory over to /addon_configs/a0d7b954_appdaemon/apps. When moved to the correct directory, everything worked like a charm but I worry that any updates via HACS will not know that my qolsysgw/ directory is in a different location.
Is there a step I missed which would have caused my AppDaemon to be built in the wrong directory or is this the result of an update which the qolsysgw application does not know about?
Hi I’m very new to the whole appdeamon and I’ve followed all the steps outlined in both the qolsys and appdeamon setup procedures but when i watch the logs of appdeamon I never see it attempt to load the qolsys gateway app I’m sure I’ve probably missed something but I’ve been at it for weeks and have tried removing both and doing it all again but i get the same results i had to create the apps.yaml and the appdemon.yaml files and i see the hass not mqtt or the qolsys app. I’ve tried looking for the addon_configs folder but doesn’t seem to exist for me, any help would be greatly appreciated.
It’s possible you’re experiencing the same issues I was having and outlined in the post above yours.
If you cannot find that addon_configs folder, you might need to point VS Code (if you’re using that) at the root directory. Click the Menu button > File > Close Folder. Then, open a new root folder (Menu > File > Open Folder > /root/). This is what helped reveal that addon_configs folder for me.
You can then copy and paste the qolsysgw/ directory over to /addon_configs/a0d7b954_appdaemon/apps using terminal:
sudo cp -r /config/appdaemon/apps/qolsysgw /addon_configs/a0d7b954_appdaemon/apps
1 Like
I’ll give that a try when i get home thanks
That worked thank you
I’m at a loss here…
Configured fron scratch my mqtt, appdaemon then the qolsys integration in HACS.
Managed to get the new device under mqtt integration with my panel state and all the sensors. But nothing refreshes.
My control4 setting on the panel is still on. Rebooting appdaemon or home assistant does t sync the device. Its stuck with the original status.
Did you figure this out? I have the exact same issue - its showing in the dashboard but I can’t get it to update status (i.e. when I open a door, etc.)
I move the qolsys addon folder (whee I had tried it before) and it suddendly started working… no clue what happened!
I posted this in the HA subreddit but would like to hear from everyone here about it. I think Qolsys is missing a big opportunity by only having the limited Control4 integration. Please post your feedback, preferably on the reddit discussion since this topic is already very long.
See Open API for Qolsys IQ Panel on Reddit
Thanks!
Hey Guys,
I’m trying to figure out how to setup an action to ARM Home/Stay Silent with no announcements and countdowns. It is doable via Alarm.com
What i have is the below.
- service: mqtt.publish
data:
topic: "qolsys/command"
payload: >
{
"event": "ARM_STAY",
"silent_arming": true,
"no_entry_delay": true,
"bypass": false,
"code": "<your_user_code>"
}
But when i look in the mqtt explorder i see this
Transmitted messages:
homeassistant/alarm_control_panel/qolsys_panel/set
1 most recently transmitted message(s)
Transmitted 7:26:47 PM
QoS: 0
Payload: partition_id: '0'
action: ARM_HOME
session_token: c1fe5d8e-c6f0-xxxx-xxx-xxxxx
I am not sure where the session token comes from, which is different than the code from the panel.
The above is also slightly different than what is in the docs
{
"action": "ARM_HOME",
"code": "4242",
"bypass": false,
"delay": 0,
"partition_id": 0,
"session_token": "<session_token>"
}
What would be the correct command to send via MQTT?
Has anyone else experienced an issue recently where when you arm your panel using the Control4 integration it arms at the panel but ADC still thinks your system is disarmed?