It is being worked. As to the depth and details they do not know yet what is causing this.
If possible to get a packet capture during the pairing that would be helpful. The only thing the engineer has discovered is that the switch is requesting a key, the hub doesn't respond, so the switch leaves the network.
We are still trying to figure out what is going on, but another capture with another hub might show something useful.
1 Like
Hmmmmm ok. Mine hasn't acted back up again since hard resetting it the other day. I'll look around the house and see if I have a spare 2531 stick laying around. I might have one in a drawer but I just can't recall, lol.
As @kkossev observed, this situation looks similar to the newer IKEA remotes failing to pair if not kept very close (2in/5cm) to the hub - to force them to choose the hub as their Zigbee parent. See my findings here:
After a successful pairing, the IKEA remotes work fine if they later migrate to another Zigbee parent (e.g.: are used far away from the hub).
1 Like
Interesting, I'll forward the info to the engineer. We are sending this to a silabs contact to help investigate it. The workaround mentioned by @d.ohlin is working though. @sky320 has been able to use it. Essentially you:
Pair the device like normal.
Right after the led flashes green (showing a successful pairing), you pull the airgap.
After waiting 15 or so seconds you push the airgap back in.
What we think is happening is that the step that would usually request a key and not get an answer is being skipped by pulling the airgap. After that unsuccessful key request is usually where the device would leave the network. Upon booting back up, the device is requesting a key and the hub is responding this time so it has fully joined.
3 Likes
Very good! I always love the "dumb luck" strategy by which I discovered this method LOL
4 Likes
