this post was submitted on 05 Dec 2025
464 points (99.2% liked)

Technology

77096 readers
2086 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

An engineer got curious about how his iLife A11 smart vacuum worked and monitored the network traffic coming from the device. That’s when he noticed it was constantly sending logs and telemetry data to the manufacturer — something he hadn't consented to. The user, Harishankar, decided to block the telemetry servers' IP addresses on his network, while keeping the firmware and OTA servers open. While his smart gadget worked for a while, it just refused to turn on soon after. After a lengthy investigation, he discovered that a remote kill command had been issued to his device.

you are viewing a single comment's thread
view the rest of the comments
[–] imetators@lemmy.dbzer0.com -5 points 1 day ago (2 children)

That's like a month old news article

No one should be outraged. That is how all robovacs are working - use LIDAR to map area -> send back to server -> server calculates optimal cleaning route -> sends back info to vac -> vac cleans. Vac cant ping back to server - server thinks vac is dead. No killswitch is needed.

Also, app is not a necessity except we are forced to use it. But many would not like to lose an ability to track progress or start and stop cleaning from their phone outside of the home network. For these features, app and external server is a must.

The only real issue with robo vacs is that it is an IoT device. We should make manufacturers and brands to let us choose if we want to selfhost their software. But that would never happen.

This article IMO is full of bs and ragebait.

[–] GreyEyedGhost@piefed.ca 1 points 18 hours ago

Pretty much everything you said is incorrect, except for the article age. Valetudo literally wrote software that does this on multiple models locally, including mapping. The response of the manufacturers whose models were capable of this was to release new versions where this wasn't an option. As for servers and local control, there are a number of solutions for those with the knowledge and hardware to set it up, and the only thing stopping robovac companies from supporting this is (less) money.

[–] nekusoul@lemmy.nekusoul.de 3 points 1 day ago (1 children)

What I don't understand is why the person that owns the device wrote the following in their blog post:

How could a simple IP block disable a vacuum cleaner that is supposed to work offline as well? - Source

This seems like that device was sold to him as "offline" capable. Where does that claim even come from? From a cursory glance I don't see that product advertised that way anywhere.

Now, I'd be totally in favor that such devices working offline should be the norm, but then again, the person writing the blog should know how these devices currently work.

[–] imetators@lemmy.dbzer0.com -2 points 1 day ago* (last edited 1 day ago)

Say, if he got it because it was advertised as an offline device then why would he connect it to wifi anyway? The more I read this article, the more questionable this so called "IT specialist" is.

This is how it has been for a long time - robovacs do talk to a server. Should it? Not necessary. But they undeniably do.