When Banggood decided to “forget” about MS5611barometer in their version of AnyFC F7 flight controller, they not only did not mounted MS5611 on it. They also made usage of any external barometer on that board almost impossible to use.
Why? Long story short: all STM32 MultiWii derivatives are unable (yet) to lookup for I2C devices across different I2C buses. So, if we define barometer to be connected to I2C bus #4, firmware will look to barometers only on I2C bus #4. But, since many boards uses multiple I2C buses, this creates a problem: AnyFC F7 onboard (and missing) MS5611 is connected to I2C bus #4, but I2C bus available on JST connector in I2C bus #2.
While for Betaflight this is not a problem (BF pilots rather do not use barometer), it is a problem for INAV. AnyFC F7 target is unable to use any barometer if onboard MS5611 barometer is missing. OK, you can just solder one in place, but without hot air station and decent soldering skills this is not a good idea after all. This is why, until better solution is found, INAV will include ANYFCF7_EXTERNAL_BARO target. The only difference between ANYFCF7 and ANYFCF7_EXTERNAL_BARO is barometer support.
If you have MS5611 in place (soldered in or bought with one) or do not intend to use any baro, you should use ANYFCF7 target.
When you do not have onboard MS5611 and want to use external barometer (MS5611, BMP180/085 or BMP280) you should use ANYFCF7 and ANYFCF7_EXTERNAL_BARO target.
Until new official version of INAV is published, you might use this custom hex:
INAV_1.7.1_ANYFCF7_EXTERNAL_BARO.hex. It is based on INAV 1.7.1 and proven to detect external barometers via JST connector.