Cannot read /ssl folder - blocks SSL automated renewal setups #835
Description
Description of the issue
The add-on might benefit from mapping a second Home Assistant folder to its container. Currently data_path allows mapping a directory of choice as the container data directory, however a new ssl_path could allow a secondary mapping to be linked to a new /ssl/ folder in the container.
Why? Today, setting the Home Assistant standard /ssl/ folder for MQTT (cert/key parameters) and FrontEnd (ssl_cert/ssl_key), means Zigbee2MQTT cannot read the files as the folder is not mapped through. This makes automating certificates renewal, e.g. via Let's Encrypt add-on, in a centralized /ssl location, something that cannot be achieved with Zigbee2MQTT. Mosquitto, Ring, and other add-ons generally support that.
Tried already? Creating a symlink from /config/zibgee2mqtt/ssl to /ssl seemed a viable solution. Unfortunately the symlink seems to be ignored and the folder is missing. Copying files works - but it's manual.
Addon version
Edge
Zigbee2MQTT version 2.7.1-dev
commit: 1688a3b5
Frontend version 2.5.0
zigbee-herdsman-converters version 25.89.0
zigbee-herdsman version 8.0.1
Platform
Installation method Home Assistant OS
Core 2025.12.4
Supervisor 2025.12.3
Operating System 17.0.rc1
Frontend 20251203.3
Logs of the issue (if applicable)
[2025-12-23 14:04:21] debug: z2m: MQTT SSL/TLS: Path to client key = /ssl/privkey.pem
[2025-12-23 14:04:21] debug: z2m: MQTT SSL/TLS: Path to client certificate = /ssl/fullchain.pem
[2025-12-23 14:04:21] error: z2m: MQTT failed to connect, exiting... (ENOENT: no such file or directory, open '/ssl/privkey.pem')