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

141–150 of 344 posts

Re: Xiaomi Home Integration for Home Assistant

#141

Post by mrj »

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…

What I wish I had known: HA is just a python program, it's pretty easy to run it manually.

After my Pi's sdcard died, I wanted to use an old laptop (more reliable with a built-in backup battery) so I followed the deployment recommendations and used the VM image. After that, for the first time I started having problems with HA not running - because VirtualBox would run only about a month before crashing. And I didn't like how much memory a VM locked up on the host.

The documentation makes it sound super complicated, but if you can make a venv and `pip install`, the setup is that easy. I tend to just run `hass` manually but there instructions for setting up supervised. I wish the documentation made this clearer, it really tries to scare people away from that method but running a whole VM is a lot of overhead for my pretty simple zwave-js setup.

Re: Xiaomi Home Integration for Home Assistant

#142

Post by re5i5tor »

ahaucnx wrote: post #94
jillyboel wrote: post #83

Earlier quoted context omitted.

Everything can fit in group 3, but manufacturers want to steal your data so they try to pretend otherwise.

Not all manufacturers. At AirGradient, all our air quality monitors can completely run local. Our official firmware is on GitHub and people could even flash their own (adjusted) version. We believe this is how IoT devices should be and are very vocal about it. So I think there are a few manufacturers that think different.

Nice! Will consider one when my Awair poops out.

Re: Xiaomi Home Integration for Home Assistant

#143

Post by re5i5tor »

wlesieutre wrote: post #114
dietr1ch wrote: post #61

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.

Slightly off topic but I just bought an inexpensive water leak monitor set and it uses LoRa — I’ve had range problems with other bands “Extremely Long Range: Powered by LoRa technology, the long-range low-power system offers the industry’s longest receiving range (1/4 mile). Areas such as basements and sheds connect up to 100 sensors to deliver product information smoothly.”

Re: Xiaomi Home Integration for Home Assistant

#144

Post by antsar »

sneak wrote: post #129
diggan wrote: post #40

Earlier quoted context omitted.

I think (some correct me) you can group most devices into the following categories: 1. Device requires internet for setup, and for usage 2. Device requires internet for setup, but after that don't need it anymore 3. Device can be fully setup without internet, and used without internet Personally I aim to be fully within 3 as much as I can, but some devices are really hard to find at a good price point that falls into…

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...

Re: Xiaomi Home Integration for Home Assistant

#145

Post by Havoc »

Fabricio20 wrote: post #135
Havoc wrote: post #65

Earlier quoted context omitted.

They sold bulbs under various brands. I’ve got some very old ones branded yeelight that work entirely offline with HA. Tried to rebuy got a different brand and they don’t work offline properly. Bit of a crapshoot These days I try to buy preflashed tasmota gear. Things like athom.tech

I got some of those Yeelight ones (gen 1/gray plastic and gen 2/white plastic!) but my experience has been really bad. Even if their app allows you to enable local mode it's laggy and just... stops working after a while, it also seems to break if it can't reach xiaomi servers (pihole). Wondering how you got yours to work, mine are just trash at this point and i've since switched to proper local devices.

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 --token FOOBAR info

miiocli device --ip 192.168.1.88 --token FOOBAR info

On iphone go to yeelight app, select the apps overall setting menu and enable lan control

Re: Xiaomi Home Integration for Home Assistant

#146

Post by 15155 »

mrj wrote: post #141
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…

What I wish I had known: HA is just a python program, it's pretty easy to run it manually. After my Pi's sdcard died, I wanted to use an old laptop (more reliable with a built-in backup battery) so I followed the deployment recommendations and used the VM image. After that, for the first time I started having problems with HA not running - because VirtualBox would run only about a month before crashing. And I didn't…

Just use Docker?

Re: Xiaomi Home Integration for Home Assistant

#147

Post by 15155 »

dingnuts wrote: post #36
michaelmior wrote: post #19

Earlier quoted context omitted.

In case anyone using a myQ opener comes across this, I feel the need to mention ratgdo which many have found to be a great inexpensive upgrade. https://ratcloud.llc/

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 :(

You only need to reconfigure 4-6 color-coded, low-voltage wires in exactly one spot (at the opener.) Clear picture instructions are provided.

If you're using Home Assistant at all, you are more than capable of installing this device.

The old MyQ HA integration was absolutely more difficult to configure and install.

Re: Xiaomi Home Integration for Home Assistant

#148

Post by mrj »

15155 wrote: post #146
mrj wrote: post #141

Earlier quoted context omitted.

What I wish I had known: HA is just a python program, it's pretty easy to run it manually. After my Pi's sdcard died, I wanted to use an old laptop (more reliable with a built-in backup battery) so I followed the deployment recommendations and used the VM image. After that, for the first time I started having problems with HA not running - because VirtualBox would run only about a month before crashing. And I didn't…

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.

Re: Xiaomi Home Integration for Home Assistant

#149

Post by diggan »

sedatk wrote: post #102
mavamaarten wrote: post #75

Earlier quoted context omitted.

I've actually done my migration the other way around. I started with zigbee2mqtt, saw that HA now offers ZHA and switched to that. It just works with all devices I own, so the end result is one less moving part I need to update so the choice was easy.

Yes, I see all the praises about Z2M, but don’t see any details how it’s better. ZHA works just fine for me?

For me, a lot more entities from each device was correctly detected out-of-the-box. I think the wide compatibility is the biggest reason why you'd go with it.

But if you only have Phillips and Ikea devices for example, probably won't be much difference with Z2M.

Re: Xiaomi Home Integration for Home Assistant

#150

Post by 15155 »

VTimofeenko wrote: post #23
Someone1234 wrote: post #9

I include this when considering buying something integrated. For example Philips Hue is overpriced, but their Home Assistant integration is top tier and ultra-reliable. Contrast that with myQ garage door openers (LiftMaster, Chamberlain and Craftsman) recently breaking Home Assistant support on purpose, to essentially replace it with nothing, and they're dead to me. So Xiaomi adding support, assuming it is reliable,…

I am looking to install a garage opener and due to meatspace constraints I will probably have to use jackshaft. Jackshafts are predominantly LiftMaster and Chamberlain => the smarts are myQ, which I don't want anywhere near my network. Genie jackshafts seem fine, but Genie's reputation is bad to the point where garage door companies may refuse to work on them. These motors also usually come with the ability to hook u…

Just use a LiftMaster/Chamberlain jackshaft opener, never connect it to any network install the ESP32-based ratgdo device into the wiring harness, be done with this issue.

Nothing else compares due to the digital integration. ratgdo uses the simple serial protocol that the opener button uses, so it has access to a lot of information.

Post reply on HN