Mqtt+z2mqtt+conbee2+freebow delta

samourai47 · Mars 13, 2023, 9:20

Hello
Je suis en train d’installer HA en VM sur freebox delta. PAs de soucis pour le moment
J’installe mqtt avec cette configuration et ca demarre impec

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

J’installe z2mqtt avec cette configuration

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:
  adapter: deconz
  port: /dev/ttyACM0

CA démarre impec et la cle conbee 2 semble trouvee, mais ca s’arrete rapidement avec ce msg d’erreur

[22:10:42] INFO: Preparing to start...
[22:10:42] INFO: Socat not enabled
[22:10:44] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-03-13 22:10:48: Logging to console and directory: '/config/zigbee2mqtt/log/2023-03-13.22-10-48' filename: log.txt
Zigbee2MQTT:info  2023-03-13 22:10:48: Starting Zigbee2MQTT version 1.30.2 (commit #unknown)
Zigbee2MQTT:info  2023-03-13 22:10:48: Starting zigbee-herdsman (0.14.96)
Zigbee2MQTT:info  2023-03-13 22:10:49: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-03-13 22:10:49: Coordinator firmware version: '{"meta":{"maintrel":0,"majorrel":38,"minorrel":120,"product":0,"revision":"0x26780700","transportrev":0},"type":"ConBee2/RaspBee2"}'
Zigbee2MQTT:info  2023-03-13 22:10:49: Currently 0 devices are joined:
Zigbee2MQTT:info  2023-03-13 22:10:49: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2023-03-13 22:10:50: Connecting to MQTT server at mqtt://core-mosquitto:1883
Zigbee2MQTT:error 2023-03-13 22:10:50: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2023-03-13 22:10:50: MQTT failed to connect, exiting...
Zigbee2MQTT:info  2023-03-13 22:10:50: Stopping zigbee-herdsman...
Zigbee2MQTT:error 2023-03-13 22:10:51: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:info  2023-03-13 22:10:51: Stopped zigbee-herdsman

et dans mqqtt j’ai

.30.33.3:56738 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:09:36: Client <unknown> disconnected, not authorised.
2023-03-13 22:09:46: New connection from 172.30.33.3:52942 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:09:46: Client <unknown> disconnected, not authorised.
2023-03-13 22:09:47: New connection from 172.30.33.3:52944 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:09:47: Client <unknown> disconnected, not authorised.
2023-03-13 22:09:57: New connection from 172.30.33.3:53234 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:09:57: Client <unknown> disconnected, not authorised.
2023-03-13 22:09:58: New connection from 172.30.33.3:53236 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:09:58: Client <unknown> disconnected, not authorised.
2023-03-13 22:10:07: New connection from 172.30.33.3:60422 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:10:07: Client <unknown> disconnected, not authorised.
2023-03-13 22:10:08: New connection from 172.30.33.3:60430 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:10:08: Client <unknown> disconnected, not authorised.
2023-03-13 22:10:18: New connection from 172.30.33.3:47878 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:10:18: Client <unknown> disconnected, not authorised.
2023-03-13 22:10:19: New connection from 172.30.33.3:47892 on port 1883.
error: received null username or password for unpwd check
2023-03-13 22:10:19: Client <unknown> disconnected, not authorised.

Je suis perdu car je ne vois pas quoi faire. j’ai parcouru plusieurs post mais pas de vrai pistes

Merci pour l’aide

golfvert · Mars 13, 2023, 9:39

On dirait que tu n’as pas défini de user/pwd du côté mosquitto…
A partir de la v2 (je pense que c’est celle de l’addon) c’est obligatoire.
Donc, il faut mettre un truc du côté mqtt et bien sur du coté z2m.

Psykozo51 · Mars 14, 2023, 6:43

Salut,

Novice sur HA, j’ai fait l’installation hier, dans la configuration de Z2M, j’ai pas mis de serveur MQTT

tu peux faire un test en créant un user et en essayant de te connecter avec le soft http://mqtt-explorer.com/

WarC0zes · Mars 14, 2023, 6:57

Bonjour,
comme le dit @Psykozo51 , il faut rien renseigner dans le mqtt si tu utilise l’addon mosquitto broker.

If you are not using the Mosquitto broker addon fill in your MQTT details (leave empty when using the Mosquitto broker addon).

traduction:

Si vous n’utilisez pas l’addon du courtier Mosquitto, remplissez vos détails MQTT (laissez vide lorsque vous utilisez l’addon du courtier Mosquitto).

quand Z2M sera lancer, sa configure automatiquement le server, user et password de mosquitto.
configuration.yaml:

homeassistant:
  legacy_entity_attributes: true
mqtt:
  server: mqtt://core-mosquitto:1883
  user: addons
  password: Thee8ahGhahxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
  keepalive: 60
  reject_unauthorized: true
  version: 4
  include_device_information: false
serial:
  port: >-
    /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_3ee8ee205d29ec1193366f7840c9ce8d-if00-port0
frontend:
  port: 8099
advanced:
  homeassistant_legacy_entity_attributes: false
  legacy_api: false
  legacy_availability_payload: false
  log_level: info
device_options:
  legacy: false
permit_join: false
devices:
  - devices.yaml

samourai47 · Mars 14, 2023, 10:56

top merci
J’ai une autre config sur RPI qui tourne depuis 1 ans je me rappelle pas avoir galeré avec ca

Merci en tous cas

Pulpy-Luke · Mars 21, 2023, 5:07

3 messages ont été fusionnés à un sujet existant : Broker Mosquitto : Client disconnected, not authorised. Broker Mosquitto