no I created a new code so that I would know whenever it was deactivated by Home Assistant.
you didn’t have any spaces before or after your code in the yaml did you? Sorry just grasping at straws right now!
Sorry for the late response. Yes I had one space but I thought that was required. So it says “panel_user_code:” then one space then my code.
But if I do it with no space there it gives me an error. With one space there there is no error. It just doesn’t do anything.
@bumpyj38 No that seems correct. I’m not sure what it could be at this point. Have you tried changing the log levels?
What do you mean changing the log levels? I have not done this.
Hello All, As we are all usign the addon, I have a question. Do you know if other type of sensors is avialble with this integration. Garage Door, Door Lock, etc…?
Thank you in advance
T
Hi,
I just found this integration and I’ve been struggling to get it to work. I think I have HACS, appdaemon and the qolsysgw installed and configured correctly.
My problem seems to be that I cannot ping my Qolsys Panel 4. I’ve turned on the 6 digit pin, turn on the Control4, the panel reboots and I cannot remotely ping the device. I’ve assigned a static IP to the device, so I know exactly what the IP is.
I see above someone mention that regenerating the token to help, but for the life of me nothing works.
Any one experiencing something similiar?
1 Like
I think this is what saved me. I moved the qolsysgw folder and it finally worked. I didn’t do a link like yourself, but instead just copied it into the Appdaemon app’s folder.
1 Like
Weird that they suggest installing through HACS but it puts the folder in the wrong place. Hope the author will update the documentation.
2 Likes
thank you! was literally looking for this…
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.