Valetudo 2023.02.0

[Hypfer]

2023.02.0

Custom instance names, more robots and quality of life improvements for existing robots

Custom instance name

It is now possible to set a custom name for your Valetudo instance.

This should be especially helpful for setups with multiple floors and thus multiple robots.

Additionally, this name is also part of the data advertised via MQTT, meaning that the robot will show up like that in Home Assistant as well.

New robots

Mi Robot Vacuum-Mop 2 Ultra

After buying a Mi Robot Vacuum-Mop 2 Ultra to evaluate if it can be rooted and supported, I can now answer yes to both questions.

It's like a Dreame Z10 Pro but with the auto-empty dock being optional and a ToF sensor instead of line lasers for obstacle avoidance.

More Viomis

Valetudo users Matthias and @zombielinux meanwhile tried the CRL200S rooting instructions with the Viomi SE and Wyze Robot Vacuum and succeeded in doing so.

Unfortunately though, shortly after that, another user reported that they've bricked their Wyze Robot Vacuum while attempting to root it :(
Thus, for now only the Viomi SE will be part of the Supported Robots list until we gain further insight into the issue.

Existing robots

Roborock S7

In the last month, I've also bought a Roborock S7. Using this test device, I was able to work through the rooting procedure, fixing things along the way. Apart from that, Quirks for a few additional S7 features have been added to Valetudo as well.

As of now, there are no more known issues with the S7 excluding the rather complicated disassembly that is unsuited for beginners.
It is now considered supported by Valetudo and rootable with the latest firmware.

Roborock General

People with a Roborock supporting the MappingPassCapability should now instantly see segments after the mapping pass has finished.

For owners of a Roborock that needs to do a full cleanup to split the map into segments, a new Quirk was added that allows to manually trigger the split. While janky in implementation, it can nonetheless be helpful for quick remappings using for example the go-to feature.

Segments on vSLAM Dreames

Segments should now appear instantly after a full cleanup on vSLAM Dreames such as the 1C, 1T or F9. Previously it was necessary to trigger a second cleanup for that.

Misc

1. The Live Map now remembers the previously selected mode in the browser's local storage.

2. Valetudo now pings the Gateway every 15 Minutes to keep the Wi-Fi module alive.
   This should help in situations where the Webinterface became unresponsive after being idle for a few hours.

3. There's now no more mop attachment reminder on Dreame robots that feature automatic mop drying.

The usual

If you want to see Valetudo on more robots and/or like this release, you might want to consider donating:

https://github.com/sponsors/Hypfer

https://builder.dontvacuum.me/donations.txt

Autogenerated changelog

Breaking Changes

• Allow setting a custom friendly name for the valetudo instance 612c484

Features

