Replies: 3 comments 6 replies
-
|
This depends on the implementation of the Device. Sometime bindings are needed to get a device to send its status regularly, like Battery Level for example. If you unbind the endpoints of your device, you may have problems down the road. There maybe also binds which may just "copied" from another device which are not necessary, but this not be the norm. |
Beta Was this translation helpful? Give feedback.
-
|
Battery level is sent by "Reporting" tab in which I have few rows of configurations about all data that I want that device sends to Z2M periodically. So I would curious why 85% of my devices have an initial Bind to Coordinator row(s) if them seems works fine even if I manually Unbind all present lines... |
Beta Was this translation helpful? Give feedback.
-
|
A bind is required for some devices to be able to report its status. If you feel the urge to mess with your devices / zigbee2mqtt config, I am not going to stop you. But please don't ask for support here if your setup breaks afterward. I suggest you make yourself familiar with the z2m source code and workings, ZigBee Protocol and specific Implementation of device Firmware like Tuya. Then you maybe deduct if something like a bind is necessary or not and improve zigbee2mqtt like fixing device profiles. |
Beta Was this translation helpful? Give feedback.
-
|
Just to know: WHO is asking for help? I'm asking a legit question because who has decided to set an Initial binding to Coordinator for those devices that I own (45 in total) SEEMS to not have any knowledge too. So until I'm not asking for help about binding, please don't invent something that I've not said or done. |
Beta Was this translation helpful? Give feedback.
-
|
Its always the same: anyone asks anything - another one gives an detailed answer with the hint that samething could broke and the thread Starter dont like this... This is the one reason why skilled User dont want to help anymore... Just my 2cent |
Beta Was this translation helpful? Give feedback.
-
|
Nope. Specifically I'm not interested to change Binding informations, but after many tries ALL my devices seems works like normal even if I click ALL "Unbind" buttons. So the question is legit: why the Developer choosed to initially create that Bind if it seems useless for THOSE devices? 🤷♂️ |
Beta Was this translation helpful? Give feedback.
-
My observations that there are 2 kinds of devices:
There are also 2 kind of message types - reports and commands. Reports are used to report a status (e.g. temperature, or brightness change). Commands are used by controller type devices (switches, knobs) to perform an action on other device (e.g light), for example turn it on, or change a color. But if you consider a smart button, out of the box it does not have any specific recepient who it can send commands to. That is why the default converter binds its commands to the coordinator, so that coordinator can convert it to an action. |
Beta Was this translation helpful? Give feedback.
-
|
I've understood what you written, but my dubt remains the same. |
Beta Was this translation helpful? Give feedback.
-
|
I also have the same question that I am trying to clarify here (from a little bit different angle). Unfortunately I have not found any guidance like 'Smart switch shall behave this way, make these reports, and allow binding in this fashion". ZCL and ZLL specifications describe low level building blocks, but do not explain how this shall work all together. As I see different vendors treat specifications in their own way. For example a few devices I have:
|
Beta Was this translation helpful? Give feedback.
-
Why a new paired device is automatically Binded to Coordinator? What is its purpose?
I tried to Unbind all Device Clusters/Endpoints from Coordinator and that specific device seems works just normal....so I don't understand why some device has this automatic initial binding.....
Beta Was this translation helpful? Give feedback.
All reactions