Closed jBouyoud closed 5 years ago
No, I have removed the full attributes reading because it's almost unneeded. That's why it only try to read attribute 5 now it's not a bug
I see that you have just fix this issue (https://github.com/doudz/zigate/commit/e68817694981808e3a45d670e69d9889cc89ef80#diff-d508f2d159253fda151b62cd6971c50dR542 ) Thank You
Hello,
I recently update my zigate module to 0.25.1. And attributes auto-discorevy/reporting seems to be broken with device that doesn't have
type
(5
) attributes on General cluster (0
) which is unfortunalty the case for my device aProfalux cover
.You can see debug logs below :
I receive a
134 (0x86)
status code, according to this doc https://www.nxp.com/docs/en/user-guide/JN-UG-3115.pdf#page=156&zoom=100,0,221 , P154 Chapter 7.1.4E_ZCL_CMDS_UNSUPPORTED_ATTRIBUTE
, It seems to match.With an older version of zigate, I've got the following auto discovered attributes for
0
cluster.Also you can found other info about the device below :