PROMO : sonoff-zigbee-30-usb-dongle-plus-efr32mg21 a 20,47

Communauté HACF Petites Annonces
21

Oui c’est vrai, mais je n’ai pas percuté quand HA m’a proposé une nouvelle détection, j’ai installé sans faire le rapprochement avec ZHA

Je test de nouveau…

22

J’ai désactivé et supprimé ZHA, mais je n’arrive toujours pas à accéder à interface

Voici le log

[16:02:23] INFO: Preparing to start...
[16:02:23] INFO: Socat not enabled
[16:02:24] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-03-25 16:02:32: Logging to console and directory: '/config/zigbee2mqtt/log/2023-03-25.16-02-32' filename: log.txt
Zigbee2MQTT:info  2023-03-25 16:02:32: Starting Zigbee2MQTT version 1.30.2 (commit #unknown)
Zigbee2MQTT:info  2023-03-25 16:02:32: Starting zigbee-herdsman (0.14.96)
Zigbee2MQTT:info  2023-03-25 16:02:36: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-03-25 16:02:36: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'
Zigbee2MQTT:info  2023-03-25 16:02:36: Currently 0 devices are joined:
Zigbee2MQTT:info  2023-03-25 16:02:36: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2023-03-25 16:02:36: Connecting to MQTT server at mqtt//core-mosquitto:1883
Zigbee2MQTT:error 2023-03-25 16:02:36: MQTT failed to connect, exiting...
Zigbee2MQTT:info  2023-03-25 16:02:36: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2023-03-25 16:02:39: Stopped zigbee-herdsman
23

Allez, un petit effort … Déjà c’est plus le même message (et donc que le souci précèdent c’est la cohabitation zha/z2m) et puis là il te dit qu’il arrive pas à se connecter à MQTT…
C’est logique, vu que cette partie de ton config est vide …

24

dans Mqtt j’ai mis cela:

server: mqtt//core-mosquitto:1883

voici mon fichier config zigbee2mqtt

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt:
  server: mqtt//core-mosquitto:1883
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20221101080844-if00
  adapter: ezsp
25

c’est mieux. ça correspond à ton cas par contre ?

26

C’est a dire ? désolé mais je suis pas très doué avec les configs…

Mon config de mosquitto est le suivant :

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

C’est pas une question de doué, il y a juste à faire toutes les étapes dans l’ordre.
Là ce que tu montre : ça semble bon, mais il manque peut-être des choses. A vérifier en se basant sur ce tuto par ex

Enfin, suite à modification de la config, il ne faut pas oublier de redémarrer l’addon et de reregarder la logs

28

Je n’y arrive pas, je comprend pas ce qui manque.
J’ai lu le tuto, J’ai crée un user_mqtt dans onglet personne
Je l’ai ajouté dans le fichier config zigbee2mqtt
Mais sa ne veut pas…de plus le log ne s’affiche pas à chaque fois, il reste vierge…

le fichier config zigbee2mqtt:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt:
  server: mqtt//core-mosquitto:1883
  base_topic: zigbee2mqtt
  user: mon user 
  password: mon password
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20221101080844-if00
  adapter: ezsp
29

Créer le user dans Mosquitto, ça marchera mieux.

Ça affiche la log quand tu la demande. Quand ça s’arrête d’écrire il faut rafraîchir manuellement

30

Toujours pareil.
Je sais pas si j’ai bien fait ou mal fait, mais sa ne fonctionne pas…

J’ai cela dans le fichier config de mosquitto :

logins:
  - username: mon_user
    password: mon_password
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
  active: false
  folder: mosquitto

J’ai cela dans fichier config de zigbee2mqtt:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt:
  server: mqtt//core-mosquitto:1883
  user: mon_user
  password: mon_password
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20221101080844-if00
  adapter: ezsp

(Mon_user et mon_password sont les memes dans les 2 fichiers)
J’ai crée un user et password dans onglet Personne avec les droits administrateur

le fichier log de zigbee2mqtt

17:52:00] INFO: Preparing to start...
[17:52:01] INFO: Socat not enabled
[17:52:03] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-03-25 17:52:14: Logging to console and directory: '/config/zigbee2mqtt/log/2023-03-25.17-52-14' filename: log.txt
Zigbee2MQTT:info  2023-03-25 17:52:14: Starting Zigbee2MQTT version 1.30.2 (commit #unknown)
Zigbee2MQTT:info  2023-03-25 17:52:14: Starting zigbee-herdsman (0.14.96)
Zigbee2MQTT:info  2023-03-25 17:52:17: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-03-25 17:52:17: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'
Zigbee2MQTT:info  2023-03-25 17:52:17: Currently 0 devices are joined:
Zigbee2MQTT:info  2023-03-25 17:52:17: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2023-03-25 17:52:17: Connecting to MQTT server at mqtt//core-mosquitto:1883
Zigbee2MQTT:error 2023-03-25 17:52:17: MQTT failed to connect, exiting...
Zigbee2MQTT:info  2023-03-25 17:52:17: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2023-03-25 17:52:18: Stopped zigbee-herdsman

apparemment toujours le problème de connexion à MQTT, mais je sais pas comment le résoudre :pensive:

31

ça ça sert à rien

C’est quoi les logs de mosquitto (après redemarrage)

32

a première vue il ne reconnais pas le client…

023-03-25 17:51:14: Client <unknown> disconnected, not authorised.
2023-03-25 17:51:35: New connection from 192.168.1.184:32360 on port 1883.
error: received null username or password for unpwd check
2023-03-25 17:51:35: Client <unknown> disconnected, not authorised.
2023-03-25 17:51:51: New connection from 172.30.32.2:54924 on port 1883.
2023-03-25 17:51:51: Client <unknown> closed its connection.
2023-03-25 17:52:07: New connection from 192.168.1.181:13021 on port 1883.
error: received null username or password for unpwd check
2023-03-25 17:52:08: Client <unknown> disconnected, not authorised.
2023-03-25 17:52:19: New connection from 192.168.1.180:27068 on port 1883.
error: received null username or password for unpwd check
2023-03-25 17:52:19: Client <unknown> disconnected, not authorised.
2023-03-25 17:52:32: New connection from 192.168.1.184:17063 on port 1883.
error: received null username or password for unpwd check
2023-03-25 17:52:32: Client <unknown> disconnected, not authorised.
2023-03-25 17:53:10: New connection from 192.168.1.181:30068 on port 1883.
error: received null username or password for unpwd check
2023-03-25 17:53:10: Client <unknown> disconnected, not authorised.
2023-03-25 17:53:15: New connection from 192.168.1.180:9002 on port 1883.
error: received null username or password for unpwd check
2023-03-25 17:53:15: Client <unknown> disconnected, not authorised.
2023-03-25 17:53:26: New connection from 192.168.1.184:1049 on port 1883.
error: received null username or password for unpwd check
33

Il y a pas de trace du redémarrage de mosquitto là dedans…
Voilà ce que ça donne (en copiant collant intégralement ta config)

image
image776×481 26.4 KB

Et MQTT explorer s’y connecte correctement.

34

Dans le tuto, il ne parle pas de creer le user dans mosquitto, mais bien dans onglet PERSONNE, je ne sais pas si cela a une influence ou pas…

35

Je viens de le redemarrer et voici le 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
[18:11:39] INFO: Setting up user mqtt_adm
[18:11:40] INFO: Certificates found: SSL is available
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)
[18:11:42] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[18:11:42] INFO: Starting mosquitto MQTT broker...
2023-03-25 18:11:42: Warning: Mosquitto should not be run as root/administrator.
[18:11:44] INFO: Successfully send discovery information to Home Assistant.
[18:11:45] INFO: Successfully send service information to the Supervisor.

