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

[Gamester17]

Mammotion are now also making the Mammotion SPINO E1 pool cleaning robot so think that this idea is relevant for this project too.

For your info, I submitted this feature request for a pool_cleaner entity domain to be added to Home Assistant's core (and frontend):

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

Wondering what your users and community who presumably are also pool owners think about that idea and if you all are interesting in helping research or list requirements for such a new entity domain?

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 someone from you userbase would be interested in submitting a such architectural proposal and actually 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.

Note that after initial feedback from others I have rewritten the upstream feature request to removed the idea of also adding chemical dispenser systems or chemical dosing systems to the same entiry domain:

Hopeing that you still do not mind posting your comments/feedback upstream in that feature request for Home Assistant there anyway:

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

Looking for cuurent and future pools owners with pool cleaner robots to provide feedback or ideas on suggestion to make that feature request better.

[mikey0000]

The integration can support spino, just I don't have one yet

[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.

[mikey0000]

Did you write it up in the architecture discussions?

[Gamester17]

Did you write it up in the architecture discussions?

@mikey0000 No I only made an outline (i.e. a draft) with the help of AI and posted that as a reply to that discussion thread, so if someone else want to run with it that can copy that outline and use it as base to edit as they choose -> https://github.com/orgs/home-assistant/discussions/3662#discussioncomment-16839426

The guideline for posting architecture proposals under discussions to the architecture repository sais that if you raise an architectural proposal, there then your intention should be to also implement the proposal yourself when accepted (which I am not intending), and it then sais that iIn case you are not able to implement your proposal (for whatever reason) you should instead post a feature request on the Home Assistant Discussions space:

• What is the architecture repository for? Please read this topic, before posting anything. Thanks! home-assistant/architecture#494

Hence I only posted the idea to the feature request section to raaise awareness in the hope that someone else will take on the task and run with it.

[mikey0000]

I would if I had time, unfortunately I lack time right now

[Gamester17]

@mikey0000 I understand. Would approciate it though if you posted a comment that expesses your support for the idea and any feedback or input you might have there in the upstream feature request discussion -> https://github.com/orgs/home-assistant/discussions/3662

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.