Valetudo VS Home Assistant

If you really want zero network theres always Valetudo, https://valetudo.cloud/

But most of the vacuums want internet access for setup, but then work completely fine being blocked from the internet after.

FYI there is https://github.com/Hypfer/Valetudo which acts as a replacement of the cloud service. I'd you buy one of the supported devices you root it to point to the Valetudo server (which you run yourselves). You can then put the robot on its own WiFi without Internet access if you want to be even more secure.

I'll be the one to plug Valetudo in this thread I guess. Primitively, it replaces the cloud functionality on-device for robot vacuums (see supported models) and replaces it with local services that run offline and can connect to Home Assistant easily.

I will never buy another robot vacuum without Valetudo support as long as that project lives. It's great.

https://valetudo.cloud/

As a consumer and homeowner I try my hardest to buy "smart" things that only have local control, especially for important systems like power and HVAC. Our standby generator has a manufacturer supplied wifi pod that I never set up. Instead I use an RS485-to-USB dongle and monitor it myself with open source software. Our HVAC is the same to the greatest extent possible. When shopping for a new robot vacuum Valetudo[1] compatibility is an overriding concern.

If/when we have solar installed it will not be connected to the manufacturer or distributor's cloud systems.

[1]: https://valetudo.cloud

I have a roborock that I have taken apart a little bit and I thought it looked extremely similar to the article's Roomba from underneath.

Obligatory mention for every robot vacuum article: https://valetudo.cloud/

There are local-only robot vacuum options: https://valetudo.cloud/

But you shouldn't ask yourself why it isn't possible. The question is why it's not successful, or why there's no demand. America is satisfied by foreign alternatives. We don't want secure devices, we want cheap and simple devices that come in pretty boxes with the labels we like. Roomba wins because it caters to the lowest-common-denominator, the basest American that most shoppers embody.

And America doesn't care. You won't see a law demanding software transparency or firmware alternatives for domestic robots. We won't assemble them locally because our labor is too expensive, we won't manufacture the chips domestically because it's cheaper to import them. You won't see people owning USA-made Roombas for the same reason you don't meet people using a Purism phone instead of a Samsung/Apple handset; the market has spoken, and they are absolutely apathetic to anything but price.

Perhaps contact somebody from the Valetudo community with your problem:

https://valetudo.cloud/

https://www.reddit.com/r/homeautomation/

Maybe it can be solved with a simple firmware patch.

https://valetudo.cloud is a project which allows you to use many vacuums without connecting to the cloud.

I also recently began to use Home Assistant. Think of it as an open-source and more powerful alternative to Google Home/Amazon Alexa/Apple HomeKit/Samsung SmartThings. With those vendor platforms, you're limited to what they support. With Home Assistant, you can build your own setups and connect things as you wish, whether it's totally DIY or consumer-ready products from vendors.

https://github.com/home-assistant/core/blob/dev/requirements... lists all the direct dependencies installed in the container.

It's enough for just a single direct or indirect dependency to be compromised to have a botnet or turn it into something used for surveillance against the users.

Preventing it from exfiltrating data by isolating it from the network with Internet access is the only option if you want to run it. This requires local only devices.

Accessing it through the web UI or through the mobile app will still load icons from https://brands.home-assistant.io. The details are in this ticket https://github.com/home-assistant/frontend/issues/18549

Home Assistant

This time, I attended Monitoring your home, with DevOps observability tools. I thought it would be about OpenTelemetry for your home. After the speaker mentioned Home Assistant, however, I didn't pay much attention to the rest.

The rootless .container files go into ~/.config/containers/systemd. I'm using one to run Home Assistant.

ha-aws-cost is a project from Diego Marques for folks who use Home Assistant (a very popular open source home automation system), and provides custom component interacts with AWS to get the month to date cost and forecast cost and make it available on Home Assistant. It adds two new entities 1/Month to date cost: The current cost of your AWS account, and 2/Forecasted month costs: The forecasted cost based in your current consumption. Check out Diego's post on LinkedIn that provides some more background to this project.

Nice!

For a home-rolled solution, I use a GE CYNC ST19 Edison Style bulb in a socket right outside my office door. I have it configured through Home Assistant (https://www.home-assistant.io/), and then use Hammerspoon (https://www.hammerspoon.org/) on my macbook to make an API call to Home Assistant when the camera state changes.

If my camera turns on/off, so does the light bulb. Works really well for letting my family know I'm busy in meetings.

Given these changes, I thought about reintroducing Homebridge. But upon researching, I discovered Home Assistant.