Replies: 6 comments 4 replies
-
Anyone to help me on this, so I can contribute after with a full functional quirk for this. |
Beta Was this translation helpful? Give feedback.
-
Hi kfran78 thanks for the reply and yes it has helped me along some other discussions to setup what I describe above. |
Beta Was this translation helpful? Give feedback.
-
As you installed zha-toolkit, I suggest you do a scan_device. You'll get a list of all the properties with their values and attribute types. |
Beta Was this translation helpful? Give feedback.
-
When the request fails, the response indicates it's manufacturer specific, and it succeeds when it is not manufacturer specific. So the cluster attributes should not be accessed as manufacturer specific attributes. It seems that zigpy is adding the manufacturer specific request type because it was not in your parameters to zha-toolkit. There is some logic in zigpy adding the manufacturer attribute in some cases - when the attribute is known in the attributes table and listed as a manufacturer attribute, but I do not see why here. You can add a third value to the parameter definition but that should not change anything as the default is False.
Needs more info/debug. You can also use a more recent version of the zha_toolkit - I don't think it impacts the manufacturer attribute, but there will be a bit more information. |
Beta Was this translation helpful? Give feedback.
-
Ok I finally got it. It is actually quite simple (but I had a lot of things to learn as I'm completely new to zha and home assistant). You just have to override the read attribute function ensuring it didn't send a manufacturer code and the property _is_manuf_specific .
|
Beta Was this translation helpful? Give feedback.
-
I just have now to found how to have those attributes appearing in Home Assistant as proper entities (any hint will be welcome). |
Beta Was this translation helpful? Give feedback.
-
Hi all, I'm very new and try to define a custom cluster for reading the manufacturer specific attributes of the Zlinkee from Lixee (documented here : https://github.com/fairecasoimeme/Zlinky_TIC)
I'm using zha_toolkit in home assistant to test and query those attributes.
If I don't change the lixee.zlinky zhaquirk then I can read those attributes values with no issues, but as soon as I modify the quirk to replace the cluster (id: 0xFF66) I got a Status.UNSUPPORTED_ATTRIBUTE
Can someone tell me what I'm doing wrong ? I don't understand !
Many thanks
Here is the trace of the error
Here is the code of the modified quirk
Here is the stack trace when the cluster 0xFF66 is not replaced in the quirk
Beta Was this translation helpful? Give feedback.
All reactions