Description:
Currently, every port published by a sub-container from an external integration automatically displays an « Open » link in the supervision block of the Configuration screen. This behavior was designed for cases where the port exposes a web interface (e.g., the Frigate UI): one click and the user accesses it.
The development of the OCPP integration (charging stations) revealed an unanticipated case: a published port not intended for a browser. The port exposes a WebSocket endpoint to which the charging stations connect. The « Open » link is then misleading, clicking on it leads to an error page.
Proposal: add an optional flag in the port declaration of the manifest (e.g., browsable: false) so that the integration can indicate that a port is not browsable. In this case, the front-end displays the assigned port in the supervision block but without a clickable link. Purely additive change to the manifest schema, current behavior preserved by default.
Context: field feedback from @Sescandell on the OCPP integration, see the topic WIP Electric Vehicle Charging Station OCPP Protocol.