Comfort 2 Alarm working with Home Assistant!

[wexfordman]

Ahh, perfect, that makes sense and appears to be working, very much appreciated.

How do I ensure that this starts up automatically now if my pi/ha restarts ?

[caravanboy]

Well... that\'s another question. You\'d have to understand which flavour of Linux your HASSOS is based on to determine the right method of auto-starting processes. I used to know how to do this on UNIX variants a few years back (e.g. rc2.d folders etc) but it has all moved on a lot.

You could read some of the HA guidance here (which is aimed at helping you auto-start HA, but the principles would be similar). That said, as I mentioned above, an upgrade to HASSOS would possibly/probably lose that config.

Alternatively, I just spotted this add-on which may be more suited to achieving what you want?  Startup.d Addon

Hope this helps!

[wexfordman]

Again, thanks a million for thus, makes sense again and I will do a bit if research.

In your opinion, what\'s the best deployment to use for HASS, bearing in mind my limited knowledge of Linux, and dockers etc. Do you think it would make sense for me to try a different configuration rather than hassos ?

[caravanboy]

I think with limited knowledge HASSOS is probably the best choice - in theory it handles everything and is as almost as close to a turnkey solution as you can get for the basic Home Assistant (unless you buy one of their dedicated \'Blue\' boxes).

I\'ve got intermediate knowledge and I still use HASSOS. My NAS supports Virtual Machines so it was easy for me to just create a raw VM on there from a HASSOS image. Also likely much more easy to get community support for running HASSOS on a Pi too.

[caravanboy]

I\'m really confused now. This is the second notification I\'ve had on this thread today. The first time I logged in there didn\'t seem to be any new messages and now just a \"thankyou\" for something not obvious? 
Although I see Skirtstrider also only made 1 post and also joined today (like the previous poster who caused my notification). Hmm...

[slychiu]

Sorry its another spanner. He has been banned

[wexfordman]

Am having to recongure my home assistant, which to me, pretty much means learning all about home assistant again :-(

Wondering if anyone can help me. I have managed to get it up and running and reporting back sensor states, but having issues with the configuration.yaml file which I have stripped back to the bare minimum to get just 1 input working, see below.

What is not working, is the status of the input is appearing as offline/unavaiable.
So I am pretty sure the issue relates to the \"availability topic\", i am definatly missing it or having issues with the syntax, can anyone help with this ?


# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
themes: !include_dir_merge_named themes

# Text-to-speech
tts:
- platform: google_translate

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

mqtt:
binary_sensor:
- name: \"Front Door\"
unique_id: \"front door\"
state_topic: \"comfort2/input1\"
availability:
- topic: \"comfort2/alarm/online\"
payload_available: \"1\"
payload_not_available: \"0\"
payload_on: \"1\"
payload_off: \"0\"

[Ingo]

After seeing this thread I tried to get this going in a Docker using posixx/comfort2mqtt container which seems to be the same as KR\'s python script discussed here.
It actually works out-the-box but I noticed that Inputs were not published until the state changes. Using mqtt explorer I can see all the Outputs and Flags but none of the Inputs until I trigger one to change. I think the same goes for Counters as only my frequently changing Counters are visible. Maybe that is the issue you refer to. Not very helpful if it\'s indeed the case. Would be nice to incorporate the z and Z commands to force an update on startup.

[wexfordman]

Thanks,
I actually think I have it working. The config.yaml format in HA changed recently, I think it was listed as a breaking change, so needed to reconfigure this.
I also found that the available topic had to be correctly defined, which is why the inputs for ecxample were showing as unavailable, but would report a status change if movement was detected.
i will post up my updated yaml files for anyone interested once I get a decent set of sensors etc up and running.
My other issue, is that I am using a HASSOS install, which, if I am thinking correctly, is a docker type install, but without python etc, it is bare bones. So when I went to install the paho client and run the python comfort2.py it was failing. I think I have found away around this by using an addon ssh client which takes me to the docker level outside of hassos, and I can install from there. I know nothing about docker, I may have this completely wrong in my understanding, but it is working now it seems. I just need to do a few final checks to ensure it is auto starting and survivs a hass system update.

[Ingo]

i will post up my updated yaml files for anyone interested once I get a decent set of sensors etc up and running.

Yes, please do. It would be nice to see what you\'ve done.