That can happen when a device fails to pair properly and ends up with all zeros for the fingerprint. I’ve seen that happen for a number of reasons including not setting the device up with S2 security if it is supported.
It would help to know the fingerprints of these devices so we can point you in the right direction. I would suggest using the API Browser+ from @TAustin to verify the fingerprints.