Log mosquito avec des erreurs

Bonjour,

Mon problème

Mes log Mosquito ne sont pas très propres :

[13:18:55] INFO: SSL is not enabled ==> je ne l’ai pas encore configuré. Cela semble logique

2025-01-11 13:18:58: New connection from ::1:49850 on port 1883.
2025-01-11 13:18:58: Client <unknown> disconnected due to protocol error.

Pourquoi ne puis je pas utiliser IPv6 ? Ce n’est pas très grave. Sur mon LAN, j’ai assez d’adresse IPv4. Autant ne pas chercher à utiliser IPv6 si la connexion ne peut se faire Comment enlever cette requète ?

2025-01-11 13:18:59: New client connected from 172.30.33.3:55280 as mqttjs_44aeacc4 (p2, c1, k60, u'mqtt_adm')
2025-01-11 13:19:05: New client connected from 172.30.32.1:52947 as 2eRGyFN3Adno1XpWTFEs9l (p2, c1, k60, u'homeassistant').

Pourquoi ai je le user mqtt_adm et le user homeassistant qui se connecte sur mosquito ?
En principe, je devrais utiliser uniquement mqtt_adm. Comment trouver l’appel avec le user homeassistant ?

Merci pour votre aide

Ma configuration


[center]## System Information

version core-2025.1.2
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.1
os_name Linux
os_version 6.6.66-haos
arch aarch64
timezone Europe/Paris
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.2
Stage running
Available Repositories 1498
Downloaded Repositories 2
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.1
update_channel stable
supervisor_version supervisor-2024.12.3
agent_version 1.6.0
docker_version 27.2.0
disk_total 28.0 GB
disk_used 7.0 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board green
supervisor_api ok
version_api ok
installed_addons File editor (5.8.0), Zigbee2MQTT (2.0.0-2), Mosquitto broker (6.4.1), Terminal & SSH (9.16.0), Node-RED (19.0.0), Silicon Labs Flasher (0.3.2)
Dashboards
dashboards 5
resources 1
views 5
mode storage
Recorder
oldest_recorder_run 24 décembre 2024 à 08:59
current_recorder_run 11 janvier 2025 à 11:51
estimated_db_size 82.67 MiB
database_engine sqlite
database_version 3.47.1
[/center] ___

Mes logs


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
[13:18:55] 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)
s6-rc: info: service legacy-services successfully started
[13:18:57] INFO: Starting NGINX for authentication handling...
[13:18:58] INFO: Starting mosquitto MQTT broker...
2025-01-11 13:18:58: Warning: Mosquitto should not be run as root/administrator.
2025-01-11 13:18:58: mosquitto version 2.0.18 starting
2025-01-11 13:18:58: Config loaded from /etc/mosquitto/mosquitto.conf.
2025-01-11 13:18:58: Loading plugin: /usr/share/mosquitto/go-auth.so
2025-01-11 13:18:58: ├── Username/password checking enabled.
2025-01-11 13:18:58: ├── TLS-PSK checking enabled.
2025-01-11 13:18:58: └── Extended authentication not enabled.
2025-01-11 13:18:58: Opening ipv4 listen socket on port 1883.
2025-01-11 13:18:58: Opening ipv6 listen socket on port 1883.
2025-01-11 13:18:58: Opening websockets listen socket on port 1884.
2025-01-11 13:18:58: mosquitto version 2.0.18 running
2025-01-11 13:18:58: New connection from ::1:49850 on port 1883.
2025-01-11 13:18:58: Client <unknown> disconnected due to protocol error.
2025-01-11 13:18:59: New connection from 172.30.33.3:55280 on port 1883.
2025-01-11 13:18:59: New client connected from 172.30.33.3:55280 as mqttjs_44aeacc4 (p2, c1, k60, u'mqtt_adm').
[13:19:01] INFO: Successfully send discovery information to Home Assistant.
[13:19:03] INFO: Successfully send service information to the Supervisor.
2025-01-11 13:19:05: New connection from 172.30.32.1:52947 on port 1883.
2025-01-11 13:19:05: New client connected from 172.30.32.1:52947 as 2eRGyFN3Adno1XpWTFEs9l (p2, c1, k60, u'homeassistant').

Salut

Parce que au moins 2 clients différents viennent se connecter: z2M par exemple, avec le user mqtt_adm mais aussi HA … Et comme le brocker est la version addon, sans contre indication, il utilise le user interne HA (homeassistant)

Qui sont les 2 clients ?
J’ai Zigbee2MQTT => je viens de le mettre en user mqtt_adm

A priori, je n’ai pas d’autres clients (HA ?)

oui ha comme indiqué dans mon message. Sinon comment les infos sont lues :wink:

Bonsoir @renard,
utilise la balise texte préformaté quand tu colles du code dans un message, pour que ça soit lisible. Sinon ça pique aux yeux.
C’est l’icône image.
J’ai modifié ton sujet :wink: