Replying to an earlier post

From what I gather, valetudo sits between the firmware and the cloud, co-opting cloud functionality and serving that from the vacuum. Since nothing is going to the cloud, only the information stored on the robot, or that you’ve stored yourself, can be used against you. So while your vacuum may have a microphone or camera, it shouldn’t be recording what you say or do anywhere. I have yet to start my valetudo journey and have barely started my robot vacuum journey precisely because of scenarios like this.

Replying to an earlier post

The code is open source. Like any open source software, unless it’s been vetted, you’re relying on trust. The premise is that the software is running on the vacuum, so there is no cloud or remote storage. So, just like anything else self-hosted, unless your network is compromised or you configure it to allow it, nothing external is accessing it. If you don’t trust it, vet it. Read the code or check your network logs.

Replying to an earlier post

From what I can see, one of two things happens. First, the main cloud communications are intercepted and handled by Valetudo. It replaces the cloud infrastructure with the firmware it adds to the vacuum. Second, some require connectivity to your router or the internet in general. Connections to your router shouldn’t be harmful, and he specifically leaves blocking connections to the internet (which shouldn’t be required for the vacuum to function). I’m only speculating here, but given the open-endedness of the comment I’m guessing explicitly blocking certain connections could be considered an illegal circumvention by laws such as the DMCA. I’d like them to note which vacuums those are so they could be more easily avoided.

Replying to @⁨VibeSurgeon@piefed.social⁩

Valetudo actively blocks the cloud connections. Also, only firmware versions specifically installed with Valetudo is supported (so no chance an update to the original device firmware happens, and does new things).

I think there’s a very low chance something escapes to the vendor cloud.

None the less, I personally run these on a separate VLAN without internet access.

Replying to @⁨VibeSurgeon@piefed.social⁩

It’s just DNS based, and iirc dont require any major effort other than patching the hosts file. Of course it is possible it is not enough, but I have high confidence in the authors after also having watched various talks at I.e DEFCON, that i would be surprised if they missed the firmware doing other nasty things.

Patching DNS is specifically possible to enable/disable on the firmware build tool: I.e builder.dontvacuum.me/_dreame_r2416.html and the source for that is here github.com/dgiese/…/modifys8image.sh#L169

Replying to @⁨gopher@programming.dev⁩

It’s just DNS based, and iirc dont require any major effort other than patching the hosts file.

Incorrect. That was technically sorta the case back on the S5 (and even there it needed firmware modifications), yes, but if DNS redirection was all it needs, then why even root the bots in the first place. Just do that on a network level and be done with it.

Replying to @⁨Hypfer@discuss.tchncs.de⁩

Oh okay, I just assumed the main method to redirect the vendor cloud connections to the local valetudo was based on the patch DNS parts in dustbuilder that seems present on most models, but if you say more is required elsewhere to block vendor cloud connections I’m sure that’s true.

In any case your work is highly appreciated! And i didn’t mean to suggest that it hasn’t taken a massive amount of work overall to make valetudo work as well as it does.

Replying to @⁨gopher@programming.dev⁩

Aaah! Oh. Yes that makes a lot of sense indeed.

The UX (and architecture, for that matter) of the dustbuilder has been… uh… lacking… due to the lack of refactoring. It evolved over all these years, and things that had a meaning once suddenly gained a different one, but are still named in the old ways.

Good point, thanks for pointing it out! I’ve been doing some refactoring there, actually, and there, it’s named “disable cloud”, but I just did that for correctness. It did not occur to me that from a user-perspective, this is not just weird but actively misleading. I mean it kinda did, but I did not make the mental connection to this specific misconception. Oh well.

Replying to an earlier post

Given that you are the author of the project, I do consider you the higher authority on what it can and cannot do.

But to me, there’s a slight distinction to be made here - Valetudo allows you to directly control the robot from a server running locally on the robot, giving you the option to not interact with a cloud service in order to remotely control the robot vacuum.

This doesn’t immediately imply that the robot is directly prevented from passing information to a cloud service - just that the cloud service does not have to be involved as a command proxy.

The larger feature I was thinking of was not only serving a local server to allow commands to come in directly, but also actively prevent any outgoing connections from the robot vacuum to its manufacturers cloud.

Again, you are the author - you know far better what Valetudo does and does not do, so your information weighs heavier here.

I guess I can also mention that I will be pleasantly surprised if my Chinese robot vacuum has actually been prevented from logging any information back home as a part of me having run Valetudo for the past years.

Replying to @⁨doomsel@lemmy.world⁩

The case mentioned here (in the beginning) is a husband manually using the camera of their robot vacuum to catch her cheating on him and using the recording as evidence in court (and subsequently have it used against him for unlawful recording). This can happen with your valetudo vacuum (assuming it has a camera) too, since it’s just user based behavior.

Replying to @⁨susieq0044@sh.itjust.works⁩

I would say the way that most people use smart devices, yes. But if you have the time and patience to select the correct smart devices and set them up properly, you’re fine.

Of course, people are lazy, so for most folks, inviting Google Alex or Nest into their house leads to…chicanery.

PS: pick a robot vacuum cleaner that can work without sending shit to someone else’s server. And make your own “Alexa”

Replying to @⁨susieq0044@sh.itjust.works⁩

Smart home stuff can be done right.

  • You need to focus on the use case. Is what it is doing actually necessary? E.g. smart lights are amazingly useful, smart washing machine? Why?!?

  • The S in IoT stands for security. Smart devices need to be treated as security risks. Mine have their own WiFi to play on. They don’t get to play with my important devices. Also, internet access is a privilege, not a right. ZigBee is often superior to WiFi too. Control the bridge and you have absolute control of their internet access.

  • Open source for the win. A lot of IoT options can run open source firmware. This helps break open the black boxes and let you see if they are doing bad things. Home assistant, EspHome, and Tasmota are the big 3 to look into.

  • If you’re not the customer, you’re the product. Google etc sell smart speakers at a loss. If you must have them, treat them as actively hostile. I’m still trying to find a good alternative to some of their functions, but getting there.

