search

py-smart-gardena / hass-gardena-smart-system

Home Assistant custom component integration for Gardena Smart System
Apache License 2.0
205 stars 52 forks source link

Full set of mower commands #2

Open osks opened 4 years ago

osks commented 4 years ago

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:

  1. START_SECONDS_TO_OVERRIDE = vacuum.start
  2. PARK_UNTIL_NEXT_TASK = vacuum.return_to_base
  3. PARK_UNTIL_FURTHER_NOTICE = vacuum.stop

The idea is that the best mapping would be this:

  1. START_SECONDS_TO_OVERRIDE = vacuum.start
  2. START_DONT_OVERRIDE = vacuum.turn_on
  3. PARK_UNTIL_NEXT_TASK = vacuum.return_to_base
  4. PARK_UNTIL_FURTHER_NOTICE = vacuum.stop and vacuum.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.

grm commented 4 years ago

I sent a mail to gardena devs to have more insight whit these commands.

meuja commented 1 month ago

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.