Je vais redemarrer zigbee2mqtt…
suite du log mosquitto apres demarrage de zigbee2mqtt:

[18:11:44] INFO: Successfully send discovery information to Home Assistant.
[18:11:45] INFO: Successfully send service information to the Supervisor.
2023-03-25 18:11:42: mosquitto version 2.0.11 starting
2023-03-25 18:11:42: Config loaded from /etc/mosquitto/mosquitto.conf.
2023-03-25 18:11:42: Loading plugin: /usr/share/mosquitto/go-auth.so
2023-03-25 18:11:42:  ├── Username/password checking enabled.
2023-03-25 18:11:42:  ├── TLS-PSK checking enabled.
2023-03-25 18:11:42:  └── Extended authentication not enabled.
2023-03-25 18:11:42: Opening ipv4 listen socket on port 1883.
2023-03-25 18:11:42: Opening ipv6 listen socket on port 1883.
2023-03-25 18:11:42: Opening websockets listen socket on port 1884.
2023-03-25 18:11:42: Opening ipv4 listen socket on port 8883.
2023-03-25 18:11:42: Opening ipv6 listen socket on port 8883.
2023-03-25 18:11:42: Opening websockets listen socket on port 8884.
2023-03-25 18:11:42: mosquitto version 2.0.11 running
2023-03-25 18:11:43: New connection from 127.0.0.1:43002 on port 1883.
2023-03-25 18:11:43: Client <unknown> closed its connection.
2023-03-25 18:11:51: New connection from 172.30.32.2:52924 on port 1883.
2023-03-25 18:11:51: Client <unknown> closed its connection.
2023-03-25 18:12:20: New connection from 192.168.1.184:24756 on port 1883.
error: received null username or password for unpwd check
2023-03-25 18:12:20: Client <unknown> disconnected, not authorised.
2023-03-25 18:12:24: New connection from 192.168.1.180:12972 on port 1883.
error: received null username or password for unpwd check
2023-03-25 18:12:24: Client <unknown> disconnected, not authorised.
2023-03-25 18:12:33: New connection from 192.168.1.181:9205 on port 1883.
error: received null username or password for unpwd check
2023-03-25 18:12:33: Client <unknown> disconnected, not authorised.
2023-03-25 18:13:14: New connection from 192.168.1.184:3414 on port 1883.
error: received null username or password for unpwd check
2023-03-25 18:13:14: Client <unknown> disconnected, not authorised.
2023-03-25 18:13:24: New connection from 192.168.1.180:17285 on port 1883.
error: received null username or password for unpwd check
2023-03-25 18:13:24: Client <unknown> disconnected, not authorised.
2023-03-25 18:13:28: New connection from 192.168.1.181:4292 on port 1883.
error: received null username or password for unpwd check
2023-03-25 18:13:28: Client <unknown> disconnected, not authorised.
2023-03-25 18:13:51: New connection from 172.30.32.2:55900 on port 1883.
2023-03-25 18:13:51: Client <unknown> closed its connection.
2023-03-25 18:14:19: New connection from 192.168.1.184:1185 on port 1883.
error: received null username or password for unpwd check
2023-03-25 18:14:19: Client <unknown> disconnected, not authorised.
2023-03-25 18:14:24: New connection from 192.168.1.180:31566 on port 1883.
36

Manifestement tu as plein de trucs qui se connectent à ton MQTT, les adresses sont différentes
Et tous les rejets sont les appareils sans user/password
Là le seul qui doit marcher c’est z2m

37

Hello

Sans vouloir mettre mon grain de sel quoique

dans Z2M j’ai cela
et j’ai pas mis de mot de passe ni de user dans le configuration.yaml de Z2M

image
image1051×676 23.3 KB

38

les ip qui se termine par 180, 181 et 184 sont des shelly uni
les IP 172.30.x.x et 17.0.x.x je sais pas…

39

Moi oui
image

Mais il va falloir le virer, parce que là ça oblige à refaire la config partout ailleurs

1 « J'aime »
40

ben en fait non car j’ai un user pour frigate declaré dans mosquitto
pareil un user mqtt-explorer
et ça tombe en marche
mais comme les voies de l’informatique sont impénétrables