Status of development for Intex ECO5220G / QS 500 – Interested in testing

[seebaer1976]

Hi Daniel,
first of all, thank you very much for your excellent work and the very detailed blog posts about reverse-engineering the Intex Krystal Clear saltwater system! The documentation of the bus protocol (SL/CL) is really outstanding.
I own an Intex Krystal Clear QS 500 (model ECO5220G / CG-26668GS) with the mainboard PCB-266 V1.5.
The communication connector on my board is 4-pin (SL / CL / +5V / GND – TEST is a separate pad).
I have already prepared the following hardware:

ESP32 D1 Mini
4-channel bidirectional logic level shifter
4-pin Dupont cable as Y-splitter

The wiring (SL → HV1 → GPIO21, CL → HV2 → GPIO22, +5V → VIN, etc.) is complete and I would love to test the project with ESPHome.
Questions:

What is the current status of development for the ECO5220G / QS 500 model (or PCB-266 board)?
Is there already a working YAML example (e.g. based on pump-controller.yaml) that I could try?
Has development for this device type been discontinued or is it just currently paused?

I am happy to actively test, provide logs, send photos of my board and wiring, or help with debugging. The goal would be a full ESPHome integration with controls (Power, Boost, Sleep, Self-Clean, Timer…) and as many status sensors as possible (Salt Level, Pump Flow, errors, etc.).
Thank you very much in advance for a short update!

Best regards
seebaer1976

[danielschenk]

Hello, thank you for your interest in this project!

The project has been paused for a while due to various other priorities. At this moment, I'm moving. I'm still interested in making this work, but it will depend on whether I will still use the pool at the new house.

My goal for a minimum viable product is at least remote power toggling. For now, the idea is to automatically set the built-in timer to infinite, so at least you don't get unexpected power-offs (this should currently already work for the pump unit). Later I want to be able to communicate all the statuses and errors to HA, and eventually also add the ability to do something with the timer. Responsibility of controlling running time of the unit would be at the remote end until that time.

Unfortunately there's nothing concrete you can test with the chlorinator right now. The last status of development was that I was trying to figure out the driver API of the RMT peripheral of the ESP, which seems a good solution to handle the protocol's unusual signalling and timing.

I will update you if I have any news! I'll also do a little readme change so the current status is a little more clear to people who stumble upon this project.