Valetudo 2022.08.0

[Hypfer]

2022.08.0

New firmwares for dreame robots and some bugfixes

New dreame firmwares

It took quite a lot of time and work, but now we're proud to announce that we've managed to get newer dreame firmwares
to work rooted and with Valetudo. A big thank you to everyone who helped during the beta test!

Important: That does not mean that these newer firmwares have become rootable.
You will need to have an already rooted robot to install these latest rooted firmwares.

To update, head over to the dustbuilder at https://builder.dontvacuum.me/ to build and install a new image.
Make sure to update Valetudo before updating the firmware.

Other dreame news

Starting today, every firmware image built with the dustbuilder will contain a fix for the vanishing Valetudo issue,
which occasionally left people with a rooted robot but no Valetudo.

If a user starts a new mapping pass, the fresh map should now appear instantly.
Furthermore, issues with frozen maps either during cleanups or when editing segments were fixed as well.

Robot Coverage View

The UI has been extended with a view displaying a much thicker path.
This can be used to better see which areas of the map have been cleaned.

Whether this view will stick around long-term is yet to be decided. It was pretty easy to implement though.
Feel free to leave your feedback in the comments.

The usual

If you want to see Valetudo on more robots and/or like this release, you might want to consider donating if you haven't done so already:

https://github.com/sponsors/Hypfer

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

Misc

This changelog features artworks generated by DALL-E 2 because I thought it would be neat to have something to look at.
Unfortunately, it doesn't like generating artworks featuring lidar-based vacuum robots (yet?)

I hope they've nonetheless enhanced your changelog reading experience.
Feel free to leave feedback on that as well.

Autogenerated changelog

Features

• vendor.dreame: Newer D9 Firmwares also have a sensor consumable 17c0d27
• ui: Trim whitespaces when renaming segments 39d72f4
• ui: Add robot coverage map a9661a0
• vendor.dreame: Add mop-only quirk for newer firmwares a33afe3
• vendor.dreame: Add Mop Dock UV-C Toggle Quirk 7ce4abe

Fixes

• vendor.dreame: Add support for more features of newer firmwares b74c281
• ui: Add margin to apple touch icon (#1526) dc72ef0
• vendor.dreame: Ignore empty maps 99aad7b
• networkadvertisement: Don't crash the process on ssdp multicast membership errors bfb96c0
• miio: Allow two simultaneous FDS uploads 6e26374
• vendor.dreame: Switch to async map preprocessing to not block the event loop 3b5743b
• miio: Further improve fds upload timeout handling 8c1ba9e
• miio: Gracefully handle connectivity issues when receiving fds uploads 8aab94f
• vendor.dreame: Ignore timezone update message 5ecf7fa
• ui: Allow sending home basic control command while paused 0dfb4ba
• vendor.dreame: Fix maps for newer firmwares 5f67103
• webserver: Fix openapi schema for MapSegmentEditCapability f106735

Refactoring

• webserver: Response cleanup 839310a
• webserver: Actually make use of the openapi schema validation 6e2d2e1
• Introduce RobotFirmwareError and refactor CapabilityRouter for unified error logs 1d2ad47

Chores

• release: 2022.08.0 214b5c0
• Minor cleanup 9356ba8
• vendor.dreame: Fix tests 15eee37
• mqtt: Minor cleanup 4ae1d03
• Minor misc cleanups 7bf3c87
• Add eslintrc flavors b3843f8
• Add close_threads github workflow e10313d
• ui: Add missing rel="noopener" tag to menu bar a7e6920
• build: Bump to NodeJS v18.5.0 66712f9
• Update wording in VoicepackHelp.ts 05a6b89
• Update issue template cebca05

---

This discussion was created from the release Valetudo 2022.08.0.

[thetic]

The coverage view looks great, but it does make it hard to discern the actual path the robot took. I think displaying the old, thin line path on top of the new coverage display would give us the best of both worlds.

[Hypfer]

Like this?

[mrJudahBella]

It would be nice if the coverage path is semi-transparent as well, to present some kind of context as to what was cleaned (the underlying map). If not, it's hard to make out room details and boundaries, at least for me.

[rwjack]

When upgrading the Z10:

• I first went to it's web UI and updated valetudo to 2022.08.0

• I'm then supposed to make a build job with the new firmware on builder.dontvacuum.me

• If so, do I prepackage valetudo or is there no need since it is already installed?
  

• also, the A/B filesystem part had me confused even when doing the initial root (I just did everything twice as described here 🦆.

• Does the filesystem change itself on each reboot A->B and B->A or do I need to trigger it somehow?

[rwjack]

For now I simply upgraded valetudo via web ui, didn't prepackage valetudo on the builder, just downloaded the latest FW and did install.sh once.

Do I need to do anything else?

[Hypfer]

Do I need to do anything else?

Nope that's all