WXCJKG13LM badly paired/configured #3111
Comments
|
logs, we can see the binding process is not the same. |
|
on the cc2530 list of active endpoints is only 1 the other endpoints are created when the device communicates, ex: |
|
the thing I don't understand is why the device doesn't send any "report attributes", it sends ieee 802.15.4 data request (0x04) but they're not related to any device action as far as I recall. |
|
nope, nothing, I'll try to rebind on cc2652 with the database entry from cc2531, but there's definitely something wrong here |
|
@Koenkk any idea what could be wrong ? |
|
Looks that there are connectivity issues, please try pairing the device close to the coordinator. |
|
@Koenkk as you could have guessed, that's the first thing I've done, pairing 5cm from the coordinator, pairing 5cm from the coordinator with all routers turned off. it should be noted the cc2531 pairing doesn't work correctly, it only get one endpoint, wrong manufacturer id, but the device works as expected, it reports to the coordinator. with the cc2652, the pairing looks ok, but the device stop sending any report after the "configuring" I can't tell if the issue with my cc2652 is related to cc2652 irself or with my actual network/setup. |
|
Could you sniff the traffic when pairing the device with the CC2652R and controlling it? |
|
@Koenkk in what format would like it ? public text packet dump with private data removed/replaced or the pcap I would only share with you |
|
pcap |
|
@Koenkk would you mind sharing a mail address ? ;-) |
|
fixed by upgrading cc2652r firmware (20200312) |
Koenkk
added a commit
to Koenkk/zigbee-herdsman
that referenced
this issue
Mar 26, 2020
|
Great that this firmware fixed. I've also fixed the manufacturerID issue you mentioned in the mail. With the latest dev could you repair the device and confirm that this is fixed? |
|
@Koenkk yes, confirmed, the manufId is now also correct, closing it now, Thanks a lot ! |
|
Note I seem to have the exact same complaint right now, with an up-to-date ConBee II plugged into an R.Pi, shared over IP using ser2net (115200) , ethernet cable, to Z2M (latest as of sept 2023) addon in HA. Will try again with my SkyConnect later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zigbee2mqtt version 1.11.0-dev (commit #8e9729c)
I'm unable to use any of my WXCJKG13LM devices on my main z2m instance (cc2652 on rpi3)
The devices are paired and configured but the devices don't send any message (report attributes) to the coordinator.
Using the same z2m version on my notebook with a cc2531 the devices work correctly
looking at the database.db I can see the entry for the same opple sensor is not the same:
cc2652:
cc2531:
z2m commit #407d329 (cc2652), z2m commit #4d54e50 (cc2531), so same herdsman*
manufId (xioami on cc2652, eurotronic on cc2531) is not the same and endpoints are not the same
The text was updated successfully, but these errors were encountered: