Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Xiaomi Home Integration for Home Assistant

github.com

Post reply on HN
Print view View original

201–210 of 344 posts

Re: Xiaomi Home Integration for Home Assistant

#201

Post by NordSteve »

michaelmior wrote: post #109
dingnuts wrote: post #36

Earlier quoted context omitted.

It's inexpensive if you discount the cost of your education learning how to wire in something like that. There's an order of magnitude difference in project size between setting up the old MyQ integration with home assistant and learning how to use.. whatever that thing is. Sometimes I think clever and educated people forget what it's like to be less intelligent or educated. I want a solution I can download :(

That's a fair point, but it's still likely less expensive than replacing your existing opener if you include the cost of an electrician doing the wiring for you.

It's really not hard at all. It probably took 5 minutes to install, with most of the time futzing with the power cable routing so that it looked decent and didn't rub on sharp corners of the opener bracket.

Re: Xiaomi Home Integration for Home Assistant

#202

Post by XorNot »

IgorPartola wrote: post #188
mrj wrote: 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.

I've ditched all ARP, mDNS in my setup. Everything is static IP addresses: it vastly improved robustness against network glitches, which absolutely will happen to you.

If my router is unplugged or offline, everything with power can still communicate for example.

Re: Xiaomi Home Integration for Home Assistant

#203

Post by XorNot »

darknavi wrote: post #44

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/

Are preflashed Valetudo vacuums a thing? It would absolutely be worth it to me to buy setup and working units.

Re: Xiaomi Home Integration for Home Assistant

#204

Post by harry8 »

I've had a reasonable run with athom pre-flashed tasmota kit and HA.

https://www.aliexpress.com/store/5790427

Low effort, low maintenance, works good. mqtt & wifi, tasmota has everything you could want in a timer interface while still exposing switching etc to override it HA.

Re: Xiaomi Home Integration for Home Assistant

#205

Post by XorNot »

antsar wrote: post #144
sneak wrote: post #129

Earlier quoted context omitted.

Home Assistant itself falls into category 2, with some integrations/utilities in category 1. The amount of stuff it pulls from the mothership and GitHub is crazy. I wish it were local-only by default.

Yes. This is frustrating. Notable examples: Updating an ESPHome device config requires network to build/compile the image. [0] Viewing your Integrations page leaks a list of integrations you are using to "brands.home-assistant.io". [1] [0] https://community.home-assistant.io/t/esphome-completely-off... [1] https://community.home-assistant.io/t/wth-why-are-brand-icon...

Locally hosting platform IO is definitely on my to-do list but it is a problem which looks vast.

I have SQUID doing TLS MITM in front of it right now, but that doesn't get me really to "offline builds".

Re: Xiaomi Home Integration for Home Assistant

#206

Post by thedougd »

IgorPartola wrote: post #188
mrj wrote: 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.

Overlooked option for running these things in containers is macvlan networking. Just give it its own MAC address on the network. Works great and you don't have to compromise on isolation.

Re: Xiaomi Home Integration for Home Assistant

#207

Post by protocolture »

WaitWaitWha wrote: post #89

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…

I have the weirdest issues with HA. Like I can either make or find everything I need, except audio inputs and outputs which seem like some kind of horrifying netherworld of barely supported through config hacks.

Which wouldnt be an issue if their voice assistant stuff wasnt otherwise fantastic.

They seem to really rely on some kind of all in one third party device, but I havent found any that work for me.

Re: Xiaomi Home Integration for Home Assistant

#208

Post by demosthanos »

mrj wrote: post #148
15155 wrote: post #146

Earlier quoted context omitted.

Just use Docker?

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.

Can't do with docker or can't do as easily with docker as you can with HAOS? My understanding has been that everything can be done by just adding new containers or files, and it's worked for me thus far.

Re: Xiaomi Home Integration for Home Assistant

#209

Post by pnw »

noprocrasted wrote: post #196
int_19h wrote: post #134

Earlier quoted context omitted.

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.

https://www.home-assistant.io/yellow has the extra interfaces for Zigbee and Z-Wave - and the compute board is an Raspberry Pi 4 or 5.

Re: Xiaomi Home Integration for Home Assistant

#210

Post by briHass »

jakupovic wrote: post #186
mrandish wrote: post #178

Earlier quoted context omitted.

Tasmota runs on hundreds of different devices including switches, plugs, buttons, power strips, sensors, IR & RF gateways, etc. Tasmota homepage: https://tasmota.github.io/docs/ . There are over 2800 devices listed in this user maintained repository: https://templates.blakadder.com/ . Three years ago when I was choosing devices I initially ordered a Kasa switch to try but after a little research quickly realized I di…

Sir, take it from a random person on the internet, you're more than kind. Thank you so much for the details and bits of your own experience to make it relatable. Even though I have many Kasa switches I do want the option 3 that was raised earlier. Again, many thanks.

If they're the older Kasa bulbs/switches (before they got all Matter), they have a dead simple local, MAC-addressed TCP packet protocol. I've implemented basic ON/OFF commands in ESPHome C++ code, but there's also a command line tool: https://github.com/python-kasa/python-kasa?tab=readme-ov-fil... There's a list at the bottom of supported devices.

Last used the command-line utility with a PowerShell script to make the lights in the playroom do a rainbow-random color dance party for the kiddos. Was nice to crank out a working automation in 2 minutes.

Post reply on HN