Mon problème
bonjour, j’avais pu appairer tous mes appareils mais ils restaient indisponibles dans HA 
voici ce que le journal de zigbee2mqtt donne :
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] socat.sh: executing...
[19:10:04] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing...
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[19:10:06] INFO: Handing over control to Zigbee2mqtt Core ...
> zigbee2mqtt@1.25.0-dev start
> node index.js
CREATED DECONZ ADAPTER
Zigbee2MQTT:warn 2022-04-19 19:14:59: zigbee-herdsman-converters:TM081: NOT RECOGNIZED DP #101 with data {"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,1,104]}}
Zigbee2MQTT:warn 2022-04-19 19:15:05: zigbee-herdsman-converters:TM081: NOT RECOGNIZED DP #101 with data {"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,58]}}
Zigbee2MQTT:warn 2022-04-19 19:25:01: zigbee-herdsman-converters:TM081: NOT RECOGNIZED DP #101 with data {"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,2,86]}}
Zigbee2MQTT:warn 2022-04-19 19:25:03: zigbee-herdsman-converters:TM081: NOT RECOGNIZED DP #101 with data {"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,0,93]}}
Zigbee2MQTT:warn 2022-04-19 19:34:58: zigbee-herdsman-converters:TM081: NOT RECOGNIZED DP #101 with data {"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,3,34]}}
Zigbee2MQTT:warn 2022-04-19 19:35:03: zigbee-herdsman-converters:TM081: NOT RECOGNIZED DP #101 with data {"dp":101,"datatype":2,"data":{"type":"Buffer","data":[0,0,1,86]}}
heuuu je devine qu’il y a un problème mais je ne sais pas quoi faire 
pouvez-vous m’aider?
Ma configuration
System Health
| version |
core-2022.4.5 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| user |
root |
| virtualenv |
false |
| python_version |
3.9.9 |
| os_name |
Linux |
| os_version |
5.10.103-v8 |
| arch |
aarch64 |
| timezone |
Europe/Brussels |
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 7.6 |
| update_channel |
stable |
| supervisor_version |
supervisor-2022.04.0 |
| docker_version |
20.10.9 |
| disk_total |
457.7 GB |
| disk_used |
3.2 GB |
| healthy |
true |
| supported |
true |
| board |
rpi4-64 |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
File editor (5.3.3), Mosquitto broker (6.0.1), Zigbee2mqtt Edge (edge), Samba Backup (5.0.0), Node-RED (11.1.1), Duck DNS (1.14.0) |
Dashboards
| dashboards |
1 |
| resources |
0 |
| views |
1 |
| mode |
storage |
est-ce possible que c’est depuis l’installation de Duck DNS pour un accès distant de Home Assistant?
car le journal de mosquitto broker à drôlement changer avec des erreurs
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] mosquitto.sh: executing...
[19:07:00] INFO: Certificates found: SSL is available
[cont-init.d] mosquitto.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[19:07:00] INFO: Starting NGINX for authentication handling...
[19:07:01] INFO: Starting mosquitto MQTT broker...
1650388021: mosquitto version 1.6.12 starting
1650388021: |-- *** auth-plug: startup
1650388021: Config loaded from /etc/mosquitto/mosquitto.conf.
1650388021: Loading plugin: /usr/share/mosquitto/auth-plug.so
1650388021: ├── Username/password checking enabled.
1650388021: ├── TLS-PSK checking enabled.
1650388021: └── Extended authentication not enabled.
1650388021: Opening ipv4 listen socket on port 1883.
1650388021: Opening ipv6 listen socket on port 1883.
1650388021: Opening websockets listen socket on port 1884.
1650388021: Opening ipv4 listen socket on port 8883.
1650388021: Opening ipv6 listen socket on port 8883.
1650388021: Opening websockets listen socket on port 8884.
1650388021: Warning: Mosquitto should not be run as root/administrator.
1650388021: mosquitto version 1.6.12 running
1650388021: New connection from 172.30.33.2 on port 1883.
1650388021: New connection from 127.0.0.1 on port 1883.
{"result": "ok", "data": {}}1650388021: New client connected from 172.30.33.2 as mqttjs_5dc8a439 (p2, c1, k60, u'mqtt_user').
[19:07:02] INFO: Successfully send discovery information to Home Assistant.
[19:07:02] INFO: Successfully send service information to the Supervisor.
1650388021: Socket error on client <unknown>, disconnecting.
1650388074: New connection from 172.30.32.1 on port 1883.
401: Unauthorized1650388075: Socket error on client <unknown>, disconnecting.
1650388195: New connection from 172.30.32.1 on port 1883.
1650388195: Socket error on client <unknown>, disconnecting.
1650388199: Client mqttjs_5dc8a439 disconnected.
1650388215: New connection from 172.30.33.2 on port 1883.
1650388215: New client connected from 172.30.33.2 as mqttjs_8e687600 (p2, c1, k60, u'mqtt_user').
1650388315: New connection from 172.30.32.1 on port 1883.
1650388315: Socket error on client <unknown>, disconnecting.
1650388435: New connection from 172.30.32.1 on port 1883.
401: Unauthorized1650388436: Socket error on client <unknown>, disconnecting.
1650388556: New connection from 172.30.32.1 on port 1883.
1650388556: Socket error on client <unknown>, disconnecting.
1650388676: New connection from 172.30.32.1 on port 1883.
1650388676: Socket error on client <unknown>, disconnecting.
1650388796: New connection from 172.30.32.1 on port 1883.
401: Unauthorized1650388796: Socket error on client <unknown>, disconnecting.
1650388916: New connection from 172.30.32.1 on port 1883.
1650388916: Socket error on client <unknown>, disconnecting.
1650389036: New connection from 172.30.32.1 on port 1883.
1650389036: Socket error on client <unknown>, disconnecting.
1650389156: New connection from 172.30.32.1 on port 1883.
401: Unauthorized1650389157: Socket error on client <unknown>, disconnecting.
1650389277: New connection from 172.30.32.1 on port 1883.
1650389277: Socket error on client <unknown>, disconnecting.
1650389397: New connection from 172.30.32.1 on port 1883.
1650389397: Socket error on client <unknown>, disconnecting.
Nom de domaine et config mosquito c’est sans rapport. Mosquito passe forcement par l’adresse interne (et c’est pas le même port)
test
ok Pulpy j’ai continué à chercher, essayé plusieurs choses et en réinstallant Mqtt il m’a découvert mais 7 appareils.
et j’ai pu configurer les entités manquantes.
Mais j’ai toujours ça dans le journal de Mqtt:
401: Unauthorized1650407187: Socket error on client , disconnecting.
1650407307: New connection from 172.30.32.1 on port 1883.
1650407307: Socket error on client , disconnecting.
1650407427: New connection from 172.30.32.1 on port 1883.
1650407427: Socket error on client , disconnecting.
1650407448: New connection from 172.30.32.1 on port 1883.
A ce sujet j’ai vu cela :
bon cela date de juin 2021 alors je ne sais pas quoi en penser.
Ça ressemble à un ‹ client id › mqtt qui n’est pas unique :
Le client 1 se connecte.
Le client 2 arrive, ça déconnecte le 1.
Le client 1 revient, ça déconnecte le 2.
Etc…
D’autres trucs que zigbee2mqtt qui utilisent mqtt ?
@Pulpy-Luke, t’es sûr 
, j’ai plutôt l’impression que le même client essaie de se reconnecter plusieurs fois.
Les nouvelles connexions viennent de la même IP : 172.30.32.2.
bon j’y comprends rien. 
j’ai maintenant ça pour le journal de mosquitto broker :
j’ai seulement installé une mise à jour « Core » et installé ESPhome pour une camera
je crois que je vais attendre quelques jours et voir si c’est toujours ok.
je vous tiens au courant.
Merci de votre patience.
oups j’avais oublié de te répondre Pulpy :
je ne pense pas. Dans Node Red j’appelle les services uniquement via Home Assistant. ESPhome je ne crois pas que ça passe par MQTT et ni Duck DNS j’ai rien d’autre
D’après les traces, un client sur localhost essaie de se connecter (127.0.0.1) qui échoue puis le client zigbee2mqtt (172.30.33.3 je suppose) se connecte et réussi.
Je ne comprends pas le 1er client…
je suis de retour de puis lundi, j’ai essayé sans (user/password) utilisateur mqtt et avec mais j’ai toujours un journal mqtt avec des erreurs.
J’ai épuisé tous mes ressources de débutants et je suis bloqué ( notez que tout semble fonctionner normalement )
je ne sais pas s’il y a lieu de faire quelque chose?
voici ma configuration mqtt
cela vous paraît correct ? 
En cliquant sur configuration > paramètres > info puis dans les lignes « intégrations » descendre jusqu’à MQTT
j’ai trouvé un message traitant du même problème qui de prime à bord n’en est pas un.
