I'm asking for help with configuring Mosquitto broker v6.5.2

Third party integrations
1

I’m trying to configure Mosquitto broker v6.5.2. in the logins field, I enter the created mqtt user into the configuration and get a response when I click save (Unknown error, see supervisor logs). if I go to devices and services → MQTT → reconfigure → and enter my username and password there, then everything stays the same. I apologize for my English, as I am writing through a translator.
logs:
s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/mosquitto.sh

[10:42:38] INFO: SSL is not enabled

cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun mosquitto (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[10:42:38] INFO: Starting NGINX for authentication handling…

s6-rc: info: service legacy-services successfully started

[10:42:39] INFO: Starting mosquitto MQTT broker…

1761363759: Error: Unable to open include_dir ‘/share/mosquitto’.

1761363759: Error found at /etc/mosquitto/mosquitto.conf:43.

[03:42:39] WARNING: Halt add-on

s6-rc: info: service legacy-services: stopping

[03:42:39] INFO: Service restart after closing

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped

s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/mosquitto.sh

[10:42:54] INFO: SSL is not enabled

cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun mosquitto (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[10:42:54] INFO: Starting NGINX for authentication handling…

s6-rc: info: service legacy-services successfully started

[10:42:55] INFO: Starting mosquitto MQTT broker…

1761363775: Error: Unable to open include_dir ‘/share/mosquitto’.

1761363775: Error found at /etc/mosquitto/mosquitto.conf:43.

[03:42:55] WARNING: Halt add-on

s6-rc: info: service legacy-services: stopping

[03:42:55] INFO: Service restart after closing

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped

2

Hello

So you see this screen and cannot add an entry?

image
image373×369 13.9 KB

You can also click the 3 dots for the extended menu to edit as YAML and use this format there

logins:
  - username: "!secret MQTT_Login"
    password: "!secret MQTT_Password"
  - username: "!secret MQTT_Explorer_usr"
    password: "!secret MQTT_Explorer_pw"

I use secrets but for beginners I suggest just clear text logins and passwords in the quotes.

3

dear “Sir_Goodenough”, of course I’ve already tried that. as I wrote earlier, I could only save the login and password like this: “devices and services → MQTT → reconfigure →” it does not give an error, but the mosquito broker does not connect either. The Home assistant had to be reinstalled. but nothing worked. I’m putting everything for the mosquito broker bundle → zigbee2 mqtt → sonoff zigbee 3.0 usb dongle plus. Since I live in Russia, I often turn off my electricity, and I think that’s why zigbee2mqtt stopped working for me. everything worked for 8 months without failures, everything is installed on rasberry pi5

1
1938×432 44 KB

server logs
2025-10-26 11:52:50.219 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons/core_mosquitto/options/validate request

2025-10-26 11:52:50.220 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons/core_mosquitto/options/validate -

2025-10-26 11:55:50.418 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /ingress/validate_session request 401, message=‘Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8’, url=‘http://172.30.32.2/ingress/validate_session’

2025-10-26 11:55:50.418 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /ingress/validate_session -
mosquito logs
s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/mosquitto.sh

[12:09:51] INFO: SSL is not enabled

cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun mosquitto (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[12:09:51] INFO: Starting NGINX for authentication handling…

s6-rc: info: service legacy-services successfully started

[12:09:52] INFO: Starting mosquitto MQTT broker…

1761455392: Error: Unable to open include_dir ‘/share/mosquitto’.

1761455392: Error found at /etc/mosquitto/mosquitto.conf:43.

[05:09:52] WARNING: Halt add-on

s6-rc: info: service legacy-services: stopping

[05:09:52] INFO: Service restart after closing

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped

4

Why not just use the default setup as per the docs it will then use your HA login details

logins: []
customize:
  active: false
  folder: mosquitto
certfile: fullchain.pem
keyfile: privkey.pem
require_certificate: false
5 
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
  active: false
  folder: mosquitto
debug: false

The

customize: active: true

, not sure what that does, but mine is false. I also have debug off but you might need that.
Also HA tries to use the mqtt login as Arh mentioned, use a different login if you are doing it in the config like this.

I get using the config with a different login, I was never able to get the add-on to use the default for the main login.

6

Thanks to everyone who doesn’t leave me in trouble. I left the default settings for mosquito broker.
here is my log.
s6-rc: info: service s6rc-oneshot-runner: starting

s6-rc: info: service s6rc-oneshot-runner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service fix-attrs successfully started

s6-rc: info: service legacy-cont-init: starting

cont-init: info: running /etc/cont-init.d/mosquitto.sh

[16:59:14] INFO: SSL is not enabled

cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0

cont-init: info: running /etc/cont-init.d/nginx.sh

cont-init: info: /etc/cont-init.d/nginx.sh exited 0

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service legacy-services: starting

services-up: info: copying legacy longrun mosquitto (no readiness notification)

services-up: info: copying legacy longrun nginx (no readiness notification)

[16:59:15] INFO: Starting NGINX for authentication handling…

s6-rc: info: service legacy-services successfully started

[16:59:15] INFO: Starting mosquitto MQTT broker…

2025-10-26 16:59:15: Warning: Mosquitto should not be run as root/administrator.

2025-10-26 16:59:15: mosquitto version 2.0.22 starting

2025-10-26 16:59:15: Config loaded from /etc/mosquitto/mosquitto.conf.

2025-10-26 16:59:15: Loading plugin: /usr/share/mosquitto/go-auth.so

2025-10-26 16:59:15: ├── Username/password checking enabled.

2025-10-26 16:59:15: ├── TLS-PSK checking enabled.

2025-10-26 16:59:15: └── Extended authentication not enabled.

2025-10-26 16:59:15: Opening ipv4 listen socket on port 1883.

2025-10-26 16:59:15: Opening ipv6 listen socket on port 1883.

2025-10-26 16:59:15: Opening websockets listen socket on port 1884.

2025-10-26 16:59:15: mosquitto version 2.0.22 running

2025-10-26 16:59:16: New connection from ::1:33962 on port 1883.

2025-10-26 16:59:16: Client disconnected due to protocol error.

[16:59:16] INFO: Successfully send discovery information to Home Assistant.

[16:59:17] INFO: Successfully send service information to the Supervisor.

2025-10-26 16:59:28: New connection from xxx.30.xx.1:52783 on port 1883.

2025-10-26 16:59:28: New client connected from xxx.30.xx.1:52783 as 1FUK4Z3h3kXVcqDUX8KTRX (p2, c1, k60, u’homeassistant’).

2025-10-26 16:59:28: Client 1FUK4Z3h3kXVcqDUX8KTRX disconnected.

2025-10-26 16:59:28: New connection from 172.30.32.1:58055 on port 1883.

2025-10-26 16:59:28: New client connected from 172.30.32.1:58055 as 6quLAPCPvlQMrmDIVah8tZ (p2, c1, k60, u’homeassistant’).

2025-10-26 16:59:34: New connection from xxx.30.xx.2:42246 on port 1883.

2025-10-26 16:59:34: Client closed its connection.

2025-10-26 17:01:34: New connection from xxx.30.xx.2:58052 on port 1883.

2025-10-26 17:01:34: Client closed its connection.

2025-10-26 17:03:34: New connection from xxx.30.xx.2:48956 on port 1883.

2025-10-26 17:03:34: Client closed its connection.

2025-10-26 17:05:34: New connection from xxx.30.xx.2:35706 on port 1883.

2025-10-26 17:05:34: Client closed its connection.

7

These are local IP addresses only available to you so no point in obscuring them if you post more logs…

So at this point, not sure exactly, so a host restart is probably in order and you might want to do a config check to make sure there isn’t something preventing the restart. I’m assuming the broker is on the HA host, so it will get rebooted as well.

8

as far as I understand zigbee2 mqtt is knocking on the mosquito broker? thanks for the help. I think you need to create a new zigbee2 mqtt theme? because there is a question about mosquito broker here?
2 logs 1 → mosquito broker. 2 → zigbee2mqtt
log mosquito broker:
2025-10-27 08:03:40: Client closed its connection.
2025-10-27 08:05:40: New connection from 172.30.32.2:36336 on port 1883.
2025-10-27 08:05:40: Client closed its connection.
2025-10-27 08:07:40: New connection from 172.30.32.2:44678 on port 1883.
2025-10-27 08:07:40: Client closed its connection.
2025-10-27 08:09:40: New connection from 172.30.32.2:54202 on port 1883.
2025-10-27 08:09:40: Client closed its connection.
log zigbee2mqtt:
[08:05:31] INFO: Preparing to start…
[08:05:31] INFO: Socat not enabled
[08:05:31] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[2025-10-27 08:07:04] info: z2m: Logging to console, file (filename: log.log)
[2025-10-27 08:07:04] info: z2m: Starting Zigbee2MQTT version 2.6.2 (commit #unknown)
[2025-10-27 08:07:04] info: z2m: Starting zigbee-herdsman (6.1.5)
[2025-10-27 08:07:04] info: zh:adapter:discovery: Matched adapter: {“path”:“/dev/ttyUSB0”,“manufacturer”:“Itead”,“serialNumber”:“fe5c89068a3aef11a0a8281455516304”,“pnpId”:“usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_fe5c89068a3aef11a0a8281455516304-if00-port0”,“vendorId”:“10c4”,“productId”:“ea60”} => ember: 4
[2025-10-27 08:07:05] info: zh:ember: Using default stack config.
[2025-10-27 08:07:05] info: zh:ember: ======== Ember Adapter Starting ========
[2025-10-27 08:07:05] info: zh:ember:ezsp: ======== EZSP starting ========
[2025-10-27 08:07:05] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-10-27 08:07:05] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-10-27 08:07:05] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Total frames: RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: DATA frames : RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: DATA bytes : RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Retry frames: RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: ACK frames : RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: CRC errors : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Comm errors : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Length < minimum: RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Length > maximum: RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Bad controls : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Bad lengths : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Out of buffers : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Retry dupes : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: Out of sequence : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: ACK timeouts : RX=0
[2025-10-27 08:07:05] info: zh:ember:uart:ash: ======== ASH stopped ========
[2025-10-27 08:07:05] error: zh:ember:uart:ash: Failed to init port with error Error: Error Resource temporarily unavailable Cannot lock port
[2025-10-27 08:07:05] error: z2m: Error while starting zigbee-herdsman
[2025-10-27 08:07:05] error: z2m: Failed to start zigbee-herdsman
[2025-10-27 08:07:05] error: z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions
[2025-10-27 08:07:05] error: z2m: Exiting…
[2025-10-27 08:07:05] error: z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:665:19)
at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1547:24)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
at Zigbee.start (/app/lib/zigbee.ts:67:27)
at Controller.start (/app/lib/controller.ts:101:13)
at start (/app/index.js:149:5)
[08:07:13] INFO: Preparing to start…
[08:07:15] INFO: Socat not enabled
[08:07:15] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/

9

Is it a Sonoff stick version 3 E or P,
I don’t know what is what, but search here one needs a firmware flash from factory, and there is the ember keyword to choose and another one. I can’t keep it straight, but these logs look like that kind of trouble.

10

I have a Sonoff Stick 3e, it has been updated, yes, I have ember specified, and everything has been working fine since March. The Stick practically does not heat up. It is installed via a 2m extension cord. and around the middle of October, everything abruptly stopped working. adon zigbee2 mqtt stopped responding and I could not log in.

1
11240×638 37.7 KB

11

2
2538×598 25.6 KB