Last capcode in message determined region

[joper112]

I note that since the merging of some control rooms (meldkamers), notifications are coming under different regions. This is because of the monitor code. This is often/always last in the message which makes the previously received capcodes that are, for example, in my case. Gelderland Midden are shown as Brandweer Noord oost Gelderland. Now I have already adjusted the monitor code of BON in the database. But also the GMS code of Gelderland Zuid, I now see when I filter on the region Gelderland midden.

Is there perhaps a solution for this. Often there are several capcodes in a message (with the fire reports) I think / notice that the last determines the region as written before.
I dont have issues for the ambulance or police.
I have the monitor codes in my ignore. But still they are picked up. Do you have an idea how I can prevent/solve this. To update the database, I always have to rebuild the package completely. Now that should be fine after a while. But I think several people may "suffer" from this. My python knowledge is a little more than beginner, but that's about it. If the ignore capcodes are banned everywhere. Then I think it would be solved for me. But that piece i don't fully understand.

Yaml:
ignore_text: "Test,test,TEST"
ignore_capcode: 000806240,000903200,123456789,987654321

Or do i need to use the format such as:
name: P2000 Lifeliners
icon: mdi:counter
capcode: "001420059,000923993,000923995,000320591"

So it would be:
ignore_text: "Test,test,TEST"
ignore_capcode: "000806240,000903200,123456789,987654321"

I dont know what i'm doing wrong to ingore the capcodes 000806240,000903200 complete.