I’m not sure then. I would try restarting the broker add-on and then restarting the AppDaemon add-on. You could also check the MQTT add-on logs to see what it’s showing when AppDaemon tries connecting.
I have decided to re-install the OS, and start from scratch. I will update you tomorrow.
started with a fresh OS. Now, AppDaemon will not start. Error loading /config/secrets.yaml. I believe this file is formatted correct. I see that I have a 2nd secrets.yaml file located at /homeassistant/secrets.yaml. which one is correct, and it there an issue having both?
Set that first line in your MQTT config and use that file.
AppDaemon is started, QolsysGateway shows up in the UI. Log file has connection errors…
after a bit, log file will contain this errors
What is your network setup? See some posts about having dual connectivity (Ethernet and WiFi) causing issues.
Home Assistant green is ethernet, Qolsys is wireless.
Both Appdaemon and Mosquito broker are on the Home Assistant, so all communication should be internal, right?
I feel that most of my issues are related to the installation location of Appdaemon, my ability (or lack of) to mover proper folder structures, and correctly identify app_dir: and secrets: in appdaemon.yaml.
There’s no issue with the panel being on WiFi. The dual connectivity problem would be having the HAOS installation on both Ethernet and WiFi.
The communication is internal but it’s not as simple as AppDaemon talking directly to MQTT. They go through a virtualized switch that is tied back to the physical network interface.
The folder move is because of HACS installing the Qolsys app in an old location used by AppDaemon. That was a change on the AppDaemon side some time back.
Can you post your current AppDaemon.yaml?
Qolsys is now communicating with Home Assistant - YAY and thanks.
Will the sensors only show as entities in HA? is there a way add them as a device?
can you reccomend any articles/examples that I should become familiar with? Do you have any reccomendations on using MQTT triggers or Entity events?
There’s an integration called “Device Tools” available in HACS that lets you create your own devices from the entities but I don’t believe there’s any real benefit to it. Here’s a sample automation I have for locking the exterior doors when the alarm is set:
alias: Locks with Alarm Arm
description: ""
trigger:
- platform: state
entity_id:
- alarm_control_panel.house
to: armed_home
- platform: state
entity_id:
- alarm_control_panel.house
to: armed_away
condition: []
action:
- data: {}
target:
entity_id:
- lock.back_door_lock
- lock.front_door_lock_frontdoor
- lock.garage_side_lock
action: lock.lock
mode: single
I have a total of 39 sensors in Qolsys, that sync’d over to HA. I was cleaning up the naming within Qolsys, and now 3-4 entities in HA are not seeing events. What is the easiest way to have Qolsys re-sync all sensors in HA?
After making sure the panel is seeing the sensors, I usually just restart AppDaemon.
Restarting AppDaemon or HA is not working for me. I think the issue started when I was trying to rename these 3 entities. now there is some disconnected between Qolsys and HA. I have since deleted these sensors from Qolsys, and the entities still will not go away.
I also installed Home Assistant Registry, and tried to purge these, but they are still there.
Edit: I meant to say restarting is not working for me
@FriedCheese - Thanks for all your help over last several days. I did find a resolution to the sensors not synching. I ended up having to clear out the MQTT.
Hello all, I was able to setup mqtt and all that worked great… now I can’t see the dashboard in appdaemon… I only see hello.dash … do I have to create a dashboard of my own or do is there a template I can follow? TIA.
You’ll want to make sure the Qolsys folder is in the correct location.
not sure why none of my door sensors are picking up. Should it do it automactically once i enable control4?
anything wrong here?
Is your panel being added? What do the AppDaemon logs show?
