@lweberru Hope it is OK with me posting here, your repo does not have a discussion section so posting this here as an issue even though the topic is not relatedto any problems with your library, component or integration.
For your info, I have created this semi-related feature request for a pool_cleaner entity domain to be added to Home Assistant's core (and frontend):
Wondering what you or 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? Feedback is welcomed even though not exactly asking for a general pool controller entity there.
Asking for input since would like to know what are the need to have states for a minimal viable implementation for a new pool cleaner entity domain if would base it on the existing vacuum entiry for reference. This research could pontentially also be reused if you or someone else would someday like to take a stab at geeting a dedicated water treatment system or dosing system entity domains added for use with your pool controller integration.
You might even want to consider submitting a similar feature request for new pool_controller, water_quality, water_teatment, water_chemicals, or dosing_system entity domains water quality monitoring, water chemicals, and chemical dispenser system or chemical dosing system entiry domain to be added too.
They key point is that new entity domains and new device classes are needed for Home Assistant's "purpose-specific triggers and conditions" to be context-aware so can have purpose-specific triggers and conditions for example pool cleaners, spa and pool controllers, water treatment systems, and dosing systems.
Also, is there any chance someone from you userbase would be interested in submitting a this or similar 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:
Hoping that you still do not mind posting your comments/feedback upstream in that feature request for Home Assistant there anyway:
Looking for pools owners with pool cleaner robots to provide feedback or ideas from other pool owner on suggestion to make that feature request better.
@lweberru Hope it is OK with me posting here, your repo does not have a discussion section so posting this here as an issue even though the topic is not relatedto any problems with your library, component or integration.
For your info, I have created this semi-related feature request for a
pool_cleanerentity domain to be added to Home Assistant's core (and frontend):Wondering what you or 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? Feedback is welcomed even though not exactly asking for a general pool controller entity there.
Asking for input since would like to know what are the need to have states for a minimal viable implementation for a new
pool cleanerentity domain if would base it on the existing vacuum entiry for reference. This research could pontentially also be reused if you or someone else would someday like to take a stab at geeting a dedicated water treatment system or dosing system entity domains added for use with your pool controller integration.You might even want to consider submitting a similar feature request for new
pool_controller,water_quality,water_teatment,water_chemicals, ordosing_systementity domains water quality monitoring, water chemicals, and chemical dispenser system or chemical dosing system entiry domain to be added too.They key point is that new entity domains and new device classes are needed for Home Assistant's "purpose-specific triggers and conditions" to be context-aware so can have purpose-specific triggers and conditions for example pool cleaners, spa and pool controllers, water treatment systems, and dosing systems.
Also, is there any chance someone from you userbase would be interested in submitting a this or similar 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:
Hoping that you still do not mind posting your comments/feedback upstream in that feature request for Home Assistant there anyway:
Looking for pools owners with pool cleaner robots to provide feedback or ideas from other pool owner on suggestion to make that feature request better.