FAQ

What is AquaChemD?

AquaChemD is a lightweight Linux daemon for automated pool-water chemistry. It reads pH, ORP, temperature and pressure sensors, controls dosing pumps and publishes state through MQTT, with a built-in web interface.

Does it require the cloud?

No. The project is designed to run locally on Raspberry Pi hardware. MQTT and local web access are used for integration and control.

What sensors are supported?

The project supports Atlas Scientific EZO pH/ORP/temperature interfaces over I2C, DS18B20 temperature sensors, several I2C pressure sensors, generic sysfs sensors and external MQTT values.

How does dosing work?

The documented strategy is a configurable threshold table, optionally using rolling averages. Each dose also has a maximum runtime and each doser can have a maximum total volume over a configured period.

How is dosing made safe?

Dosing is gated by interlock conditions. These can come from MQTT or physical GPIO inputs. A condition can also have a delay before its state is trusted, which is useful after circulation starts.

Can it work with AqualinkD?

Yes. The README specifically describes MQTT integration with AqualinkD, including using pool-equipment states such as filter-pump operation as dosing interlocks.

Can it work with Home Assistant?

Yes. MQTT Discovery is built in, and the project documents chemistry sensors, dose-volume entities, safety conditions and doser controls.

Can it work with Apple Home?

Yes, either through Home Assistant's HomeKit Bridge or through the documented Homebridge AquaDaemon integration.

Where is the complete configuration reference?

The project's README contains the full configuration reference, including system/web, MQTT, dosing, safety interlocks, GPIO, sysfs and sensor settings.

Where should I report problems?

Use the GitHub issue tracker and include relevant debug logging and configuration details where possible.