Bindings whose `context` doesn't match the schema

[andrewfg]

Apropos openhab/openhab-core#5372 I just ran all of the existing bindings through a schema validation for the proposed new stricter XML Schema for the context field. The following are the addons that fail.

• org.openhab.binding.anel → config.xml → invalid context: port-send
• org.openhab.binding.broadlink → config.xml → invalid context; static-ip
• org.openhab.binding.broadlink → rm-config.xml → invalid context: static-ip
• org.openhab.binding.broadlink → rmpro-config.xml → invalid context: static-ip
• org.openhab.binding.emotiva → config.xml → invalid context: control-port
• org.openhab.binding.huesync → config.xml → invalid context: `` (empty string)
• org.openhab.binding.matter → config.xml → invalid context: qrcode
• org.openhab.binding.mqtt.fpp → config.xml → invalid context: name
• org.openhab.io.homekit → config.xml → invalid context: qrcode

=> So the question is shall we:

1. Add (any of) these to the allowed schema?
2. Open PRs to remove (any of) these from the respective bindings?

[jlaur]

@andrewfg - do you mean "context" rather than "category"?

[andrewfg]

"context" rather than "category"?

Yes. Sorry..