11/30/2023 0 Comments Spa plug![]() 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. 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. 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. 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. 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 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? Is really more easy to use in.touch2 and just network sniffer to capture packet. Sorry i not have time for this except maybe if someone can found pinout shema of COMM port cuz i will not guest on wire and broke my IN.XE controler Why i think is a good way to work on COMM port and not really on RS485 internal port. But sadly i cant use in.mix menu to chose my colorįake module on “gecko network” can have many avantage to make some DIY component The relays can drive my WLED button (short press, long press) i use this for control color and animation on my WLED. I can use normal light button on my spa pluged on relay. Exemple my gecko spa have WLED firmware on esp82266 and all led is programmable. Menu fonction will switch on Keyboard like in.k1000Įach “fake” fonction will can be use on HASSIO. If someone can do this he will able to simulate in.touch / in.mix / all device on the “gecko network”. Plug existing module and capture GET/POST for all function. Use same communication on the network to capture all data. ![]() is possible to control spa with this but COMM port have advantage to communicate with all devices in the “gecko network” maybe is RS485 too. Found pinout shema for COMM port and not really RS485 internal port. Sorry i speak english little bit and not have time to analyse this doc. Yes agitting, really good doc to found clue. I’ve ordered some RS485 modules, so when that slow boat arrives I guess it’ll be time to sit down outside with the hot tub, a multimeter and some probes! The techbook for the in.xm2 module notes that the IR receiver pins are present on all but the heater and light connectors, so there’s at least some variation in the wiring, I guess. Our xm2 has connectors for light, “comms”, 2 x keypad, IO and heater comms. The low-voltage stuff all uses an 8-pin connector, but each type is keyed differently - I don’t know how much the pinouts differ or if the keying is mainly for feature restriction. ![]() Note that the in.stik is called “usb key like” not “is a usb key”, and their docs says the stik is programmed at Gecko Alliance factories, so I suspect it’s not a user/dealer-programmable anything, let alone a usb device. I think it’s probably a fairly safe bet to start tinkering with. There’s a techdoc on another (older?) unit that has an internal RS485 connection as well. They specifically mention RS485 in their patent docs where it talks of using RS485 to communicate with external computer and I2C for internal comms. ![]() I’m interested in interfacing directly to the controller as well (not so keen on dropping hundreds of dollars to get a wifi interface that’s still proprietary).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |