I have noticed with my Peanut outlets and my Hampton Bay Fan Controllers, when the Zigbee discovery process finds more than one device, it names them all the same these days, usually the first device name. This seems to be true if I do multiple device discovery (60 second) clicks or if I actually catch all 4 fans in one discovery click.
Hubitat Elevation® Platform Version
2.1.1.122
Hardware Version
Rev C-4
Simple enough to deal with, but annoying.
Cheers!
Greg
I've noticed the same problem (on my C5 in both the latest macOS Firefox and iOS Safari). Definitely happens when adding multiple Zigbee devices at the same time for me; not sure if might be more widespread (though you're not supposed to add multiple Z-Wave devices at the same time, and LAN and virtual devices are different, so I guess this would probably be it). Forgot to report it, but your post reminded me. 
Thanks. I have 4 zigbee fans on 1 switch, so there's no avoiding it given how terrible the fan controllers seem to be. I'm considering hard wiring them on, but the remotes are similarly terrible and I can imagine going insane running to the breaker to reset them repeatedly. My next post will be about the fans I think.
I've seen it in Chrome on my Pixelbook, I could try others if someone thinks it's browser or OS specific caching or something.
Are you talking about the Hampton Bay/King of Fans fan controller, the ceiling- or canopy-mounted Zigbee module often advertised as compatible with Wink and ST? If so, there are several posts on this forum (and probably ST) if you search, but core of the issue seems to be that they have weak radios/antennas, and adding a repeater or two as close as you can (same room or maybe a story above if you have multiple levels) helps.
Yes, that's it. I've read most of the posts and tucked a Peanut Outlet within 4 ft of each of them as a result of reading all the posts and the ensuing legendary signal strength issues.
Just noticed this myself when I did my first multi-device discovery. The two Z-Wave+ switches it discovered both got the same name as the first entry.
Tracked this down, was a bit confused on what the actual issue was, since no one mentioned its the "Label" that was getting set by the first "Label" that was set, the name is being set by the pairing process / fingerprint and that is fine.
As always, it helps to get screenshots, browser and OS details to help track down exactly what's going on.
Appreciate reporting the issue.
Download the Hubitat app
