Help implement a new pool cleaner entity domain in upstream Home Assistant?

[Gamester17]

@sh00t2kill @elad-bar I submitted this feature request for a pool_cleaner entity domain to be added to Home Assistant's core:

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

Wondering what you think about that idea and if you could help research and list the requirements for your integration?

What are the need to have states for a minimal viable implementation if would look at 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.

[elad-bar]

Thanks for raising this.

I do think a dedicated pool_cleaner domain has a place in Home Assistant. Pool cleaners are not really vacuums, and some concepts do not map perfectly today. For example, in this integration fan_speed is actually the cleaning mode, and return_to_base is closer to Dolphin pickup mode than to a vacuum returning to a dock.

That said, I am not sure I would invest all my effort in driving this direction myself right now. The pool-cleaner space is still quite fragmented, and every brand seems to expose a different set of capabilities: cleaning modes, pickup/docking behavior, scheduling, filter status, manual control, battery, water temperature, and so on. Because of that, the current vacuum entity, while not perfect, still works as a fairly generic abstraction for the basic actions: start, pause, return/pickup, state, and mode-like behavior.

So my feeling is that a new domain would be valuable only if it defines a clear shared contract beyond naming differences. If the main difference is just renaming fan_speed to cleaning_mode and return_to_base to pickup, then improving or generalizing the existing vacuum model might be just as useful.

If Home Assistant does introduce and approve a pool_cleaner domain, I would be happy to adapt this integration to use it. I just do not think I can commit to leading the full architecture proposal and implementation effort at this stage.

[Gamester17]

@elad-bar @sh00t2kill Would you mind cross-posting your comments/feedback in upstream feature request for Home Assistant? -> https://github.com/orgs/home-assistant/discussions/3662

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

[Gamester17]

For your information, I have updated the upstream feature request discussion and drafted outline of architecture proposal:

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

Again, would be great if you can post feedback/input comments there in upstream feature request to show your support.

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 can also up-vote the feature request there too.