this post was submitted on 05 Dec 2025
589 points (99.0% liked)

Technology

77715 readers
4398 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
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
589
Manufacturer issues remote kill command to disable smart vacuum after engineer blocks it from collecting data — user revives it with custom hardware and Python scripts to run offline (www.tomshardware.com)
submitted 1 week ago by spaghettiwestern@sh.itjust.works to c/technology@lemmy.world
142 comments fedilink hide all child comments
 

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
[–] jjlinux@lemmy.zip 6 points 1 week ago

This is every single 'smart device' out there. The way I was able to block everything in 2 Roborocks at home was by setting them up in Home Assistant over Matter, blocking everything and using it from HA only (us the schedules, those remain in the robots). It's less than convenient allowing it access to the update servers once per month to see if there's any and then blocking it again, but it's something.

We're preparing our 'smart home' for our new house that's not finished yet by choosing only devices that are matter over wifi (not thread) so that I can set it all up to work locally ove Home Assistant. That, in my opinion, is the best way to keep some convenience while shutting those assholes out.