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

331–340 of 344 posts

Re: Xiaomi Home Integration for Home Assistant

#331

Post by grahamj »

euroderf wrote: post #260
grahamj wrote: post #241

Earlier quoted context omitted.

yeah I f'ing love HA, it's my favourite hobby. But as it turns out I'm a programmer so I guess it fits :D HA is only good for normies if there's a techie setting it up and keeping it running.

I have an Apple HomePod Mini (with Matter support), and HA with Homebridge, and every now and then I see evidence in HA of tighter integration. Not sure where it might all end up tho. I'm keeping my fingers crossed that some day it will magically become self-aware and make everything "just work".

You probably don't need Homebridge if you run HA. You can expose whatever you like from HA to HomeKit so it works great with Apple devices.

Re: Xiaomi Home Integration for Home Assistant

#332

Post by ssl-3 »

azinman2 wrote: post #325
ssl-3 wrote: post #324

Earlier quoted context omitted.

Certainly not Chamberlain. Chamberlain's system is cloud-based. Strictly speaking, it doesn't work on LANs -- that's not one of its functions.

Exactly. So what alternative are you getting instead?

Ah, sorry. I may have misinterpreted your question.

I've only had a garage worth having motorization for a short time. It isn't something I've thought a ton about: While I do have this garage, and it would be nice to be able to park a car in there on a daily basis, and having it be motorized (and automated!) would be great, it's still full of the detritus from moving. Having the door go up and down by itself is pretty low on the list right now and will probably remain that way until the weather gets warmer and drier. :)

When I have thought about it, I've thought that building something myself would be adequate; that I'd just pick any dumb opener that has open/closed IO exposed, and graft on the connectivity functions I need with an ESP32 and some relays, using ESPHome.

Or maybe Shelly modules: One variation or another might have enough IO built in to do it, and they're packaged neatly, priced right, and the default software integrates well with Home Assistant. (They've also got ESP32s inside and can run ESPHome if one is so-inclined.)

Seems easy enough to me, and I've certainly done much more daunting and elaborate integration stuff at $dayjob.

But I don't know of a competitive "just-works" LAN-controllable garage door opener.

If it weren't for the SNAFU a year or so ago[0], I'd probably pick Chamberlain and a Ratdgo[1] board for local network control. But as it stands, I do not want to reward Chamberlain with any of my dollars, and I'm willing to go to any expense in order to avoid doing so.

[0]: https://www.home-assistant.io/blog/2023/11/06/removal-of-myq...

[1]: https://paulwieland.github.io/ratgdo/

Re: Xiaomi Home Integration for Home Assistant

#333

Post by Croftengea »

cassianoleal wrote: post #330
Croftengea wrote: post #110

Earlier quoted context omitted.

> At this point the hardware side of things was fine but my Zigbee network was gone. How come the hardware was ok but the network was gone? Did some Z2M config files go wrong because of two dongles? Did you try to restore VM from snapshots? Losing the network and having to re-pair everything would be a nightmare for me given the number of Zigbee devices I run (~35) and that some of them are mounted in switch boxes in…

Honestly, I don't think I can answer your question. I didn't change the config but I had to delete and re-pair all devices (or they had been gone from Z2M already at this point, I can't remember - it's mostly an academic distinction though).

Thanks anyway :)

Re: Xiaomi Home Integration for Home Assistant

#334

Post by jillyboel »

nomel wrote: post #320
jillyboel wrote: post #253

Earlier quoted context omitted.

Sure, nothing is stopping them from offering both.

The fact that the engineering effort would be diverted to something that targets a small fraction of a percent of their customer base is a perfectly valid reason to not do it, especially when that engineering effort could be put towards making the product better for the other 99.x% of their customers.

Except it almost guarantees the product will become useless in a few years, which makes it worthless now.

Re: Xiaomi Home Integration for Home Assistant

#335

Post by c0wb0yc0d3r »

shepherdjerred wrote: post #313
c0wb0yc0d3r wrote: post #308

Earlier quoted context omitted.

I assume then, you don’t use HAOS? What benefit do you see by managing your config this way? Do you also have an operator to reload HA when when you update configs?

