I know little about the C1M1. The Elk integration requires a TCP internet connection between HA and the Elk. If that’s possible with the C1M1 then it should work.
Reading the tech note it does sound promising. There is mention of strong encryption. That may cause problems. It’s unclear without more detail. The integration does support TLS which is storing.
If you find any other tech notes I’ll take a look at them.
I do have a C1M1 connected to home assistant as well as another M1 connected via the M1XEP and I don’t see any issues. My personal preference would’ve been to do the M1XEP, the site that has the XEP originally had C1M1 and it failed, replacing it was far less expensive using the XEP and separate communicator, also my alarm company prefers this method because if the C1M1 fails the cellular communicator will still work and vice versa.
Thought no additional power cords on the C1M1 makes the installation a lot cleaner.
Just wanted to follow-up. Adding the ElkM1 with a C1M1 to HA has worked really well through this integration. I just need to get it to arm without having to input a usercode on my HA dashboard.
Based on what I’m reading, HA seems to import Elk M1 outputs only if they are named. So I see no representation for outputs 205, 206, and 207 that were used to setup our Elk system. Further, a lot of old web hits seem to suggest manually adding these by editing config.yaml, but that whole concept seems to be outdated now and it’s unclear what replaced it.
Question is, how I do add unnamed outputs 205-207 to HA so that I can display their state and switch them on and off? I am assuming I need to manually edit something…
Note that ElkRP2 configuration software seems not to allow renaming any outputs above 32, so just renaming them on the Elk side is not an option.