583
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 11 months ago by to c/technology@lemmy.world
69 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
[–] -1 points 11 months 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.

  • permalink
  • fedilink
  • source
  • parent