Describe the issue you are experiencing

Description

When using the customize feature to load a custom /share/mosquitto/mosquitto.conf,
the file is loaded before /etc/mosquitto/mosquitto.conf. This means any settings
in the custom config (e.g. log_type) are overridden by the main config generated by
the add-on, making it impossible to control log verbosity via the customize folder.

Check the additional information section at the end for the impact.

Expected behavior

Custom config settings should take precedence over (or at least not be overridden by)
the generated main config.

Actual behavior

From the logs it is clear the custom config is loaded first:

1. Loading config file /share/mosquitto/mosquitto.conf
2. Config loaded from /etc/mosquitto/mosquitto.conf.

The main config is loaded second and overrides log_type.

Suggestion

Either load the custom config after the main config, or use include_dir at the
end of /etc/mosquitto/mosquitto.conf so custom settings win.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which app are you reporting an issue with?

Mosquitto broker

What is the version of the app?

2.0.22

Steps to reproduce the issue

1. Enable customize: active: true, folder: mosquitto in the add-on config
2. Create /share/mosquitto/mosquitto.conf with log_type warning
3. Restart the add-on
4. Observe logs — informational connect/disconnect messages still appear

System Health information

System Information

Anything in the Supervisor logs that might be useful for us?

Anything in the app logs that might be useful for us?

2026-04-03 11:20:50: Client <unknown> closed its connection.
2026-04-03 11:22:50: New connection from 172.30.32.2:40150 on port 1883.
2026-04-03 11:22:50: Client <unknown> closed its connection.
2026-04-03 11:24:50: New connection from 172.30.32.2:34934 on port 1883.
2026-04-03 11:24:50: Client <unknown> closed its connection.
2026-04-03 11:26:50: New connection from 172.30.32.2:36322 on port 1883.
2026-04-03 11:26:50: Client <unknown> closed its connection.
2026-04-03 11:28:50: New connection from 172.30.32.2:60914 on port 1883.
2026-04-03 11:28:50: Client <unknown> closed its connection.
2026-04-03 11:30:50: New connection from 172.30.32.2:43750 on port 1883.
2026-04-03 11:30:50: Client <unknown> closed its connection.
2026-04-03 11:32:50: New connection from 172.30.32.2:35246 on port 1883.
2026-04-03 11:32:50: Client <unknown> closed its connection.
2026-04-03 11:34:50: New connection from 172.30.32.2:59764 on port 1883.
2026-04-03 11:34:50: Client <unknown> closed its connection.

Additional information

Why this matters

The inability to control log verbosity has real hardware consequences for users
running HAOS on SD card-based devices (e.g. Raspberry Pi).

The Mosquitto add-on watchdog (watchdog: tcp://[HOST]:1883) probes port 1883
every ~2 minutes via a raw TCP connection. Since it never completes the MQTT
handshake, Mosquitto logs every probe as:

New connection from 172.30.32.2:PORT on port 1883.
Client <unknown> closed its connection.

This generates ~720 unnecessary log entries per day — caused entirely by the
add-on's own internal infrastructure. Users cannot suppress this noise because
the custom config's log_type setting gets overridden by the main config.

Excessive log writes accelerate SD card wear. For users on Raspberry Pi or
similar embedded hardware, this is not a cosmetic issue — it directly impacts
the lifespan of their storage medium.