Sorry Bogdan, I missed this. It's a known problem to do with SOTAwatch. SOTAwatch applies hard filtering to the association, region and summitref. This was to stop non-SOTA spots. This means SOTAwatch has to know of the summits or you cannot spot. Spotlite allowed a more relaxed view of what was a SOTA summit but it still needs to use a valid association.
With the (delayed) but imminent demise of SOTAwatch, the painful way new associations were added has been dropped. This means SOTAwatch is unaware of many new associations and FL/xxx will fail along with ZB2 or OY etc. I will ask Jon is something can be done.