Open osks opened 4 years ago
I sent a mail to gardena devs to have more insight whit these commands.
Does this integration will move from vaccum to LawnMoverEntity? As it seems to be merged to Core HA https://github.com/home-assistant/architecture/discussions/894#discussioncomment-6520473 It could help supporting START_DONT_OVERRIDE feature. Or maybe the basic send vacuum command could be a workaround, but I have no idea what command to send.
This is an issue from the old repository (osks/hass-gardena-smart-system#10).
The status now is that the mapping between mower and vacuum commands is like this:
If in the end we would have to live with only 3 services, I would recommend the following mapping - which would provide the most important functions for automations:
START_SECONDS_TO_OVERRIDE
=vacuum.start
PARK_UNTIL_NEXT_TASK
=vacuum.return_to_base
PARK_UNTIL_FURTHER_NOTICE
=vacuum.stop
The idea is that the best mapping would be this:
START_SECONDS_TO_OVERRIDE
=vacuum.start
START_DONT_OVERRIDE
=vacuum.turn_on
PARK_UNTIL_NEXT_TASK
=vacuum.return_to_base
PARK_UNTIL_FURTHER_NOTICE
=vacuum.stop
andvacuum.turn_off
But it seems that vacuum.turn_on and vacuum.turn_off doesn't work as expected.
TODO: Check if there is a way to make vacuum.turn_on and vacuum.turn_off trigger the corresponding methods in vacuum.py. If yes: Implement 4 command version. If no: Stay with current version and close this issue.