Consider submitting this integration for inclusion in Home Assistant's core?

[Gamester17]

First, thank you for creating and maintaining this integration. I understand it is very useful for many owners of Mammotion robotic products using Home Assistant.

I was wondering whether you have considered submitting this integration for inclusion in Home Assistant's core by default rather than only having it available only through HACS as a custom component?

• https://github.com/home-assistant/core/tree/dev/homeassistant/components

Home Assistant's developer documentation includes guidance for contributing an integration to its core repository, and it seems that having a native integration could provide benefits such as:

• Easier discovery and installation for users.
• Inclusion in official Home Assistant documentation.
• Improved long-term visibility and maintenance.
• Elimination of the need for HACS as a prerequisite.

I understand that moving an integration into Core requires significant work and could be a relativly huge effort to meet Home Assistant's Integration Quality Scale requirements, testing standards, documentation requirements, and ongoing maintenance commitments.

• https://developers.home-assistant.io/docs/core/integration/contributing_to_core/

I also understand that many HACS-only integrations remain outside Core by choise because of API stability, maintenance burden, or Home Assistant's requirements for core rather than lack of interest.

• https://developers.home-assistant.io/docs/development_submitting/

Bet that many would be interested to hear your thoughts if you think this integration could be a candidate for Core inclusion, or are there technical, API, licensing, maintenance, or other obstacles or blockers that would make this difficult?

Thanks again for all your work on this project!

[mikey0000]

Well ahead of you I already had a draft

[Gamester17]

• Add Mammotion integration home-assistant/core#143429

@mikey0000 Nice! Because all this is now a catch-22 argument or chicken-and-egg dilemma, because the fact is that the Home Assistant's core developers will normally not consider adding new entity domains until there already is enough existing integrations in Home Assistant's core that have a need for it.

So you should really consider first submitting your existing integration as-is (with the vacuum entity domain like is does now) to upstream Home Assistant's core and only if and when that get existed then do we have a stronger argument with the Home Assistant's core developers that there is finally enough integrations in Home Assistant's core that have a need for it.

Thus please keep in mind that he Home Assistant's core developers do not count custom integrations not in the corse as cause to add a pool cleaner entity domain, which will make this a Catch-22 situation if Home Assistant core devs do not add a pool cleaner entity domain until there are more integrations already in the core would benefit from it.

[mikey0000]

No, you cannot do that, you must submit small PRs with one entity type at a time.

[Gamester17]

For reference, bassrock and dddddl has now also submitted pull requests to upstream HA core for Beatbot and WyBot integrations:

• Add Beatbot integration home-assistant/core#177108

• Add WyBot integration home-assistant/core#176363

@mikey0000 FYI, since those are also for pool cleaner robots I believe they are similar to your integration, and just like you said, they each initially only added a single platform (i.e. sensor) to their new integrations for core submission since Home Assistant core development limits that when first adding new integrations, however once merged then you can add support for more platsfoms one platform at a time:

"When adding new integrations, limit included platforms to a single platform. While we appreciate the effort, reviewing larger than necessary PRs slows down the review process. Please reduce this PR to a single platform. See the review process for more details."

• https://developers.home-assistant.io/docs/review-process/#home-assistant-core

Also FYI and for reference, the Open Home Foundation has recently published an AI-policy for all Home Assistant projects to be aware of:

• https://developers.home-assistant.io/blog/2026/07/20/ai-policy/

It basically sais that using AI tools for LLM assisted coding are welcome as an aid, however you should still understand the code yourself and that all communication should be done human to human. In summery it more or less sais that if you are not a developer then you should not just have an AI vibe-code everything and blindly submit that without knowing what you are doing or have an autonomous AI agents answer reply directly. So they are not AI assisted development or AI-coding, but they do not want people who can not even read code to waste their time by having AI autonomously submit pull requests for them without understanding that the code does and how.

• https://developers.home-assistant.io/docs/ai_policy

Btw, with this kind of being a sub-community I am sure that bassrock and dddddl could help provide feedback and suggestions if you maybe ask and they have the time since it is should be in there interest too to have additional integrations for more pool cleaner robots in HA core.