I am not sure what you mean here, I think the translation makes it more difficult Do you mean you HAVE found a pinout schema for a COMM port, or just that it would be easier IF we found a pinout for a COMM port?
I haven’t seen any evidence that these controllers have an RS-232 interface (assuming that this is what you mean by COMM port - a serial connection like you find on a PC) and it wouldn’t make much sense for them to have one since RS-232 is only much good for point-to-point computer comms, not multi-device control networks.
I believe that the connectors on the gecko gear that are labelled “CO” are RS-485 interfaces, based on what I could find in the patent docs. They might also include i2c.
That’s where I’m working from, everything else is just speculation - until we can physically interface with the unit we won’t know what features are available on which busses/connectors, but exporting whatever we can is obviously the next step after that.
What I’m targeting is hopefully getting an ESP8266 to talk to the controller (probably via RS485), and then either HA api or MQTT to (and from) my home network.
The in.touch connects to the purple “CO” port (as you can see in these product images), so that’s where I expect we’ll find an RS485 port. This same connector also appears to be what’s used by the in.stik for loading firmware (based on the in.xm2 techbook), so I wouldn’t be surprised to see i2c on that connector too (or it could be almost anything for all we know). The purple “CO” port is also what’s used to link two spa packs together, and is used by the in.terface AV thingy, so it does look like that port is the way to get access to most of what’s going on in the system. Hopefully.