SEKO PoolDose
The PoolDose integration connects a SEKO
This integration uses an undocumented local HTTP API. It provides live readings for pool sensors such as temperature, pH, ORP/Redox, as well as configuration parameters.
Prerequisites
- Install and set up the PoolDose device according to its user manual.
- In particular, connect the device to your Wi-Fi network.
- Identify the IP address or hostname of the device.
- Browse to the IP address or hostname. Use HTTP and port 80.
- Log in to the web interface.
- Verify that sensor data is displayed, such as water temperature or pH values shown as gauges.
- Deactivate the device password, i.e., set it to 0000.
- Optional: Block the device’s internet access to guarantee fully local operation and prevent potentially breaking firmware updates.
Configuration
To add the SEKO PoolDose integration to your Home Assistant instance, use this My button:
SEKO PoolDose can be auto-discovered by Home Assistant. If an instance was found, it will be shown as Discovered. You can then set it up right away.
Manual configuration steps
If it wasn’t discovered automatically, don’t worry! You can set up a manual integration entry:
-
Browse to your Home Assistant instance.
-
In the bottom right corner, select the
Add Integration button. -
From the list, select SEKO PoolDose.
-
Follow the instructions on screen to complete the setup.
Removing the integration
This integration follows standard integration removal. No extra steps are required.
To remove an integration instance from Home Assistant
- Go to Settings > Devices & services and select the integration card.
- From the list of devices, select the integration instance you want to remove.
- Next to the entry, select the three dots
menu. Then, select Delete.
Data updates
This integration pollsData polling is the process of querying a device or service at regular intervals to check for updates or retrieve data. By defining a custom polling interval, you can control how frequently your system checks for new data, which can help optimize performance and reduce unnecessary network traffic. [Learn more] data from the device every 10 minutes (600 seconds) by default. This polling interval is configured to balance data freshness with device stability:
- The device does not support frequent requests and may become unstable with shorter intervals
- Physical water treatment values typically change slowly and do not require frequent monitoring
- This interval provides adequate monitoring for pool water management while maintaining device reliability
Supported devices
The following devices are known to be supported by the integration:
- SEKO PoolDose Dual/Double (API v1)
Supported functionality
Sensor entities
Identifier | Unit | Description | States |
---|---|---|---|
temperature | °C/°F | water temperature | — |
ph | — | pH value | — |
orp | mV | Current ORP (Redox) value | — |
ph_type_dosing | — | Type of pH dosing being used | pH+, pH- |
peristaltic_ph_dosing | — | pH peristaltic dosing mode | Off, Proportional, On/Off, Timed |
ofa_ph_value | min | Time threshold for pH overfeed alerts | — |
orp_type_dosing | — | Type of ORP dosing being used | Low, High |
peristaltic_orp_dosing | — | ORP peristaltic dosing mode | Off, Proportional, On/Off, Timed |
ofa_orp_value | min | Time threshold for ORP overfeed alerts | — |
ph_calibration_type | — | Type of pH calibration being used | Off, Reference, 1 point, 2 points |
ph_calibration_offset | mV | pH calibration offset value | — |
ph_calibration_slope | mV | pH calibration slope value | — |
orp_calibration_type | — | Type of ORP calibration being used | Off, Reference, 1 point |
orp_calibration_offset | mV | ORP calibration offset value | — |
orp_calibration_slope | mV | ORP calibration slope value | — |
Known limitations
Hardware and connectivity issues
The PoolDose devices have two characteristics that can affect their network connectivity:
-
Hardware limitations: The devices use a small-scale controller that is heavily loaded by web server and data processing tasks. This can occasionally cause brief connection interruptions, though devices typically recover quickly.
-
Energy-saving mode: When the pump monitoring feature is activated in the device settings, the device often enters an energy-saving mode if no pump operation is detected. During this time, the device may be less responsive or temporarily unavailable on the network, for example, at night.
Cached data behavior
These limitations are normal behavior for the device and not issues with the integration itself. To handle these connectivity issues, the integration caches values for a maximum of 300 seconds (5 minutes) when the device is temporarily unresponsive. After this cache period expires, entities will show as “unavailable” until the device provides new data again.
Troubleshooting
Device not found
Symptom: “Device could not be found on the network”
When trying to set up the integration, you receive an error that the device cannot be found.
Description
The device may not be properly connected to your network, or it may be using a different IP address or hostname than expected.
Resolution
To resolve this issue, try the following steps:
- Check that your device is powered on and connected to your Wi-Fi network.
- Look for a device called “kommspot” in your router’s device list or DHCP client table.
- Use the IP address shown for “kommspot” in the integration setup.
- Ensure the device and Home Assistant are on the same network segment.
Connection refused
Symptom: “Connection refused” or authentication errors
The integration cannot connect to the device even though it’s found on the network.
Description
This typically occurs when the device’s web interface password is not set to the default value (0000) or not properly deactivated.
Resolution
To resolve this issue:
- Browse to the device’s IP address using a web browser.
- Log in to the web interface.
- Set the password to the default value (0000) or deactivate password protection.
- Try setting up the integration again.
Unstable connection
Symptom: Entities frequently become unavailable
Sensor entities show as “unavailable” intermittently, especially during certain times of day.
Description
This is normal behavior for the PoolDose device. When the circulation pump is not running, the device enters a kind of sleep mode and becomes less responsive to network requests.
Resolution
This behavior is expected and does not indicate a problem with the integration:
- The integration uses cached values when the device is temporarily unresponsive.
- Entities will return to normal once the device becomes responsive again.
- Consider this behavior when creating automations that depend on these sensors.
Missing peristaltic pump status
Symptom: No peristaltic pump status data is available
Peristaltic pump status sensors don’t show any data or appear as unavailable.
Description
The PoolDose device only propagates the status of peristaltic dosing pumps when the external relays for these pumps are enabled in the device settings.
Resolution
To get peristaltic pump status data:
- Browse to your PoolDose device’s settings.
- Find the external relay configuration for the pH and ORP pumps.
- Enable the external relays for the pumps you want to monitor.
- Save the settings and restart the device if required.