Hi everyone,
I’m integrating a GCE Electronics “X-Pool Connect” pool controller (pH/ORP/water temp/air temp, relay outputs) into Home Assistant via MQTT, and I’m stuck on a device-side bug that I’m hoping someone here has already run into.
Setup: X-Pool Connect, firmware v4.2 (latest available), device ID 0000F7, connected to a local Mosquitto broker (confirmed reachable, other topics work fine).
Symptom: Using GCE’s own official MQTT topic scheme (confirmed against their “API MQTT X-POOL V1.0” doc):
x-pool_0000F7/ana/ph→ publishes correctlyx-pool_0000F7/ana/air→ publishes, but stuck at 0.00 despite the probe being wiredx-pool_0000F7/notif/uporp(ORP threshold alarm) → publishes correctlyx-pool_0000F7/ana/eau(water temperature) andx-pool_0000F7/ana/redox(ORP) → never publish anything, confirmed over several days withmosquitto_sublistening on the fullx-pool_0000F7/#wildcard.
What rules out a wiring/probe problem: switching the device to its WiFi app mode (mode 1) and checking the official “XPOOL-Connect” mobile app shows correct, live values for BOTH the ORP probe and the water temperature probe. So the probes and wiring are fine — this is specifically an MQTT publishing bug for these two channels.
Already tried, no effect:
- Full captive-portal reconfiguration (WiFi + MQTT broker settings from scratch)
- Full firmware reflash (same v4.2 version)
- Double-checked topic names against GCE’s official API doc — they match exactly
I found a thread on GCE’s own forum describing the exact same bug, where a moderator only pointed to opening a HelpDesk ticket — no technical fix posted. I’ve opened a ticket with GCE directly, but wanted to ask here in case someone in the HA community has an X-Pool Connect running and has actually gotten ana/eau/ana/redox working over MQTT — or found a workaround (specific firmware version, a config quirk, anything).
Thanks in advance for any pointers!