Got a few NRF52832s from AliExpress. They all have the same UUID but different, non-changing MAC addresses. (I have not found a simple way to change UUID yet; suggestions welcome.)
Whatever Monitor configuration I make (I hope I haven't missed anything), even when not putting them in known devices and only looking at the MQTT topics that have MAC address as name, something like this happens:
One of the beacons is detected, Monitor marks the MQTT topics of the corresponding UUID and MAC address as home.
Another beacon is detected, MAC is marked as home, UUID not sure, maybe it is updated, but of course it was home already from the first beacon.
Now if one of them leaves, it is not detected as away. Its MAC address is not getting the away state.
Thus my assumption is that Monitor does not use the MAC address but uses the UUID internally as unique identifier, which in this case looks the wrong choice. (Not sure about all the technical details.)
Got a few NRF52832s from AliExpress. They all have the same UUID but different, non-changing MAC addresses. (I have not found a simple way to change UUID yet; suggestions welcome.)
Whatever Monitor configuration I make (I hope I haven't missed anything), even when not putting them in known devices and only looking at the MQTT topics that have MAC address as name, something like this happens:
One of the beacons is detected, Monitor marks the MQTT topics of the corresponding UUID and MAC address as home.
Another beacon is detected, MAC is marked as home, UUID not sure, maybe it is updated, but of course it was home already from the first beacon.
Now if one of them leaves, it is not detected as away. Its MAC address is not getting the away state.
Thus my assumption is that Monitor does not use the MAC address but uses the UUID internally as unique identifier, which in this case looks the wrong choice. (Not sure about all the technical details.)