Accuracy can’t be trusted
The Thread topology view is especially problematic. It includes many devices that are not Thread devices, and the connection lines between devices are arbitrary, unlike the Eve app.
The protocol scanner is more a novelty than a useful diagnostic feature. It treats things as the same device while still showing two different manufacturers in the details.
Response from developer
Thanks for the specifics, this kind of feedback is more useful than a one-star with no explanation. On Device Layers: you're right. Thread, HomeKit, and mDNS each return their own manufacturer metadata and they don't always agree. Right now the view shows all of them. I'm working on a smarter merge that picks the most authoritative source per field instead of surfacing the conflict. On Thread topology: iOS doesn't expose actual mesh routing tables the way a dedicated Thread coordinator does. The connection lines are inferred from border router relationships, so they're approximations. Non-Thread devices appear because the view correlates across all protocol layers, that framing needs to be clearer in the UI. These are real limitations, not edge cases. For context: v2.5 that is upcoming adds SmartThings as a fifth protocol layer in Device Layers, improves cross-ecosystem device merging, and unifies device counts so the numbers are consistent across screens. The manufacturer conflict issue you flagged is on the list. If you're open to it, email me at anthony.harmond@smarthomelifellc.com, I'd like to know more about what you're seeing. Hope you stick around to see the improvements!