Help with the implemention a new pool cleaner entity domain in upstream Home Assistant?

[Gamester17]

@lmaertin @ronaldvdmeer I submitted this feature request for a pool_cleaner entity domain to add to Home Assistant's core:

• https://github.com/orgs/home-assistant/discussions/3662

Wondering what you think about that idea and if you are interesting in helping research or list requirements for your integration?

What are the need to have states for a minimal viable implementation if would base it on the existing vacuum entiry for reference?

Also, is there any chance you would be interested in submitting a such architectural proposal and impementing it if approved?

If not then consider posting your feedback and inputs there as comments on what would be needed or could be a improved ideas.

Will also post same suggestion to the developers of some other pool cleaner integrations as well so hopefully will not be alone.

[lmaertin]

Hi @Gamester17, I support you idea for pool robots, but I would not go to have one class for dosing systems. Even after reading you proposal in the discussion, I see no direct relation here due to such dosing devices belong more to the recirculation systems of a pool/spa than to active/moving robots.

[lmaertin]

@ronaldvdmeer please share position in this as well. I would close the issue when you agree as well.

[ronaldvdmeer]

I support the idea of a dedicated entity domain for autonomous pool cleaning robots, especially where the current vacuum abstraction becomes limiting.

However, I would strongly separate those devices from pool dosing and water treatment systems such as Seko PoolDose integrations.

A dosing controller is architecturally much closer to a water treatment / recirculation system than to an autonomous cleaner. Its primary responsibility is regulating water chemistry (pH, ORP, chlorine dosing, flow monitoring), not performing cleaning jobs or navigation tasks.

Combining robotic pool cleaners and chemical dosing systems into a single domain would likely create an overly broad abstraction with mismatched states, services and UI expectations.

For PoolDose specifically, the current approach using dedicated sensor, switch, select and number entities feels much more semantically correct.

[Gamester17]

OK I hear what you guys are saying, so I have now rewritten the upstream feature request to removed chemical dispenser systems:

• https://github.com/orgs/home-assistant/discussions/3662

Would you still mind cross-posting your comments/feedback upstream in that feature request for Home Assistant there anyway?

• https://github.com/orgs/home-assistant/discussions/3662

Note that while I completly removing the mentioning of dosing I partially keep mentioning of sensors of chemical levels since think some "pool cleaner" devices and dosing systems can have a wide array of sensors and those could include sensors for chemical levels too.

Looking for people to provide feedback or ideas from other pool ownwer on how to make that feature request better.

Please also post any missing states, attributes, and services/actions there as well so that we try to collect them all in a single place.

You might also want to consider submitting a similar feature request for a chemical dispenser system or chemical dosing system entiry domain to be added too.