Could you please share a screenshot of the icons as they currently show for the X1, T2, and D2? That’ll help us see exactly what’s displaying versus what’s expected, and whether this is a metadata mismatch on just those two devices.
Also, as a quick test in the meantime: you can manually set the icon yourself. Right-click (or long-press) the zone icon, then go to Zone Settings → Edit Zone Icon, and pick the correct one from there. Let us know if that option isn’t available or doesn’t stick for your X1 and T2, that would tell us something too.
Fourth image shows Lumin D2 icon image is included in icons grouping. The Lumin X1 and T2 icons are not included in their respective icon groups. Thank you for your support and help.
Thanks for the detailed screenshots, that’s exactly what we needed, and it confirms what’s happening.
Your logs show that all three LUMIN units connect and play perfectly; this is purely about the default zone icon. The important clue is that your X1 and T2 are on LUMIN’s newer firmware/hardware platform, while your D2 is on the older one. Roon assigns the default icon by matching what each device reports about itself against our device database, and it looks like the X1 and T2 on the current firmware are reporting an identifier we aren’t yet mapping to their proper icons, so they fall back to the generic speaker, and don’t appear in their own icon groups. The D2 still matches correctly, which is why it looks right. In other words, this is on our side to fix in the device database, not a problem with your network or your units.
I’m flagging this to the team that maintains those icon mappings so we can get the X1 and T2 recognized properly.
In the meantime, the manual override Vadim mentioned should get you looking right: long-press (or right-click) the zone → Zone Settings → Edit Zone Icon → pick the correct one. If you can let us know whether that setting sticks for the X1 and T2, that’s a useful confirmation for us too.
One quick question to help us pin it down: did the X1 and T2 recently install a firmware update around the time this started? That would line up with what we’re seeing.