Hi,
After performing a ZDO_BIND Request I get 0x84 as return status. Can't find the meaning of that status code anywhere.
What does it mean?
Also: I have ccs and opened the ZNP Project, where can I find the various status codes?
BR,
Luca Vetri
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
After performing a ZDO_BIND Request I get 0x84 as return status. Can't find the meaning of that status code anywhere.
What does it mean?
Also: I have ccs and opened the ZNP Project, where can I find the various status codes?
BR,
Luca Vetri
As soon as i can i will screenshot it from my terminal.
The value is in return of the ZDO_BIND Request.
Hi,
I have a Danfoss Thermostat which I run a Bind to it of the cluster 0x0201.
These are the informations ( as you can see the packet is constructed correctly)
BIND PACKET: fe
17
25 21
e0 74 <-- network address
9 c2 d9 e5 ff 5f d1 4c <-- Serial of the danfoss
1 <-- SrcEp
1 2 <-- Cluster
3 <-- Addressing Mode
fe 1b c3 24 0 4b 12 0 <-- Coordinator IEEE
1 <-- dstEp
16
Serial: 4c d1 5f ff e5 d9 c2 9 <--- Serial of the danfoss thermostat
coordinatorIeee: 0 12 4b 0 24 c3 1b fe <--- serial of the dongle.
Is pretty interesting to note that even if i write all zeroes in the coordinator ieee i get the same status 0x84.
I don't really know what could be the problem.
I can't setup a sniffer unfortunately.
Is good to note that the firmware on the dongle is compiled from the ZNP Project of the SDK 6.0, changed Network Timeout Value.
With the Zigbee2MQTT Firmware it works. Now how can a change in SysCfg lead to this?
You can try to set breakpoint in MT_ZdoBindRequest to debug why it returns 0x84 in your ZNP project.
How do i do it? I flash the firmware on the sonoff dongle using flash programmer 2 and then communicate with it using Java
You should use CCS debug function to download and connect ZNP to debug. I would suggest you to use Ztool as host when you debug ZNP.
The CC2562P is connected via CP21xx Silicon Labs Bridge so Z-Tool Won't work.
0x84 can also mean ZDP_NOT_SUPPORTED as a ZDO Status Value defined in zd_profile.h, and it means that an optional feature is not supported. Either the Bind Request parameters are not valid or the destination node does not support the bind being requested.
Regards,
Ryan
I don't really know myself, but ZTool connects to CC2531EMK but not my SonOff Dongle.
What is very curious is that when I'm joining the valve the first time the bind goes successful, but aftewards it doesn't work anymore. Which means that the Parameters and the node are correct and support the Bind Request. I also checked the structure of the packet and everything seems okay.
Well, my boss forces me to use this one and honestly is better than the competition.
If the bind has already been created once then why is another Bind Request being attempted? The valve likely needs a factory reset or else it does not support multiple binds on the same endpoint/cluster.
Regards,
Ryan
It is pretty interesting to note that when joining the first time i can send as many bind request i want without them to fail, but once i unplug the dongle and connect it once again, restart the network via BDB Commissioning (Network Steering) the bind request raises me the error 0x84. Maybe after the reset the valve doesn't allow any more rebind.
You should factory reset the valve or attempt a ZDO_UNBIND_REQ before re-binding. If all bind information is the same (i.e. source/destination IEEE addresses and endpoints have not changed) then the bind may still be valid and re-binding would be unnecessary, hence the error.
Regards,
Ryan