zbdongle-e router IEEE change not taken into account

[Outsidewall]

My zigbee mesh is about 140 devices.
I have uploaded into my zigbee dongle-e version 2024.6.2update7. (router)
I have attached to it via a serial console.
I have put the zigbee network into pairing.
It does seem that the new router will not pair? any ideas what is up with it?
Here is the output

NWK Steering stack status 0x1D
NWK Steering trying next network.
No beacons left on current mask. Moving to next state
NWK Steering State: Scan Primary Channels and Use Distributed Key
Examining beacon on channel 11 with panId 0x1A62
NWK Steering joining 0x1A62 on channel 11
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C7 cmd 02 payload[6B 6A 24 04 00 01 01 ]
T00000000:RX len 13, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq D6 cmd 02 payload[00 00 12 02 00 04 00 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C1 cmd 02 payload[00 CB 66 04 00 01 00 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
RX: ZDO, command 0x0013, status: 0x00
Device Announce: 0x7AFE
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C8 cmd 02 payload[6B 6B 24 04 00 01 01 ]
RX: ZDO, command 0x0013, status: 0x00
Device Announce: 0x3C84
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 13, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq D6 cmd 02 payload[00 00 12 02 00 04 00 00 01 01 ]
T00000000:RX len 7, ep 01, clus 0x0000 (Basic) FC 18 seq 41 cmd 0A payload[01 00 20 64 ]
RX: ZDO, command 0x8001, status: 0x00
RX: IEEE Address Response
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 8, ep 01, clus 0x0B04 (Unknown clus. [0x0B04]) FC 18 seq 89 cmd 0A payload[08 05 21 B5 02 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq CA cmd 02 payload[6B 64 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C1 cmd 02 payload[00 CB 66 04 00 01 00 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq CB cmd 02 payload[6B 65 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 8, ep 01, clus 0x0B04 (Unknown clus. [0x0B04]) FC 18 seq C9 cmd 0A payload[0B 05 29 00 00 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C1 cmd 02 payload[00 CB 66 04 00 01 00 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 13, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq D8 cmd 02 payload[00 06 14 02 00 04 00 00 00 04 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq CC cmd 02 payload[6B 64 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C1 cmd 02 payload[00 CB 66 04 00 01 00 ]
T00000000:RX len 13, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq D8 cmd 02 payload[00 06 14 02 00 04 00 00 00 04 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C1 cmd 02 payload[00 CB 66 04 00 01 00 ]
T00000000:RX len 13, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq D8 cmd 02 payload[00 06 14 02 00 04 00 00 00 04 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq CD cmd 02 payload[6B 64 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C1 cmd 02 payload[00 CB 66 04 00 01 00 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 8, ep 01, clus 0x0B04 (Unknown clus. [0x0B04]) FC 18 seq B4 cmd 0A payload[0B 05 21 67 00 ]
T00000000:RX len 13, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq D9 cmd 02 payload[00 06 15 02 00 04 00 00 00 07 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq 71 cmd 02 payload[00 FF 24 04 00 01 01 ]
T00000000:RX len 10, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq CE cmd 02 payload[6B 65 24 04 00 01 01 ]
T00000000:RX len 13, ep 01, clus 0xEF00 (Unknown clus. [0xEF00]) FC 09 seq C2 cmd 02 payload[00 CC 70 02 00 04 00 00 09 7B ]
SL_STATUS_NOT_JOINED

[Nerivec]

Do you have the debug logs from Z2M?

[Outsidewall]

It never paired, thus no logs (even in debug) in Z2M that relate to the pairing attempt.

[Nerivec]

If you haven't already, can you try clearing the NVM3 on the router? https://github.com/Nerivec/ember-zli/wiki/Bootloader#clear-nvm3

[Outsidewall]

I have tried a number of the gbl files, I have no idea what adapter I have other than zbdongle-e, can't find any mode etc numbers on it, nor the chips.

The error message has changed.

[Outsidewall]

I think I have worked it out. The zbdongle-e is a resued dongle, it used to be the cordinator, until I swapped it out fro slzb-06m, which i copied the ieee to. Thus the old dongle is has the original ieee address!
So I will have to change the ieee address on the dongle.

[Outsidewall]

Changed the ieee, Nope, did not work

Error: install code setup failed. Is an install code flashed onto the device?

[Outsidewall]

I'm wondering if the dongle is missing, what looks like the default 'key', found some documentation on the silabs site.
DEFAULT_INSTALL_CODE="83FED3407A939723A5C639B26916D505"

[Nerivec]

You have to flash the proper GBL for your adapter, otherwise, things can get really bad (brick). If you select the adapter properly in ember-zli, it should select the right file automatically.

Install codes are not needed, it's just one step in the pairing process, that fails since it's not used, it then tries the other methods.

If you have an IEEE clash, it definitely will create problems, make sure it is different from any other device in the network.

Do you have a close enough device to join the network? Only 1 beacon seems odd. If it's too far, it could be dropping off before it can join.

[Outsidewall]

I have come to the conclusion that the adapter I have, has had its ieee address changed, by me ages ago, and it seems although I have changed it to another unique address, it insists on using the original, seems the hardware only allows it to be changed once. which is in conflict with the current coordinator.
I pretty much spend all day investigating it, many flash/clear/change/google, and round again.

I have ordered a new zbdongle-e to carry out evaluation of the new router firmware.

I was hoping to reuse the old dongles.. shame, more ewaste.

[Nerivec]

The old IEEE change technique was only doable once, but not the new one.

Did you try the full APP clear as last resort? https://github.com/Nerivec/ember-zli/wiki/Bootloader#clear-app
Make sure you change the IEEE after flashing the new firmware.

[Outsidewall]

Hello, Yes I did carry that out, sadly did not seem to help, but not using the link you have given for the ieee change, I used the

which indicated it had changed it, the suddenly it was back to the default.

[Outsidewall]

OK, tried all the above,
So flashed it to 7.4 (ncp)
Changed ieee( using ember-zli)
Then flashed it back to sonoff_zbdonglee_zigbee_router_8.0.2.0_115200_sw_flow
It would not join the network, loads of output indicating something was up.
No joy, even 3ft away from the coordinator. In fact it looked like it was still on the old ieee, as it seemed to get incoming packets from the other devices, at the same time zigbee2mqtt was complaining about duplicate ids

[Nerivec]

Seems the IEEE change is not taken into account with the router firmware (only NCP).

I guess for now (would have to investigate this scenario better), you could re-use it, but you would have to re-pair your coordinator network (by changing back the IEEE on the smlight so it doesn't conflict anymore).

[Outsidewall]

The smlight will have to stay on the current ieee, I have around 140 devices that would have to be repaired. I should get another dongle-e in the coming week, will give that a try and get back to you.