this post was submitted on 18 Jun 2023
161 points (100.0% liked)
Technology
37720 readers
41 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Everything became very easy for me once I decided to go all open source. In my opinion, the problem is all of the different proprietary "hubs". I got a ZigBee controller that can control all ZigBee devices without requiring a hub (there are several options available).
Lights: ZigBee Hue. Plugs: ZigBee Innr. Motion sensors: ZigBee Aqara. Cameras: Ethernet Amcrest. NVR: Frigate.
Everything is local, no data leaves my network, and everything is controlled directly from Home Assistant dashboards via the ZigBee controller, and I never have to open any proprietary apps.
Care does need to be taken to plan the network at least somewhat in advance, but that doesn't take too long, and everything is very stable and super reliable.
What is the ZigBee controller? Is the Hue Bridge one? Does the Hue bridge not go on the internet?
No, I am currently using a TubesZB Ethernet controller, but before that I used a Deconz ConBee II. There are others available as well.
I used the hue bridge before setting up HA, but after setting up and configuring the other controller, you can unpair your hue bulbs from the hue bridge and pair them with the new controller instead. You can then unplug the hue bridge, because the new controller is now handling the hue bulbs.
This is possible because devices that comply with the ZigBee protocol specs must accept properly formatted commands from a hub/controller after a successful pairing.
So if you have one of these controllers, AND the ZigBee device you purchase is compliant with the protocol AND the device is supported by the controller, the controller will be able to control the device locally, and you can throw out the "required" hub from the manufacturer that sends your data to that company's servers. This is why you need to plan things out ahead of time, to ensure that what you get will work with what you have. Every controller has a list of what devices are supported. For example, here are the devices supported by the ConBee II, and here are the devices supported by the TubesZB device, which uses Zigbee2MQTT.
Bonus: with one of these controllers, your smart home stuff will now work just fine if your internet goes out. As long as your local network is up and running, all of your HA stuff will work as well.
Thanks for all this info. I'm just planning out what I will use. This gives me a lot to dig into!
Really glad to hear it! Feel free to ping me if you have questions.
Edit: The Deconz is a good starter device, but it doesn't support nearly as many devices as Z2M. I got an Aqara Pet Feeder that Deconz doesn't support, but Z2M does, which is why I switched. You can't use Z2M with the ConBee.
This is the video I used to set up Z2M to work with the new controller.