Figuring out the future of this library

[William Pietri]

Hi, folks! We have previously discussed what to do with this library. My vacuum is starting to make funny noises, which reminds me that we should figure that out.

When my current vacuum dies, I won't be replacing it with the same model, and likely not from the same vendor. That means I won't be able to test new code at all. Further, it has come to bother me that Ecovacs still doesn't have an API for their devices, or even published developer docs. It doesn't feel like a good use of my time to, in effect, subsidize their behavior.

If someone (or better, a few someones) would like to officially take this over, that's great. The code has been ported to a few languages and there 48 GitHub forks of this project, so it's possible there's enough of real community of vacuum enthusiasts out there to sustain something.

If not, then when my vacuum dies I'll sunset the project, probably after making one more check to see if anybody cares. By sunsetting I mean marking it abandonware in my repo and on PyPi, closing the issue tracker, and eventually ending the mailing list.

If you'd like a different outcome, now's a good time to speak up.

William

[Guillermo Schimmel]

I use the library but understand completely.

You shouldn't work for Ecovacs given that they don't seem to care at all.

Thanks for all your effort so far.

Regards

--
You received this message because you are subscribed to the Google Groups "sucks-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sucks-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sucks-users/0a07b199-92e1-584e-2397-626b619edb44%40pota.to.

[Jasse]

I'm also using the library, but I absolutely understand your situation. Great job on creating what you have, we are all very thankful that you shared this project with us.

[William Pietri]

Update: My vacuum failed once with a brush roller lockup, so I took it apart. That worked for another week or so, but then it failed again. Per Wirecutter's suggestion, I now have a Roomba 675;  it seems perfectly adequate, so I'm keeping it.

Since I no longer have hardware that can run this code, I'm no longer able to test any changes, meaning I'm poorly placed to maintain it. If one or more people would like to pick up the torch, let's talk. But if not, in a week or so I'll mark it as abandonware.

Either way, I'm glad it was useful to so many people over the last 2+ years. I really appreciate all the feedback, encouragement, code contributions, and assistance to other users that people have contributed. Thanks to all of you!

William

[Brian Martin]

William,

Thank you for all the time and work you put into this project.  While I’ve contributed in the past, I’m not a true consumer of sucks - I don’t utilize it for any automation and mainly worked on it to test with Bumper.  That said, I won’t be stepping up or volunteering to continue development efforts for it.  

Thanks again!

-Brian

To view this discussion on the web visit https://groups.google.com/d/msgid/sucks-users/3ffa06bd-cf0a-9e3f-7ecd-119d2ca6a71a%40pota.to.

[Maximilian Baehr]

Hi Martin,

that is very sad to hear.

I have a 980 at Home and am trying to get it to work with Home Assistant.

I can try to develop for this, but I have almost zero Knowledge in Python.

Best regard,

Max

Am Donnerstag, 12. März 2020 17:49:18 UTC+1 schrieb Brian Martin:

William,

Thank you for all the time and work you put into this project.  While I’ve contributed in the past, I’m not a true consumer of sucks - I don’t utilize it for any automation and mainly worked on it to test with Bumper.  That said, I won’t be stepping up or volunteering to continue development efforts for it.  

Thanks again!

-Brian

On Mar 11, 2020, at 4:24 PM, William Pietri <wil...@pota.to> wrote:

Update: My vacuum failed once with a brush roller lockup, so I took it apart. That worked for another week or so, but then it failed again. Per Wirecutter's suggestion, I now have a Roomba 675;  it seems perfectly adequate, so I'm keeping it.

Since I no longer have hardware that can run this code, I'm no longer able to test any changes, meaning I'm poorly placed to maintain it. If one or more people would like to pick up the torch, let's talk. But if not, in a week or so I'll mark it as abandonware.

Either way, I'm glad it was useful to so many people over the last 2+ years. I really appreciate all the feedback, encouragement, code contributions, and assistance to other users that people have contributed. Thanks to all of you!

William



On 2/10/20 11:13 AM, William Pietri wrote:

Hi, folks! We have previously discussed what to do with this library. My vacuum is starting to make funny noises, which reminds me that we should figure that out.

