Hi @KevinGeorge , I can confirm that the MXID is really not expected to change.
I also looked for bit errors between the 2 numbers (hex), but there are many differences:
18443010712F8E0E00
1844301021775C0F00
so I think the software started talking to a different OAK device on the same network, after it was ran again.
I can also find both these MXIDs in our factory calibration logs.
How is the application connecting to the device (DeviceInfo), is it based on the IP address? If this is the case and a DHCP server is present on the network, it could happen it may assign a previous IP address to a different device.