Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Home Assistant is getting Lawn Mover support #183

Open
olalid opened this issue Sep 4, 2023 · 8 comments
Open

Home Assistant is getting Lawn Mover support #183

olalid opened this issue Sep 4, 2023 · 8 comments

Comments

@olalid
Copy link

olalid commented Sep 4, 2023

Since Home Assistant 2023.9 will get Lawn Mover support, this integration should change to using that instead of vacuum.
https://rc.home-assistant.io/integrations/lawn_mower/

@smoki3
Copy link

smoki3 commented Oct 4, 2023

also looking forward to this. But as far I understand, lawn mower are actually only supported by mqtt

@Robbe-B
Copy link

Robbe-B commented Oct 5, 2023

also looking forward to this. But as far I understand, lawn mower are actually only supported by mqtt

I believe the MQTT integration is the only integration to make use of the new Lawn Mower entity.
But every integration can use that new type of entity.

However it has a lot less to offer compared to the vacuum entity at this point.

Vacuum entity: Mower entity:
image image

@Jogge
Copy link
Contributor

Jogge commented Oct 11, 2023

@Robbe-B What more do you need than these three services?

start_moving => Start mowing
pause => Park until further notice
dock => Park and start again with next schedule

@Robbe-B
Copy link

Robbe-B commented Oct 11, 2023

@Jogge,
For me personally nothing more.
I'm just making the comment that changing the entity type will make you loose functionality (like e.g. the STOP command).
Which is currently provided separately from the dock command:
image

@smoki3
Copy link

smoki3 commented Oct 17, 2023

What is actually the difference between stop and pause?

@Jogge
Copy link
Contributor

Jogge commented Oct 25, 2023

What is actually the difference between stop and pause?

Stop (■) parks the mower until further notice, meaning you will have to manually start the mower again:

def stop(self, **kwargs):
"""Stop the mower using Gardena API command PARK_UNTIL_FURTHER_NOTICE."""
_LOGGER.debug("Mower command: vacuum.stop => PARK_UNTIL_FURTHER_NOTICE")
asyncio.run_coroutine_threadsafe(
self._device.park_until_further_notice(), self.hass.loop
).result()

There is no pause, but the return to base (⌂) parks the mower until next task:

def return_to_base(self, **kwargs):
"""Stop the mower using Gardena API command PARK_UNTIL_NEXT_TASK."""
_LOGGER.debug("Mower command: vacuum.return_to_base => PARK_UNTIL_NEXT_TASK")
asyncio.run_coroutine_threadsafe(
self._device.park_until_next_task(), self.hass.loop
).result()

@tompi69
Copy link

tompi69 commented Feb 27, 2024

It's possible you support both? What do I mean is that the lawn mower is displayed on the surface, but the functions of the vacuum cleaner can be used in the background? Actually, the only thing that bothers you is the view and user interface.

@grm
Copy link
Contributor

grm commented Sep 2, 2024

👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants