Valetudo VS Home Assistant

Obligatory Valetudo reference. Replace the robovac firmware so it doesn't do cloud.

https://valetudo.cloud/

Can't help with the rest unfortunately.

Been meaning to try something like https://valetudo.cloud/ on my iRobot but I haven't checked out how hard it is.

I can repeat that experience but didn't take me quite as long as I had time to walk through it.

However, just this last update, they added support for a new set of vacuums, Midea/Eureka that don't require that PCB.

https://github.com/Hypfer/Valetudo/releases/tag/2025.12.0

You may want to check if your robot is supported by Valetudo: https://valetudo.cloud/

https://valetudo.cloud is the only one I know about but not sure if the controller in those units would be flashable.

People obviously find them useful. But I will reiterate a sibling comments recommendation, get one that can run Valetudo : https://github.com/Hypfer/Valetudo

Valetudo. I haven’t had personal experience using it (due to an unsupported model of NAND memory chip), but I’ve heard good words: https://valetudo.cloud/

This user is talking about this story:

https://github.com/Hypfer/Valetudo/issues/1664

So is this like Valetudo[0] but for mowers? Very cool! I wonder how much overlap / shared code there is between robot vacuums and robot mowers.

[0]: https://valetudo.cloud/

Yeah that’s an issue! But I also found this interesting project: https://valetudo.cloud

It’s a local first solution for robovacs and there are a few popular models!

https://www.home-assistant.io/

the interface can be set up on her phone, a tablet on a wall, and limiting things to giant buttons and displays is very easy for you.

And, you can monitor and be alerted near real time to issues of course.

Not the title (maybe you tried to deep link and the fragment got stripped?), although it is funny when the agent delivers a recipe (c/w "You are absolutely right")

https://github.com/home-assistant/core/pull/173465#issuecomm...

Do you have examples of issues? OCI is tarball of dependencies that doesn't fight with the OS userland.

Why do you need to write code to insulate Python in containers?

At the simplest level, you can add the flags to the container runtime (network host, host ipc, host process namespace) to turn off all the namespacing besides filesystem and the Python container runs just like a non containerized process.

An extreme example

https://github.com/home-assistant/docker-base (Debian, Ubuntu, Alpine base images with Python for arm64 and amd64)

& https://github.com/home-assistant/core/blob/dev/Dockerfile (Python app built on those with >1000 deps)

And even there most of the custom code is just running a ton of combinations of inputs against docker build.

I don’t really know why, but since recently I’ve been reading and watching videos about Home Assistant (HA), and it has always sounded very appealing but I’m a bit change averse and don’t want to commit to something if I’m not sure that I’ll make good use of it. So, when I recently started seriously considering purchasing a Home Assistant Green (which is a preconfigured system running HA), my inner self pushed me into the hole:

Home Assistant for automations

It is essential to purchase and configure Home Assistant (https://www.home-assistant.io/) compatible devices around the home whenever possible if you want a "smart home" that will last.

That host and the BACKUP bay are part of a Home Assistant installation I did with their HAOS system. If you'd like to know more about it let me know.

The solution is home assistant [0] it lets you manage and control all kinds of smart devices with a lot of customizable, hackable things. And it runs locally, so if you buy the right types of devices that don’t phone home to the cloud (or you shitcan their internet access) you can fully manage your own system.

[0] https://www.home-assistant.io/