Live data from Hacker News

Xiaomi Home Integration for Home Assistant

github.com

191–200 of 344 posts

Re: Xiaomi Home Integration for Home Assistant

#191
post #157

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/

Yeah I almost installed it, ripped apart my vacuum, just to realize there are many different roborock S7 versions with different SoCs, and my variant wasn't supported. Also roborock doesn't even support scheduled cleaning without cloud :(

Yeah, I have a Roborock S7 MaxV I bought about two years ago and was hoping I could put open source firmware on it but after some searching I learned that Roborock makes a lot of similar but different flavors within a generation like S7 and they can be quite different. Unfortunately, it appears my MaxV flavor of the S7 isn't rootable.

For those interested: This Reddit post had more info https://www.reddit.com/r/Roborock/comments/vlvep2/roborock_s... and a sub-post there linked to this Defcon presentation on rooting Roborock vacs https://dontvacuum.me/talks/DEFCON29/DEFCON29-vacuum-robots.....

Re: Xiaomi Home Integration for Home Assistant

#192

If you are thinking of deploying Home Assistant (HA), let me give you a few tips that I should have known when started. HA environment is vast. There are myriads of options, features, and functions. There are some gotchas that can be costly down the road. All of the following are "for now, as you start out": Do not gyrate over which version of HA to run. Run the HAOS loaded on RasPi, or a dedicated machine. You can m…

Also a tip that will save you few days and save you few things from destroying in anger. If you have existing zwave integration in let say alarm.com hub you first need to remove the devices from the network. Resetting DOES NOT WORK. Enjoy!

Re: Xiaomi Home Integration for Home Assistant

#194
post #148

Earlier quoted context omitted.

There are a few things you can't do with docker (my case was an addon that I wanted). The install docs have a good grid of the differences.

I also don’t think Docker can do ARP network interrogation, though I could be wrong about that. Also not sure how it handles mDNS.

You can run in host network mode to avoid that.

Re: Xiaomi Home Integration for Home Assistant

#195
post #148

Earlier quoted context omitted.

There are a few things you can't do with docker (my case was an addon that I wanted). The install docs have a good grid of the differences.

I also don’t think Docker can do ARP network interrogation, though I could be wrong about that. Also not sure how it handles mDNS.

The benefit of docker for home assistant is the packaging of it, rather than isolation. You can always run a container with host network mode and privileged mode so that it can access everything it needs to the same as if it were running directly on the host.

Re: Xiaomi Home Integration for Home Assistant

#196

If you are thinking of deploying Home Assistant (HA), let me give you a few tips that I should have known when started. HA environment is vast. There are myriads of options, features, and functions. There are some gotchas that can be costly down the road. All of the following are "for now, as you start out": Do not gyrate over which version of HA to run. Run the HAOS loaded on RasPi, or a dedicated machine. You can m…

As far as hardware, you can just get https://www.home-assistant.io/green (plus https://www.home-assistant.io/connectzbt1/ if you need Zigbee and Matter).

I'd recommend a Raspberry Pi instead. Easier to source (you may even already have it!) and I can guarantee it will be supporter longer and better than whatever low-volume Chinese board they're using here. There is zero advantage to this box, it doesn't even include built-in interfaces for some of the more "exotic" protocols like Zigbee or Z-Wave so you still need dongles either way.

Re: Xiaomi Home Integration for Home Assistant

#197
post #145

Earlier quoted context omitted.

Zero lag. If they lose power they revert to cool white. All local. Checked home assistant and its direct integration (yeelight)...no mqtt. And looked up my old notes - copied in below though don't recall details of what I did. Suspect maybe I used the python stuff just to check that lan is enabled rather than editing ------ https://github.com/Squachen/micloud pip install micloud miiocli device --ip 192.168.1.88 --tok…

Just to confirm, you are using the Yeelight app for this setup? On android there's Yeelight Classic (red icon), Yeelight (purple icon), Yeelight Pro (black icon) and the Xiaomi Home one. I think some of my issue might have been that region lock thing that kept changing a few years back (someone mentioned in another parent here). I remember setting it up on the Yeelight (red) but it eventually had me switch to Xiaomi…

Both the red yeelight classic and green Xiaomi Home is showing as previously downloaded on my iphone. Afraid I don't know which (was years ago) but I'd try red first

...and that too feels on brand for Xiaomi...utter chaos on branding.

Re: Xiaomi Home Integration for Home Assistant

#198

Earlier quoted context omitted.

I'm not buying any device that's not 3, everything else turns into a brick as soon as there's some larger change. I have some older Google Speakers, and while they seemed to be 2, after being powered off for long enough they can't be set up again, not even with internet access since their firmware was also outdated and the app isn't able to set them up again.

That’s why I’m sticking to Zigbee as much as possible. The only place where there’s an internet connection is at the Home Assistant computer which has a Zigbee USB stick.

I settled on Zigbee for door, window and some motion sensors, stand-alone buttons and other devices that need to be battery powered but for everything that's built into a wall or perma-attached to an outlet (like light switches, dimmers and wall plugs) I use generic commodity hardware running open source Tasmota firmware. These devices are based on standard reference designs, made by multiple Shenzen manufacturers and dirt cheap via Amazon, eBay and AliExpress. They're mostly based on ESP-8266 or ESP-32 chips and communicate via wifi.

The reason I use wall-powered wifi devices alongside Zigbee is the Zigbee architecture was designed to enable tiny battery powered devices that can run for a year or more on a small battery. Zigbee does this really well but I didn't want to be changing batteries on nearly a hundred wall switches, plugs and sensors that are connected to 110V anyway or perma-installed in places where wall power was easy to supply. There are also many devices like ultra wide band motion sensors, RF bridge repeaters, etc that can't be battery powered for long periods.

This Wifi+Zigbee split architecture has worked flawlessly in both our primary residence and a vacation home but they are both large detached homes, well-covered by wifi mesh routers with wired backhaul and other 2.4Ghz wireless neighbors a hundred or more feet away from our outer walls. So it's important to test wireless range and environmental compatibility inside your specific wall construction and unique RF domain before settling on wireless standards and architecture and installing a bunch of devices. Also, I'll mention that it's always tempting to just use wireless backhaul because it's easy but I think a big reason my large, complex home automation installs have avoided issues with randomly varying latency and intermittent signal loss is that I put in extra effort to get gigabit wired backhaul to each wifi mesh node and wired a Zigbee node alongside each wifi node. This entailed getting creative, like using an old pre-existing coax cable run with a Docsis modem to one mesh node and powerline ethernet to another. I'm pretty sure that extra pain up front prevented a lot of niggling gremlin pain later.

Re: Xiaomi Home Integration for Home Assistant

#199
post #148

Earlier quoted context omitted.

There are a few things you can't do with docker (my case was an addon that I wanted). The install docs have a good grid of the differences.

I also don’t think Docker can do ARP network interrogation, though I could be wrong about that. Also not sure how it handles mDNS.

As an alternative to host network mode, you can give the container a dedicated IP on your network using the macvlan driver.

Re: Xiaomi Home Integration for Home Assistant

#200

low-end Chinese phones, including Xiaomi and Huawei, show ads on system apps like Settings and Contacts. soon, smart home appliances might also display or speak ads. there's nothing stopping these Chinese companies from doing so - both technologically and ethically. Xiaomi definitely should not lead the way in smart home automation.

> low-end Chinese phones, including Xiaomi and Huawei

Did you mean Oppo and Vivo?

Post reply on HN