From 870d25dd18ead0d75409902dd225cce66e5e7c1c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6ren=20Beye?= Date: Fri, 22 Dec 2023 14:39:15 +0100 Subject: [PATCH] docs: FAQ + some useful hints --- docs/_pages/faq.md | 26 +++++++++++++++++++++++++ docs/_pages/general/supported-robots.md | 15 ++++++++++++++ 2 files changed, 41 insertions(+) diff --git a/docs/_pages/faq.md b/docs/_pages/faq.md index ebfe5d04296..ab79cd08c3a 100644 --- a/docs/_pages/faq.md +++ b/docs/_pages/faq.md @@ -47,6 +47,32 @@ The proper solution is strong legislation enforcing product usage either without in a controlled fashion right out of the box. The vendor cloud can still be an option, but it must not be the only way to use an IoT Device. +## Can I use Valetudo to bypass region locks? + +**No.** + +Valetudo does not support bypassing region locks to e.g. use a CN unit outside of CN. + +The reasoning behind this stance is that, as it works right now, Valetudo existing does not have any negative impact +on sales for the vendors.
+In fact, I'd argue that it has an ever-growing **positive** impact on their bottom line, because +lots of people buy their products _only_ because they can use it with Valetudo. + +However, as soon as you decide to undermine regional pricing strategies of these vendors, you'd be giving them a +_very good reason_ to try their hardest to shut you down. It would be foolish and short-sighted to do that. +On-top, it would also be futile to do that. +You as some rando hacker and developer can't win against a corporate entity of that scale. At least not long-term.
+If you give them (or rather their investors) a business incentive to stop you, they will stop you. + +And what would it be good for anyway?
+Is allowing a few people to save some minor amounts of money worth souring the relations with the vendors?
+Is getting what you want (CN unit with cool features in EU) worth jeopardizing the ability of regular buyers to use their +robot without the cloud? + + +Yes, I hear you, you bought the HW and now you want total freedom over it because you paid for it.
+It's an understandable perspective, but that's not how the world works. And - most importantly - you won't be able to change +how the world works by just forcefully trying to get what you want without considering the needs of other parties involved. diff --git a/docs/_pages/general/supported-robots.md b/docs/_pages/general/supported-robots.md index 4639e67fa2f..ffc0ffd15d2 100644 --- a/docs/_pages/general/supported-robots.md +++ b/docs/_pages/general/supported-robots.md @@ -117,6 +117,8 @@ There are multiple hardware revisions under the same name. Only the `dreame.vacu Rooting is pretty easy, only requiring a 3.3v USB UART Adapter, [the Dreame Breakout PCB](https://github.com/Hypfer/valetudo-dreameadapter) and almost no disassembly. All warranty seals stay intact. +If you only see weird characters on the UART, try `500000` instead of `115200` as the baud rate. + #### Details **Valetudo Binary**: `armv7` @@ -125,6 +127,7 @@ All warranty seals stay intact. #### Rooting instructions - [UART](https://valetudo.cloud/pages/installation/dreame.html#uart) +- [Init override (may be patched)](https://gist.github.com/stek29/5c44244ae190f3757a785f432536c22a) ### Xiaomi 1T @@ -390,6 +393,18 @@ The Dreame W10 is sold as: Rooting is pretty easy, only requiring a 3.3v USB UART Adapter, [the Dreame Breakout PCB](https://github.com/Hypfer/valetudo-dreameadapter) and almost no disassembly. All warranty seals stay intact. +For some yet unknown reason, installing firmware updates doesn't work if we try to pre-package Valetudo as we do +on other dreames. Because of that, with this robot, you will have to manually install Valetudo after rooting. + +For that, follow these steps: + +1. Download the latest matching Valetudo binary: `https://github.com/Hypfer/Valetudo/releases/latest/download/valetudo-armv7-lowmem` +2. Copy the binary to the robot the same way you copied the firmware tar file +3. Move it to `/data/valetudo`. `/data/valetudo` should be the binary. It should **not** be a folder +4. `cp /misc/_root_postboot.sh.tpl /data/_root_postboot.sh` +5. `chmod +x /data/valetudo /data/_root_postboot.sh` +6. `reboot` + #### Details **Valetudo Binary**: `armv7-lowmem`