Sorry for the delay, been very tied up with a work project the last few months (still am but had a break to respond).
And I’m not a developer by trade either (I’m an IT Infrastructure guy, mostly IP networking), which is why this is a bit of a kludge, I’ll admit. As mentioned in the release notes, it was thrown together to help a friend with a handful of X10 devices left, and I thought others might find it useful.
Worse yet, the CM11A I was using for testing died…
@g13092, if you’re running HassOS under a VM (which hypervisor are you using?), check to make sure HassOS can see the serial port attached to your CM11A. I know sometimes hypervisors have to be configured to do this.
Under the covers, ‘heyu’ simply attaches to the serial port like it would if you’re running in standalone. It does this by creating a simple x10.conf file with 'TTY '. However, the Docker container (which is what addons are) needs to be able to see the serial port from HassOS / your VM hypervisor.
If you go to Configuration → Addons, Backup, Supervisor, System tab, take a look at the hardware listed on Host and make sure HassOS can see the USB serial adapter.
You can also try using the full HassOS dev name as well. So, instead of ‘/dev/ttyUSB0’, which may change on reboot if you have other serial devices (e.g. Zwave, Zigbee, etc), you can try using the full ‘/dev/serial/by-id/…’ for the serial port in the add-on config. I did test this once and it worked.
Hope this helps…