(feature) report audio source GPIO conflicts in web UI

[softhack007]

Is your feature request related to a problem? Please describe. It seems that often users do not notice that GPIO from sound settings are already in use. Examples:

• MCLK = 0 but GPIO 0 already configures as button 0
• SCK = 15 but GPIO15 alread in use as LED pin
• WS = 14 but gpio 14 in use for I2C
• SD=33 but GPIO33 already in use for potentiometer Etc etc.

Describe the solution you'd like I see several possibilities

• adopt the coloring feature from LED settings page
• when preparing info page content, check configured pins for pin owner. Show a "red box" in case that some GPIO are already in use.
• other ideas?

Describe alternatives you've considered Ther is already a message "not initialized - check GPIO config" but it appears that people do not understand what it means...

Additional context Luzer support 😉

[netmindz]

+1 for this. I got caught by the button Vs pin 0