you can turn that check off under schematic setup -> pin conflict map.
Please don’t, this is here to help you. Having worked at a place where they set all pins to passive with a leading eCAD package simply because not all designers know how to use the program (resulting in board issues…), having such checks are worth their weight in copper!
use the powerflags, I quite like this concept in KiCad and it has saved me a number of times
I agree with that.
But I also understand the reasons for wanting to disable it. If you have several filters in your power supply going to different sections and/or work with net-ties or jumpers then the PWR_FLAG symbols quickly go in the direction of the bad side on the annoyance scale.
The PWR_FLAG also become more annoying if your schematic gets too crowded. (That creeps in, you may not have noticed it). Going to a hierarchical design over more sheets can remedy this.
Ouwch, silly me.
Just realized that it is not in the matrix at all. The matrix defines what sort of connections get flagged, but the “not driven by any pin” error/warning is triggered by something that is not there.
In itself I like the PWR_FLAG and the extra checks it enables, but it feels only partially implemented. Recently I read an idea about telling KiCad that some pins are shorted for ERC purposes (Filter inductors, jumpers, net-ties, 6x6mm push buttons, etc) but this is not implemented. In KiCad V5.99 there is a “rules based” DRC check, and maybe this can be done with a similar system for ERC.