Avenir Next LT Pro (OTF) - Only shows two options.

One possible cause for such trouble: Font faces/styles of the same family (name) can still end up in different "font groups" (internal name of the concept).

The typical reason would be a switch of the font technology described by the font type. This happened at LT a few years ago, so when you purchased some of them earlier you end up with such a mix. I've also seen similar changes with newer revisions of fonts from other foundries.

For completeness sake, another possible reason (unlikely in your case) is triggered by different native names of the family as displayed in UIs with non-roman writing script. That's the theory, I haven't yet come across such a font.

I think font management can also get confused if you spread the different files of a family across multiple folders, but that could also be an observation where the actual problem was the type mixup.

You can't tell from the font family's display name, because there are multiple font types that cause the same (OTF) suffix. Same problem with the icon, if it is showing at all. In some of the dropdown widgets you should still have two entries for that name (including suffix), in your case the one with the two condensed, plus another one with the rest of them.

Beyond those two entries with the same name, you can also have a look at the font details in the Find-Replace dialog, more info section - e.g. version info, type details, or your operating system can tell more, or do you use Monotype cloud?

If you apply the various font faces in a test document, you can also produce a snippet and look at its XML with a text editor, it should have the same divide.

Or, maybe it is a completely different reason. Could you please share that test document? 😉

Glitches like this are often cured by clearing the InDesign caches (as opposed to resetting prefs).  You'll find direction at Reset InDesign Preferences and Other Troubleshooting  if you scroll down the page.

OP here, it also works as it should in Photoshop so I think it's an indesign issue. It happens in the both the beta and non-beta versions.