Custom Home Assistant integration for Vigipool controllers already publishing their state on a local MQTT broker.
This project currently targets a controller visible under the MQTT prefix:
tild_30C9229A50C4
0.4.0 is the current release and adds a cleaner compact filtration schedule editor.
Included today:
- UI setup through a Home Assistant
config flow - native subscription through Home Assistant's built-in
mqttintegration - automatic tracking of
.../reportedtopics under a configurable device prefix - main sensors for temperature, setpoint and diagnostics
- a decoded filtration schedule sensor with readable slot attributes
- binary sensors for flow, light, auxiliary relay, cover and connectivity
- a filtration switch using the Vigipool command topic
- a pool light entity using the Vigipool command topic
- filtration program switches for programs 1 and 2
- thermoregulated mode switches for both filtration programs
- compact editable
daystext fields for both programs - compact editable
slotstext fields for both programs - readable schedule summary sensors for both programs
- one raw diagnostic entity exposing every MQTT topic received for the device
Not included yet:
- auxiliary relay control
- full
pH / Redoxsupport
- pool temperature
- temperature setpoint
- filtration state codes
- pool light state and related parameters
- auxiliary relay state and configuration
- winter / frost-free related flags
- simple connectivity and error diagnostics
- raw filtration, light and auxiliary schedules
- Home Assistant with the native
mqttintegration already configured - access to the local Vigipool MQTT topics
- Open
HACS > Integrations > Custom repositories. - Add
https://github.com/greenlynxe/ha_vigipoolas anIntegration. - Install
Vigipool. - Restart Home Assistant.
- Go to
Settings > Devices & services > Add integration. - Search for
Vigipool.
- Copy
custom_components/vigipoolinto your Home Assistantcustom_componentsfolder. - Restart Home Assistant.
- Add the integration from
Settings > Devices & services.
The config flow asks for:
Device nameMQTT topic prefix
Example:
tild_30C9229A50C4
The integration then subscribes to:
<topic_prefix>/#
Pool temperatureTemperature setpointFilter state codeError codeState bitmaskWi-Fi RSSIModel IDHardware versionSoftware versionAction codeFilter service intervalLight typeLight codeLight brightnessLight speedAux typeAux configAux minimum temperatureAux temperature hysteresisFrost free modeBackwash codeFilter schedule rawFilter scheduleProgram 1 scheduleProgram 2 scheduleLight schedule rawAux schedule rawSerial number rawDevice IDRaw MQTT topics
Flow onCover onAux stateLight stateMQTT connectedServer onWinter mode
FiltrationswitchPool lightlight entityProgram 1 enabled/Program 2 enabledswitches- thermoregulated switches for both programs
Program 1 days/Program 2 daystext entitiesProgram 1 slots/Program 2 slotstext entities
The controller appears to publish topics with a shape close to:
<device_prefix>/<type>_<direction>/<feature>/<channel>/reported
Useful examples already observed:
u16_r/value_temp/value/reportedu16_w/consigne_temp/consigne/reportedu16_w/filt_state/info/reporteds128_w/filt_sched/info/reportedu8_w/light_state/info/reporteds44_w/light_sched/info/reportedu8_r/aux_state/info/reporteds44_w/aux_sched/info/reportedu32_r/error/info/reported
The first writable topics now used by the integration are:
u16_w/filt_state/info/desiredu8_w/light_state/info/desired
Observed filtration values on the reference controller:
1for forced filtration on0for filtration off
- auxiliary relay control is not enabled yet
- light and auxiliary schedules are still exposed as raw strings
- no full support for the separate chemistry module
- confirm auxiliary writable MQTT topics
- add auxiliary relay control
- add write support for light and auxiliary schedules
The Home Assistant integration lives in custom_components/vigipool.