I have found an issue with the message count on Zigbee Details page
One device had 261 messages on 2025-02-12 13:54:03, but only 23 messages on 2025-02-16 18:53:22. No hub reboot in between, all other devices have equal or higher number of messages than they had before.
I noticed that the device's DNI (16 bit address) has changed, so could it be that the count is based on the DNI instead of the 64 bit fixed address?
Side note: It would be great if this page could keep the selected ordering after a reload, I always have to reorder after reloading.
I'd also like to understand better when the DNI can change, because the device mentioned above hasn't been repaired.
It is an XBee 3 device, and the DNI change has only caused the issue reported above, but I also have currently 5 XBee S2C on the mesh (they are incredible repeaters), and their DNIs sometimes change, but in this case the hub keeps pointing to the old DNI, so the messages sent after the change don't reach the device.
Questions
When can a device's DNI change, other than when being paired?
Isn't the coordinator the only responsible to assign new DNIs to devices?
If it is the coordinator responsibility, why in some cases it keeps pointing to the old DNI?
Is there a way for the driver to be notified about the DNI change?
1 sometimes it might get a new address when it rejoins the network
2 yes
3 it shouldn’t unless the device is no longer able to reach the hub, when the hub sees it again it will update the 16 bit address
4 no
I’m not sure what your need is to be notified about this, if you’re writing a standard device driver any 16 bit address changes are transparent
So a simple power cycle could cause a DNI change, right?
The problem then is that there was no power cycle, the device is on all the time, but the DNI changed, and the hub held at its record the old DNI.
This happens every other week with at least one of the 5 XBees S2C.
I won't pretend to know the details of Zigbee messaging, but I had 6 Xbees on my network(4 S2Cs & 2 Xbee3s) and although they are excellent repeaters, since removing them my network is much more reliable. They kept having their address changing creating havoc even tho I had them set to auto rejoin and not to change channels or look for alternate coordinators. I postulate that HE or Xbee have some features that are not working well together. Maybe Xbee is 100% stock and Mike was forced to make adjustments to gain stability or compatibility for a myriad of devices or unskilled users-like me.
I have 5 of each currently, the XBee3s are there for more than 2 years and they are very stable, but I'm not using them just as repeaters, they have sensors attached, specially mmWave and PIR.
The S2Cs were added 6 months ago and are the only ones showing the problem reported above.
