I’m not yet sure that we’re understanding each other. Your FLARM will always receive another FLARM enabled aircraft’s ICAO ID. So, saying “…I know I’m seeing him as we communicate each other’s locations and the outside view tracks what I see on the instruments” is totally irrelevant to your problem as that is exactly the expected behavior. What is relevant is determining what your FLARM display will show you. Converting the ICAO number to a contest ID happens on the FLARM traffic display itself so your FlarmView and ClearNav both need a flarmnet file. FlarmView will require LxNav formatted 20210529.fln file and ClearNav will require the data.fln formatted file. The flarmnet file is a simple database with hundreds of entries that say ICAO number ABCDE=Contest ID XY. ICAO number ABCDF= contest ID YZ. Etc. You have previously stated that some aircraft show the proper contest ID on your FlarmView and other aircraft show only the ICAO number. The only way this is possible is for you to have some sort of working flarmnet file already residing on your FLARM displays. And, this is exactly the expected behavior when some aircraft are registered in in the flarmnet database and others aren’t.
So, there are a few scenarios that could explain the observed behavior:
A) Your friend isn’t registered on flarmnet. You’ve said he is so this one seems unlikely.
B) Your friend has accidentally registered the wrong ICAO number on flarmnet (One that's different than what they put into their FLARM)
C) Your friend has configured their FLARM with the incorrect ICAO ID (One that's different than what they put into flarmnet)
D) The flarmnet file on your display is older than the date on which your friend registered their ICAO and contest ID with flarmnet
Therefore, what I’m trying to convey is that if your friend is registered in flarmnet as one ICAO number, say ABCDE, but through a fat fingering of his FLARM config file has set his FLARM to transmit ICAO ABCED neither you nor anyone else will ever see his real contest ID. If others are seeing the same thing you are you’ve proven the issue is with your friend’s FLARM configuration or flarmnet registration. If others see the correct contest ID on their displays then you’ve proven the issue is with your system. It seems a bit unlikely to me that you would be having the exact same flarmnet file problem on 2 different displays, which is why I’m suggesting that it may make sense to start from square one and test some of the more obvious scenarios as outlined above.
Anyway, just in case it may be helpful, here is what I see when loading (or not) a new flarmnet file to my system. My FLARM is hooked up to a Butterfly display so my FLARM boot time messages are as shown below when I do and don’t load a new flarmnet.bfn file. Of course, your messages will be slightly different since you’re using a different brand of traffic display.
FLARM initialization *with* flarmnet.bfn file:
00040.647 INFO Looking for butterfly firmware file
00040.675 INFO Found butterfly firmware file: BFD_3_4.BFW
00040.699 INFO Looking for butterfly firmware file
00040.726 INFO Found butterfly firmware file: BFD_3_4.BFW
00040.730 INFO Looking for butterfly flarmnet file
00040.763 INFO Found butterfly flarmnet file: FLARMN~1.BFN
00150.857 INFO Allowing drivers to catch up...
00150.858 INFO Updated BF display firmware and flarmnet on Data Port #1
FLARM initialization *without* flarmnet.bfn file:
00010.353 INFO Looking for butterfly firmware file
00010.378 INFO No butterfly firmware file present
00010.378 INFO Looking for butterfly flarmnet file
00010.402 INFO No butterfly flarmnet file present
Hoping some of this turns out to be useful to you. Good luck.
Robert