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

Resume ongoing task after docking #190

Open
sebastian3107 opened this issue Oct 25, 2024 · 16 comments
Open

Resume ongoing task after docking #190

sebastian3107 opened this issue Oct 25, 2024 · 16 comments

Comments

@sebastian3107
Copy link

The problem

Is there a way to resume a task after the robot has been sent back to the dock?
I tried using the general lawn mower action like lawn_mower.start_mowing which should also handle the resume function. This fails with this notification in the Mammotion app when the robot is docked:
image
This resuming does work if the robot has only been paused previously via lawn_mower.pause and is not docked.

I am looking for a way to press this resume button via the integration.
image

Is there a plan to have an action like mammotion.resume_mow?

What Mammotion mower are you using?

Luba 1

What version of the Mammotion intergration are you using?

v0.1.78

What version of Home Assistant Core are you running?

core-2024.10.3

@mikey0000
Copy link
Owner

Seems to be a similar issue as to what was raised in Discord, I'll check the resume logic and see whats going on.

@mikey0000
Copy link
Owner

I fixed this today, will be out in next release to verify

@mikey0000
Copy link
Owner

Please try 0.1.88

@mikey0000
Copy link
Owner

Reasonably sure this is solved now, feel free to reopen if its not.

@sebastian3107
Copy link
Author

I just tried it with 0.1.91 and still get the "Mowing area selection is abnormal" when I try to resume a task while being docked.

@mikey0000
Copy link
Owner

mikey0000 commented Nov 4, 2024

I just tried it with 0.1.91 and still get the "Mowing area selection is abnormal" when I try to resume a task while being docked.

This is resuming when the mower has gone to dock on its own right?

@mikey0000 mikey0000 reopened this Nov 4, 2024
@sebastian3107
Copy link
Author

This is resuming when the mower has gone to dock on its own right?

That I haven't tested. What I meant is when I sent it to the dock either manually in the app or via the integration.

@mikey0000
Copy link
Owner

OK and that's during a mow? As I thought I'd tested this, this is easier to test as well. I'll retry it tomorrow.

@mikey0000
Copy link
Owner

mikey0000 commented Nov 6, 2024

OK I think I saw whats happening, I just had my mower randomly pause for no reason at all, and it was in mode_ready. and puased in app. Which will definitely throw HA off in terms of logic. Can you confirm the activity mode was mode_ready?

@sebastian3107
Copy link
Author

image
It goes from MODE_RETURNING back to MODE_READY, despite still having a task active.

@mikey0000
Copy link
Owner

mikey0000 commented Nov 6, 2024

Cool now I know what's happening I can resolve it. Really annoying though

@mikey0000
Copy link
Owner

Can you try on the latest release please

@sebastian3107
Copy link
Author

sebastian3107 commented Nov 9, 2024

I tried using v0.1.100, but I still see the same error in the Mammotion app.

Steps to reproduce:

  1. Start a task in the app (I haven't tried starting the task via the integration)
  2. Send Luba back to dock using the house icon in HA.
  3. Try to resume the task via the HA integration once the robot has docked (using the Play button in the GUI)

@mikey0000
Copy link
Owner

I think I sorted it this time, can you try on the latest. At least I've been able to resume with the luba 2

@sebastian3107
Copy link
Author

Sorry for the delay, but we already had some snow here last week.
I just tried it again using v0.1.107, but I still see the same behavior on Luba 1.
In the app I get the error code 1415 when I try to resume a task from the dock.
It is sitting on the dock in the states MODE_READY and CHARGE_ON, but it still has the active work area hash (instead of "Not working").

@mikey0000
Copy link
Owner

Sorry for the delay, but we already had some snow here last week. I just tried it again using v0.1.107, but I still see the same behavior on Luba 1. In the app I get the error code 1415 when I try to resume a task from the dock. It is sitting on the dock in the states MODE_READY and CHARGE_ON, but it still has the active work area hash (instead of "Not working").

OK I'll see if I can find out what's going on specifically for the Luba 1's

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

2 participants