Karl Anders Øygard

As far as I can tell, the Eaton xComfort Bridge is a completely different device from those supported by this code.

I can try building on Windows in order to figure this out, but in the meanwhile, try using the '--hidapi' parameter and see if that works? I have seen issues...

I tried building the code on Windows, but was lead down a rabbit hole of broken links and not very helpful guides via https://github.com/google/gousb and https://github.com/libusb/libusb/wiki and gave up after...

Device 188a:1102 is the xComfort CKOZ-00/13, which is only used when configuring the xComfort network. xcomfortd-go supports the xComfort CKOZ-00/14 device, which needs to be added to the network with...

188a:1101 is the CKOZ-00/14. That's the device this code supports.

Whoops, I've not tested the shorthand flags in a while. I pushed a fix for that now, just pull again and it'll be fixed.

Can you do sudo ./xcomfortd-go --hidapi --verbose and send me the logs? Really curious what it's sending, it looks very strange. When I've seen this in the past, it's been...

Don't know why the chose the numbering scheme like this, but 2.60 dates back to 2012. "2.11, 2.05" is from 2016. Upgrade to that and you should be good to...

Ah, that makes a lot more sense. I'll take a look and see if I can add some support for the 00/03 as well, it may need some minor tweaks...

I've made some accommodations to the USB code, please give to code a spin and see if it works better with the CKOZ-00/03 now. I suspect the CKOZ-00/03 is missing...