![]() ![]() ![]() ![]() Zigbee uses mesh networking topology, which means that most mains-powered devices are a “Zigbee Router” that can act as signal repeater and range extended by transmitting data over long distances by passing data messages through the Zigbee network mesh of intermediate devices to reach more distant Zigbee devices. Most importantly is that you should add mains-powered “Zigbee Router” devices closer to the Zigbee Coordinator to extend the range and coverage before trying to add battery-powered devices further away from the Zigbee Coordinator, as that is a common mistake that can lead to a bad experience. It is not a god idea to begin by adding just a few battery-powered Zigbee devices to a new network. Start with just a device or two and see what you Highly recommend that you read and follow this guide before starting to build a new Zigbee network → You don’t have to move everything at once. Grab an inexpensive usb stick and start experimenting. I strongly suggest you just buy a Zigbee Coordinator USB adapter as they only cost about $20 and try with ZHA which is super easy to get started so should normally be up and running in just 1-minute, see: remote controls and keyfobs) you might also be interested you check out EPMatt’s Awesome HA Blueprints which includes a collection or Blueprints for controllers, see → Blueprints Overview | Awesome HA Blueprints and Controllers | Awesome HA Blueprints touch recommend check his GitHub repository to see if there are any known issues for your specific controllers → Other than searching the Blueprints Exchange when you got advanced/complex controller switches with multiple buttons (e.g. remote controls and keyfobs, like Philips Hue Dimmer Switch) will show up as a single device with multiple entities, and therefore it is usually a good idea to do a search in the Blueprints Exchange to see if there are Blueprints for any such advanced/complex which you then will also import/install to create a dummy device which organizes all its entities into something that is simpler to control in the UI, like for example this Blueprints → ZHA - Philips Hue Dimmer Switch (RWL020, RWL021) (search there for “ZHA” and/or model/brand of the product).Ĭontroller Blueprints will basically create a new more user-friendly virtual device that is nicer in the UI, and they have already done the work of mapping entities to device types such as switches, etc. For a simple relay “switch” without a built-in relay, such as the “Philips Hue Wall Switch Module”, will likely show up as a single device with probably only one entity for ON/OFF exposed, while a more advanced/complex switches with multiple buttons (e.g. In the world of Zigbee a “switch” can be either a basic single or dual-button ON/OF (like for example a smart wall-switch) or multi-button switches in remote control/fobs style also informally known as “controllers”). Not exactly sure what you mean by “switches” in this context as the words/terminology that Philips/Signify uses in this Philips Hue ecosystem app may or may not be the exactly same as the words/terminology that is used in the standard Zigbee specifications and in Home Assistant’s integrations or UI.įirst, understand that each separate physical device (like a smart-lightbulb or a smart-switch) always shows up in the ZHA (Zigbee Home Automation) integration as a single device with multiple entities, then it depends on each different device how many entities and which types of entities are exposed for that specific. How do the Hue switches integrate with ZHA? What kind of device do they show up as and how do the 4 buttons appear as? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |