External Integration - Roborock

Hello @Lokkye, I made a PR to add a widget and actions and triggers.

I also made a request to one day select the rooms to clean on the map and thus evolve this widget :slight_smile:

I don’t know if you’ve seen what has been done for the external integrations of the Dreame robot (Demande d'intégration externe pour robot aspirateur/laveur DREAME - #39 par Chris75) and the Mammotion robot integration (Intégration externe - Mammotion - #41 par prohand)
After testing them extensively, I am really very satisfied with the result because now I can do without the official apps of the brand for all essential functions and settings
And it was developed by @guim31 @prohand in 1 week :flexed_biceps:

Yes but that’s because we’re too strong :smiling_face_with_sunglasses:

Haha (to prompt Claude!)

Thanks so much for your PR, I’m currently reviewing it and giving you some feedback :slight_smile:

return processed :slight_smile:

Code merged :slight_smile:

you noticed there were issues on the repo:

No, I don’t know why I didn’t receive the emails :frowning:, « I » am currently fixing it

Version 2.5.0 released with code by @spenceur and 2 fixes :rocket:

Cool new widget!!

@Lokkye
I made a correction to the image jump that wasn’t very nice and added a condition for the scenes

Sorry for the fix at this hour :slight_smile:

hello I don’t see my card? Do I need to do something else?

@spenceur Sorry for the reaction time but a « small » headache kept me company all evening. I made a small change in your PR, we should avoid modifying the version number in the PRs as it’s another process that does it when building the Docker image.

It’s published under version 2.5.1

Hi, yes great widget for Roborock vacuums, it works perfectly for my Saros 10 R and S7 Max Ultra:

It even shows the last activity… what they don’t store :frowning:

The widget is now only missing the room selection…

The request is here

Your vote

Language diversity… I’m even learning French:

:wink: :joy:

Sorry, I have to point out my message:

It seems that with some newer Roborock models, the assignments between functions and between rooms may be different…

I really don’t want to stop, slow down, or otherwise interrupt the current momentum of development for integrations.

But the fundamental development of Claude without having the actual objects in front of you or corresponding access to test devices seems problematic.

Here’s the example of Roborock:

– Translation mess
– Room assignment is rather left to chance. Sometimes the integration takes the last setting, sometimes a completely different room, and sometimes it actually works.
– Subfunctions, especially on newer models, are not adjustable. Here’s an S7 Max Ultra with its subfunctions:

Vacuum

The integration does not offer the ability to assign suction power, number of cleanings, or distance to vacuuming.

Vac&Mop

Here too, the subfunctions are not offered, so suction power, cleaning intensity, number of cleanings, or distance

Mopping

– The integration does not offer the ability to combine rooms, so I cannot say: Please vacuum room 10 and 12. I am forced to first vacuum room 10 and then go through the process again with room 12.

Final result:
The integration seems to have been developed very quickly without sufficient testing. The widget also does not react stably. Sometimes the widget works, sometimes it doesn’t. Inconsistent state.

Again, I apologize, but the integration should not be published in its current state of development.

Even if I partly share your feelings, I don’t think the conclusion you draw is the right one.

Indeed, I have a Roborock S7 MaxV, so I can test and see that there are gaps.

The issue is rather that we need to find an effective balance between two situations:

  • either we wait for a developer to own the hardware and publish an integration (knowing that, in addition, they can’t own all the hardware from a single brand/protocol)
  • or we dive in and hope for user feedback (who don’t need to be developers).

I genuinely think there’s no debate.
After that, we could always determine whether we consider an integration as « beta » needing testers or « stable »… But even then, the line is blurry.

This is just my opinion, of course, and I especially find that your feedback is precious to quickly evolve the integration! :+1:

@guim31: Don’t get me wrong, I’m the last person who wants to influence anyone here or is allowed to.

My reference to the test devices is based on the developer’s own notes:

  • The device layer (MQTT and local TCP transports, RPC commands) is covered by unit and end-to-end tests against fakes, but has never been exercised against a real robot on a Roborock account. The authentication chain, on the other hand, is verified end to end against the live cloud: region discovery, sendEmailCode, loginWithCode, the home id, and the Hawk-signed home data.

Found:
GitHub - callemand/gladys-roborock: Roborock robot vacuum integration for Gladys Assistant (Xiaomi Home account, local miIO with cloud fallback) · GitHub

With my own vacuums, I only noticed big differences to the older models, and this combination of the developer’s own notes and my tests led to my post.

If I’ve now stepped on someone’s « toes » (German idiom :wink: ), then my apologies.

Regards
Tom