There is an undocumented interface into my alarm panel, a QolSys IQ2+. I can access it by running
openssl s_client -host 10.0.0.199 -port 12345
It is a bi-directional interface that periodically reports the state of all alarm sensors and allows the alarm to be armed and disarmed. At the moment, I have to have a node-red flow connect to the alarm panel using a daemon node that runs openssl, then massage and push the data to a mqtt broker (an Aedes node in Node-Red). then have a HE device connect to the broker.
It works but it's really cumbersome and adds several failure points to the whole thing. Would be so much simpler and self-contained if I could just open the connection to the alarm panel directly in HE,
Seems to me that you already have the whole ssl/tls thing implemented as we can open https and wss connections in HE. Wouldn't an encrypted raw socket mostly be a subset of already existing functionality? In my case, the ability to ignore cert errors is a must, as the cert in the alarm panel is self-signed. But you already have that option in https and wss as well.
I intend to publish my driver sooner or later, but the whole openssl/node-red thing complicates it.