It’s mostly a fun way to learn Kubernetes for me. I don’t have an operator.

I hear ya! For awhile earlier this year I was playing around with using k8s as a router, but trying to firewall it properly was a headache.

Re: Xiaomi Home Integration for Home Assistant

#336

Post by epcoa »

greggsy wrote: post #274
epcoa wrote: post #218

Earlier quoted context omitted.

HAOS uses docker to containerize everything, so it can’t be that difficult, and it really is not. Docker has a —-device flag for this purpose, udev makes it easy enough to assign stable names.

Trust me it's not worth the effort to get USB passthrough for HAOS on Docker.

What do you mean by “HAOS on docker”. HAOS is a standalone complete Linux system with its own fully managed kernel, not meant to be containerized. It uses docker internally itself though and “pass through” works transparently.

If you’re talking about running home assistant in a docker container, sure you’re more on your own, but since official home assistant in HAOS must run in docker, none of this is terribly difficult to configure.

The dongles are usually exposed as tty devices and I’ve been running zigbee2mqtt and Zwavejs addons in docker containers for years with no issue. HAOS takes care of stable naming (based on default udev rules) out of the box.

Unlike system virtualization, there isn’t really anything that needs passing through, it’s a naming and permissions issue - the container just needs an appropriately permissioned dev node ideally with a stable name. If you are using official addons it is effectively zero-config, and if you’re not, sorry but I don’t find the configuration to ensure a dev node to be anything but straightforward container config.

As someone else mentioned it may be as simple as:

  devices:
      - /dev/ttyUSB0:/dev/ttyUSB0
But you can just as easily use the /dev/serial tree to have stable names. Those names come out of the box with udev. You can always make your own too, I’ve done it, it’s not hard.

Re: Xiaomi Home Integration for Home Assistant

#337

Post by WaitWaitWha »

s2l wrote: post #225
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…

Can you share some of the zigbee devices that you are using? Thanks.

Happy to, but caveat emptor, your mileage may vary, and so on. The following is for a North American site I was just in.

The things that are battery operated, no big deal. The things that are full power, make sure they are UL, CSA, CE, AS/NCS, JIS, IS, and such listed. The cheaper the device the more likely to have quality shortcuts. Last thing we need is things to catch on fire unnecessarily.

Aqara Smart Plug

Linkind PIR Motion Sensor

Linkind Door Window Sensor

Seedan Zigbee Smart Light Bulbs

Seedan Zigbee Smart Plug

Sonoff SNZB-01 Zigbee Wireless Switch

eWeLink SNZB-03 ZigBee Motion Sensor

IKEA STYRBAR remote control

TRADFRI motion sensor

Some Zigbee devices go to sleep (e.g., STYRBAR) and disappear from the list or show unavailable. Once acted on, they would come to life and perform as expected.

Re: Xiaomi Home Integration for Home Assistant

#338

Post by X-Istence »

grahamj wrote: post #239
X-Istence wrote: post #97

Earlier quoted context omitted.

Hue bulbs currently are stock standard Zigbee compatible light bulbs. You can pay them into ZHA/Z2M without any issues and control them without any Hue hub or app. If Hue were to suddenly switch to something proprietary their existing bulbs will all continue to function without their app or hub.

The bulbs are ok but I tried moving my Hue motion sensors over to my main Zigbee network and they were terrible, constantly dropping offline and needing reset. Luckily Hue is made by Philips who I'm pretty sure aren't going anywhere.

I moved my Hue sensors to my primary Zigbee network and left the bulbs on the hub, especially since I have some of the gradient strips that don't work unless they are on the Hue hub, and my motion sensors have been rock solid.

Re: Xiaomi Home Integration for Home Assistant

#340

Post by majkinetor »

mrandish wrote: post #178
jakupovic wrote: post #152

Earlier quoted context omitted.

Hi, I'm using Kasa switches and not sure they can be flashed? Can you provide couple links with the switch and the firmware you used. Thanks

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…

Fantastic info. Never heard about tasmota before, but it looks like a right thing to do.
Post reply on HN