Replying to @⁨nkat2112@sh.itjust.works⁩

I’ve been playing with my smart home for years now. I’m well past the “oh wow” honeymoon phase and into the “just do your job” phase.

I forgot to mention WAF, Wife Acceptance Factor. Any smart system should fall back to a dumb one, if something goes wrong. E.g. You should never require WiFi to turn your lights on. There should always be a switch that will just work. Central control computer crashes? The wife is annoyed the house is now just dumb, not that the house is now dead.

Replying to @⁨cynar@lemmy.world⁩

Smart washing machine: ours is in the basement and my wife and I used to regularly forget we had laundry in it. I now have Home Assistant text us when a load is complete. But it only texts us if we are home and can do something about it. If nobody is home it waits until one of us gets home to text us.

BUT: The washer and dryer are still dumb, pre-IoT generation. I built light sensors that are taped to the displays, and Home Assistant relies on those to determine if the appliances are on or off. No need for cloud-based monitoring, etc. A little creativity like that can work just as well or better than a convenient cloud-based solution.

Replying to @⁨IphtashuFitz@lemmy.world⁩

I’ve considered that, for the same reasons. My machines are obnoxious enough to be heard through half the house on their own however.

The built in smart ones seem to be the worst of all worlds. They farm you for data, while not providing much of use. They try to tie you into ecosystems, that stop you using the data elsewhere.

My solution was going to be to monitor current draw, via a power monitoring plug, running Tasmota. Once it’s below a threshold for long enough, send an alert.

Replying to an earlier post

Also, internet access is a privilege, not a right. ZigBee is often superior to WiFi too

I’m setting up a smarthome from scratch the last few days. After having Philips Hues and a Google Home for ages at my previous home, my new place has downlights rather than edison screws so none of my lights work and after a year I’m finally trying things out properly. Got a server with Home Assistant and border routers for Thread and Zigbee, bought a bunch of no-brand Zigbee downlights and Ikea sensors with Matter over Thread. No wifi is a hard requirement for me. For security reasons and for performance. I don’t want a dozen extraneous devices littering my wifi network.

Replying to @⁨Mustachius_Grumpius@thelemmy.club⁩

Soon, every fuckin’ thing you buy that plugs in will have an app, and demand to connect to the internet, and do it’s damnedest to make that happen, whether you let it or not. There’s probably a generic, dedicated chipset or board that does just this available for OEM purchase that they just wire into whatever they’re building. Fans, speakers, TVs and monitors, every appliance, lights, clocks, push vacuums, pet feeders, smoke alarms, anything you can think of. They’ll add some feature that no one wants to justify the camera, mic and internet connection. Or, they’ll just hide it, because whatever law might be used against them for doing that would not be strong enough to outweigh the profits, if it’s enforced at all.

If you have old appliances without these “features”, do your best to keep them working.

This won’t stop until we kick the capitalist out of our governments.

Replying to @⁨DarrinBrunner@lemmy.world⁩

There's also a social factor in play: yes, I could refrain from having "smart" apparata (and face the crushing social ostracism stemmed from this choice), but if one of my neighbors have a "smart" apparatus, depending on which one it is, it could technically be used to spy on me. I mean, the whole polemic involving Meta's Creep-Glass has to do exactly with how those things can be used and are being used to spy on others, unbeknownst to said others who never ever purchased a Creep-Glass.

!technology@lemmy.world

Replying to @⁨dsilverz@catodon.rocks⁩

Exactly. Even if you do everything right as an individual, if the society you live in is shit, your personal discipline will not protect you.

And then some ahole will tell you not to take any of it personally. Because if the bad thing is only happening to you, it’s horrible and you deserve to be angry. But if the same thing is happening to everyone, then you get to smile and carry on like it’s normal, and like it is supposed to be like that.

Replying to @⁨DarrinBrunner@lemmy.world⁩

There’s probably a generic, dedicated chipset or board that does just this available for OEM purchase that they just wire into whatever they’re building.

Yup. It’s called an Espressif ESP8266, and it’s spawned a bunch of variants including the more powerful ESP32. It’s a little microcontroller on a circuit board with an antenna on the board, cost about $1-$2 in quantity, out of the box it speaks WiFi and most variants now have Bluetooth also. It’s got enough intelligence on board to run a simple IoT gadget, and if you want more it’ll act as the communication module for your larger system board. And since it’s got all the RF approvals (FCC, CE, etc) already done, it means you can add RF communication to your product without expensive RF certification.
In fact, use an external low voltage power supply (which comes with its own certification), and pretty much the only regulatory testing you need to do is to prove it won’t spontaneously catch fire.

Anyway there’s over a dozen variants of ESP-family chips and boards with various capabilities. Here’s an example. Or that same example mounted on a breakout development board. See the pinout here- this little module is a proverbial tub of Legos with TONS of capability to unlock.

Then throw in some cloud platforms like Tuya that will handle most of the cloudiness so all the developer needs to do is write an app and sell products.

Replying to @⁨Mustachius_Grumpius@thelemmy.club⁩

I use homeassistant, it even keepa tabs on my homelab, etc. Only way to do smart home right is with ZigBee,zwave and esphome. None of these devices need internet access. Everything I have on my smart home is local and on its separate vlan. Again this isn’t for everybody because it does take a lot of time if you don’t know what your doing. Home assistant has come a VERY LONG way though and is very much user friendly now.