3 ms·

I initially skipped this comment as sarcasm; it’s not! For other readers, the context: Valetudo is a custom firmware project. > Cloud replacement for vacuum ro

I initially skipped this comment as sarcasm; it’s not! For other readers, the context: Valetudo is a custom firmware project. > Cloud replacement for vacuum robots enabling local-only operation

deleted 1y ago
[deleted]
laulis 1y ago
Not a custom firmware.
- boomskats 1y ago
  Custom man-in-the-middleware?
  - hypfer 1y ago
    Cloud replacement. Middle would imply there being another end still.
    - mcv 1y ago
      Local cloud running on your vacuum cleaner.
      - yencabulator 1y ago
        A dust cloud?
LukeShu 1y ago
To expand on laulis' comment: Valetudo isn't a full custom-firmware, it's a mod for the existing firmware. You copy on the Valetudo daemon binary, fuss with the init scripts to start the daemon, and fuss with the DNS and such to point some domains at 127.0.0.1 to talk to that daemon instead of the normal servers (well, actually you probably download a firmware image from dustbin that already has those modifications applied). This is a distinction that is worth making because the robot is still running and relying on all of the on-robot proprietary code; it's just the in-cloud code that has been replaced.
- ghostpepper 1y ago
  it's a bit of a blurry distinction because, what is firmware if not the software that runs on an embedded device? a more accurate description would be that the high-level operating system (HLOS) has been modified to include the installation of a drop-in-replacement for the cloud API. the client side, and whatever hardware abstraction layer lives below it, is untouched. so the client thinks it's talking to the server but it's actually talking to a local open-source server. I think it's also not quite correct to say the low-level firmware is unmodified, because with vale tudo you rely on the project author to provide a minimal rootkit that gets customized on a per-serial-number basis for the initial rooting. from a high-level though, it delivers what it says on the tin - cloud features without any requirement of packets leaving your network or even the robot itself. here's a talk from the author discussing his research https://www.youtube.com/watch?v=AfMfYOUYZvc https://www.youtube.com/watch?v=AfMfYOUYZvc
dvfjsdhgfv 1y ago
> I initially skipped this comment as sarcasm Why on earth would you do it?! It was literally the comment I visit HN for - a solution for the problem we basically all have, already tested by someone, starting a thread with people's experience of it.

I initially skipped this comment as sarcasm; it’s not! For other readers, the context: Valetudo is a custom firmware project. > Cloud replacement for vacuum robots enabling local-only operation

deleted 1y ago

[deleted]

laulis 1y ago

Not a custom firmware.

boomskats 1y ago
Custom man-in-the-middleware?
- hypfer 1y ago
  Cloud replacement. Middle would imply there being another end still.
  - mcv 1y ago
    Local cloud running on your vacuum cleaner.
    - yencabulator 1y ago
      A dust cloud?

LukeShu 1y ago

To expand on laulis' comment: Valetudo isn't a full custom-firmware, it's a mod for the existing firmware. You copy on the Valetudo daemon binary, fuss with the init scripts to start the daemon, and fuss with the DNS and such to point some domains at 127.0.0.1 to talk to that daemon instead of the normal servers (well, actually you probably download a firmware image from dustbin that already has those modifications applied). This is a distinction that is worth making because the robot is still running and relying on all of the on-robot proprietary code; it's just the in-cloud code that has been replaced.

ghostpepper 1y ago
it's a bit of a blurry distinction because, what is firmware if not the software that runs on an embedded device? a more accurate description would be that the high-level operating system (HLOS) has been modified to include the installation of a drop-in-replacement for the cloud API. the client side, and whatever hardware abstraction layer lives below it, is untouched. so the client thinks it's talking to the server but it's actually talking to a local open-source server. I think it's also not quite correct to say the low-level firmware is unmodified, because with vale tudo you rely on the project author to provide a minimal rootkit that gets customized on a per-serial-number basis for the initial rooting. from a high-level though, it delivers what it says on the tin - cloud features without any requirement of packets leaving your network or even the robot itself. here's a talk from the author discussing his research https://www.youtube.com/watch?v=AfMfYOUYZvc https://www.youtube.com/watch?v=AfMfYOUYZvc

dvfjsdhgfv 1y ago

> I initially skipped this comment as sarcasm Why on earth would you do it?! It was literally the comment I visit HN for - a solution for the problem we basically all have, already tested by someone, starting a thread with people's experience of it.