Extended address of SED changed abruptly

[kaushalyasat]

Hi, 

I have seen the ExtAddr of a SED device changed abruptly. The SED was connected through a router before this happened. This is very rare, but this could be a catastrophic failure for us. What I want to know is

1. I am using 'otLinkGetExtendedAddress(openthread_get_default_instance())' to get the ExtAddr of the SED on the fly. Normally this is very consistent. Is it not the correct API?

2. Under what circumstances would/could the ExtAddr be changed in a SED?

3. Is 'otLinkGetFactoryAssignedIeeeEui64 ()' a better way to retrieve the hardcoded MAC?

Cheers,

Kaushalya

[Marte Myrvold]

Hi Kaushalya,

1. I am using 'otLinkGetExtendedAddress(openthread_get_default_instance())' to get the ExtAddr of the SED on the fly. Normally this is very consistent. Is it not the correct API?

You can use this to get the IEEE 802.15.4 extended address of the device.

2. Under what circumstances would/could the ExtAddr be changed in a SED?

The 802.15.4 extended address of the device should not change unless you manually change it or erase the network data of the device. Did the device reset right before the address change? It could be that you are not setting the extended address persistent, so it is changed upon reset.

3. Is 'otLinkGetFactoryAssignedIeeeEui64 ()' a better way to retrieve the hardcoded MAC?

This will give you the IEEE EUI-64, which is different from the extended address.

Best regards,
Marte