Unfortunately I’m not able tpo do that, since I neither own a Q series device nor a LAN C module. Principally, I developed the binding in a way that other connection types besides RS232 could be added pretty straightforward by other developers, as long as the send and receive commands are the same.
However, a quick google search about the Q series brought up that the protocol is completely different compared to the non-Q series, which this binding is about. Therefore I really think that it makes sense / is required to have two separate bindings for both types. It seems that there are already efforts to develop a binding for the Q series: Zehnder ComfoAirQ350 -- do I need ComfoConnect to control it?
With relation to that, I also wonder if this binding should be renamed to something less generic, so that it is clear which kind of devices are supported. WDYT?