When my current vacuum dies, I won't be replacing it with the same model, and likely not from the same vendor. That means I won't be able to test new code at all. Further, it has come to bother me that Ecovacs still doesn't have an API for their devices, or even published developer docs. It doesn't feel like a good use of my time to, in effect, subsidize their behavior.

If someone (or better, a few someones) would like to officially take this over, that's great. The code has been ported to a few languages and there 48 GitHub forks of this project, so it's possible there's enough of real community of vacuum enthusiasts out there to sustain something.

If not, then when my vacuum dies I'll sunset the project, probably after making one more check to see if anybody cares. By sunsetting I mean marking it abandonware in my repo and on PyPi, closing the issue tracker, and eventually ending the mailing list.

If you'd like a different outcome, now's a good time to speak up.

William
--
You received this message because you are subscribed to the Google Groups "sucks-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sucks...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sucks-users/0a07b199-92e1-584e-2397-626b619edb44%40pota.to.

--
You received this message because you are subscribed to the Google Groups "sucks-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sucks...@googlegroups.com.

[Duncan Bayne]

I'm a keen Home Assistant user currently building out a home automation solution, which is how I discovered sucks - I have a fleet of 3 DeeBot 600s at home, and plan to add more.

Having had some luck getting good API docs from Rinnai for their Wi-Fi module, I'm currently chasing various leads at ECOVACS trying to get good API docs for the DeeBots ( see https://github.com/wpietri/sucks/issues/93 ).  This started out as an itch-scratching exercise; my 600s don't work with Home Assistant yet :)

Would you like me to take over maintenance of the library?  My commercial experience with Python is limited and I'm only recently getting into home automation.  But I have a background of decades as a developer (C, C#, Ruby, JavaScript, Java, Clojure, Common Lisp), including some IoT / smart grid work on Tridium systems; I think I'd be well suited to the task.

[Kevin McCormack]

I ran into the issue where the Ecovacs home assistant integration stopped working with the latest version 2022.7

https://github.com/home-assistant/core/issues/74564

I would be happy to lend a hand maintaining the library but would prefer to not do it solo 😁. I have a DEEBOT N79 and a Roomba i3

I also wrote the (limited) https://www.home-assistant.io/integrations/vivotek/

[Alex Szymanik]

I have a working fix for HA core-2022.7 but will need to update a sucks-dependent library to do so (sleekxmppfs). Fortunately,  OverloadUT is the maintainer of both. I put in a PR for sleekxmppfs. If approved, should allow HA to work with Ecovacs again.

https://github.com/OverloadUT/SleekXMPP/pull/1

[Alex Szymanik]

In retrospect, it's unlikely the PR will be approved (and also has like 43 manual merges).

I've merged and created a fork on my github: https://github.com/aszymanik/SleekXMPP

Not sure where to go with this now though...

[Allie Laabs]

Hi William -

I've got a PR ready for sucks to simply bump the dependency on sleekxmppfs by a version to fix the library. I saw that you've archived the project on GitHub so it won't let me submit the PR.

I'd be happy to take ownership of the repo (or just unarchive and have me as a maintainer, as well as PyPi) in order to push out this update.

I'm not planning on doing anything more than this maintenance hotfix though. Another option is I could just push up under a new name on PyPi if I don't hear back :)

Allie (aka OverloadUT)

[William Pietri]

Hi, Allie!

Let's give it few days for people to object, but absent that I'm happy to have you take it over.

I have no experience here, but apparently we have to pick between moving the repo and just blessing your fork of it by changing the docs, etc. The latter seems easier and safer to me, so I'd prefer that. We'd also have to give you PyPi powers, which I'm happy to do, especially if you tell me exactly what needs doing.

William

--
You received this message because you are subscribed to the Google Groups "sucks-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sucks-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sucks-users/2480f11e-1b97-4ec1-b9c7-c5a30606f151n%40googlegroups.com.

[Michelle Dupuis]

Any progress on creating a fork?  This project sounds perfect for me...but if there is a fork that is being maintained I would rather use that.

Hopefully someone keeps this alive.  Actually, I would hope that Ecovacs sends you a free robot to promote the project!  Might next vacrobot might be a Roomba if that's where the CLI/API support is.