• Migrate existing MQTT friendlyName to instance friendlyName on upgrade 3d9c7c2
• vendor.roborock: Add manual map segment trigger quirk 54891dc
• ui: Replace consumables view with boring but unified ListMenu 7173bc6
• vendor.dreame: P2150 (Mi Robot Vacuum-Mop 2 Ultra) support 1909f24
• vendor.roborock: More quirks for the S7 f789df0
• Periodically ping the gateway when embedded to keep the wifi module alive d2637fd
• ui: Remember the last selected live map mode in the browser cf15896
• vendor.viomi: Add mop pattern quirk to Viomi V7 (Add mop pattern quirk to Viomi V7 #1682) 127a086

Fixes

• vendor.dreame: Don't raise the mop attachment reminder for robots that can dry their own mops aba7931
• vendor.dreame: Display vSlam segments after initial cleanup a00280a
• vendor.roborock: Fix map not immediately showing segments after a mapping pass 25a6670
• vendor.dreame: Newer 1T firmwares have a sensor consumable ad59e09
• webserver: Add return after failing to load OpenAPI spec (fix(webserver): Add return after failing to load OpenAPI spec #1689) b37fb09
• vendor.viomi: Fix manual control state not being reported correctly 3fe2998
• Handle special character ssids in linux wifi status d75514b

Chores

• release: 2023.02.0 6b01ed5
• Update actions to fix github workflow deprecation warnings d4a7ae3
• Formatting bebf0a4
• Remove config migration code 50a15a0
• Delete obsolete deployment instructions beee8b1

---

This discussion was created from the release Valetudo 2023.02.0.

[zombielinux]

I’d love to know more about the Wyze being bricked.

I know there were some that were unusable out of the box from Wyze. Those were supposedly “bricked” from the start.

[Hypfer]

Similar to the Viomi v8, it seems that there are robots with the same model name that behave differently.

In this instance, the "press power button 10x" method did not work, however the enable-adb.sh script did, as there was an adbd that very briefly appeared.
What this script does is that it disables the main process as that would - at least on viomi v7 - disable adb access as soon as it starts up: https://github.com/Hypfer/valetudo-crl200s-root/blob/ab56659fa8d36d039fb6bb9611760793ec0f0e42/enable-adb.sh#L70-L72

This effectively bricks the robot but on the v7 that's fine because then you'll have adb access to undo that.
With the robot of that user however, adb never came back :/
This likely means that the whole business of starting and stopping adb works differently in that wyze firmware

[Skjivar]

Hey
I tried to flash my vacuum cleaner Roborock S7 with the image from Dustbuilder. However, after flashing I could not access the robot via ssh.
You wrote that you were able to flash your S7, I would be interested to know what software version your robot had at that time. Or do you know if flashing should work with version 2.15.78?

Even though this is not a direct dustbuilder discussion I hope it still fits the topic here.
Thanks a lot

[Hypfer]

Indeed off-topic for these release notes. It would be best to discuss this in one of our telegram groups.

Rooting should work for all known firmware versions including 1578 and 1612

[elitistphoenix]

"a new Quirk was added that allows to manually trigger the split"
This was awesome and incredibly useful. Thank you!

[rufik]

Hmmm, there is no option in UI to choose how many times my Viomi SE should cleanup segment or area. Is it by seeing or bug?

[Hypfer]

To my knowledge, that feature is not supported by the viomi firmware

[rufik]

Well, MiHome app has an option to repeat vacuuming and it works. Do you thing this feature is app-controlled, no fw-controlled?

[Hypfer]

As I haven't ever used the app, I have to rely on footage on youtube here.
I guess you mean the "secondary cleanup" toggle as can be seen in this screenshot?

Because there at least don't seem to be any controls for that in the map view itself.

That works different from how it is with the other robots but it should be possible to implement.
My only concern there is that it requires a second command to be executed first, which given the unreliable nature of the viomi firmware might set that flag even though it shouldn't be.

We'll see if someone complains
72e6b84

[rufik]

Yes, it is "secondary cleanup" indeed.
Thanks a lot, I'd be happy to test is once it's released :)

[rufik]

I've tried this feature (in 2023.03.0) and it looks like working very well 👍 Thank you very much!

[Biont]

Our Dreame L10 Pro has been running Valetudo for many months and it has been a joy!
After applying this update though, it is very unresponsive: the frontend rarely loads, MQTT does not respond and I cannot even ssh into it anymore.

Sometimes a reboot helps, but I did not have any luck this evening. It seems to power down and reboot normally and the wifi LED comes up, but that's all I'm getting.

Please do you have any advice how to troubleshoot this? I will try to connect with UART some time in the next days. Would you know what to check if I can access the system that way?

Thank you.

[TheDiddel]

Hello everyone, since the last update (2023.02.0) the mode can no longer be set - "vacuum" is the only mode that works. I get the following error message: PresetSelectionCapabilityRouter: Received error from robot while handling route "/preset" { body: { name: 'vacuum_and_mop' }, message: 'Error code -1' }
System information:
Dreame L10 Pro, Firmware Version 1105 Release: 2023.02.0
I have already tried the nightly version, but unfortunately this does not change the problem,
First of all, thank you very much for your feedback and basically: Thank you very much for your work!
Best regards
Mike