[résolu] - Intégration des nouveaux objets zigbee

Entraide Home Assistant
1

Bonjour à tous, je suis un super débutant en domotique , après beaucoup de mal, j’ai réussi à installer zigbee2mqtt , maintenant tout va bien , sauf , que lorsque j’appaire mes capteurs , je les vois que dans la console Zigbee2MQTT !!

1
11051×250 26.7 KB 

Info 2023-04-20 20:40:48MQTT publish: topic 'zigbee2mqtt/xiaomi_9ce5', payload '{"battery":100,"humidity":51.92,"linkquality":244,"power_outage_count":45172,"pressure":1007,"temperature":21.1,"voltage":3055}'
Info 2023-04-20 20:41:32MQTT publish: topic 'zigbee2mqtt/sonoff_7367', payload '{"battery":100,"humidity":53.46,"linkquality":216,"temperature":21.16,"voltage":2900}'
Info 2023-04-20 20:41:32MQTT publish: topic 'zigbee2mqtt/sonoff_7367', payload '{"battery":95,"humidity":53.46,"linkquality":216,"temperature":21.16,"voltage":2900}'

j’ai bien mes 2 capteurs , mais ils n’apparaissent pas ni dans APPAREILS ni dans ENTITES …
J’ai redémarrer home Assistant , et rien pas de nouveaux objets …

2

Hello

Il faut aussi installer un broker mqtt ( mosquitto)

3

Bonsoir didier02100

Et le broker, il en dit quoi?

4

bonsoir, Krull56 , j’ai bien mosquitto broker …
après un redémarrage ,

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
[21:05:18] INFO: Setting up user mqtt
[21:05:20] 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
[21:05:22] INFO: Starting NGINX for authentication handling...
[21:05:23] INFO: Starting mosquitto MQTT broker...
2023-04-20 21:05:23: Warning: Mosquitto should not be run as root/administrator.
[21:05:26] INFO: Successfully send discovery information to Home Assistant.
[21:05:27] INFO: Successfully send service information to the Supervisor.

dans les journaux de Zigbee2MQTT çà cause bien pourtant …

Info 2023-04-20 21:30:17Succesfully changed options
Info 2023-04-20 21:30:17MQTT publish: topic 'zigbee2mqtt/bridge/response/options', payload '{"data":{"restart_required":false},"status":"ok","transaction":"f5n3i-1"}'
Debug 2023-04-20 21:30:38Saving state to file /config/zigbee2mqtt/state.json
Debug 2023-04-20 21:31:12Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Info 2023-04-20 21:31:12MQTT publish: topic 'zigbee2mqtt/0xa4c1382d119df935', payload '{"child_lock":"UNLOCK","current":0,"energy":0.05,"indicator_mode":"off/on","linkquality":76,"power":0,"power_outage_memory":"restore","state":"OFF","voltage":232}'
Debug 2023-04-20 21:31:14Received Zigbee message from 'sonoff_7367', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2090}' from endpoint 1 with groupID 0
Info 2023-04-20 21:31:14MQTT publish: topic 'zigbee2mqtt/sonoff_7367', payload '{"battery":100,"humidity":52.32,"linkquality":128,"temperature":20.9,"voltage":3100}'
Debug 2023-04-20 21:31:15Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Info 2023-04-20 21:31:15MQTT publish: topic 'zigbee2mqtt/0xa4c1382d119df935', payload '{"child_lock":"UNLOCK","current":0,"energy":0.05,"indicator_mode":"off/on","linkquality":76,"power":0,"power_outage_memory":"restore","state":"OFF","voltage":232}'
Debug 2023-04-20 21:31:18Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Info 2023-04-20 21:31:18MQTT publish: topic 'zigbee2mqtt/0xa4c1382d119df935', payload '{"child_lock":"UNLOCK","current":0,"energy":0.05,"indicator_mode":"off/on","linkquality":76,"power":0,"power_outage_memory":"restore","state":"OFF","voltage":232}'
Debug 2023-04-20 21:31:21Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Info 2023-04-20 21:31:21MQTT publish: topic 'zigbee2mqtt/0xa4c1382d119df935', payload '{"child_lock":"UNLOCK","current":0,"energy":0.05,"indicator_mode":"off/on","linkquality":72,"power":0,"power_outage_memory":"restore","state":"OFF","voltage":232}'
Debug 2023-04-20 21:31:59Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Info 2023-04-20 21:31:59MQTT publish: topic 'zigbee2mqtt/0xa4c1382d119df935', payload '{"child_lock":"UNLOCK","current":0,"energy":0.05,"indicator_mode":"off/on","linkquality":72,"power":0,"power_outage_memory":"restore","state":"OFF","voltage":232}'
Debug 2023-04-20 21:31:59Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:31:59Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:31:59Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:00Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:00Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:00Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:00Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:00Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:01Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:01Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:01Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:01Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:01Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:02Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,5]}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:02Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":0,"rmsCurrent":0,"rmsVoltage":232}' from endpoint 1 with groupID 0
Info 2023-04-20 21:32:02MQTT publish: topic 'zigbee2mqtt/0xa4c1382d119df935', payload '{"child_lock":"UNLOCK","current":0,"energy":0.05,"indicator_mode":"off/on","linkquality":72,"power":0,"power_outage_memory":"restore","state":"OFF","voltage":232}'
Debug 2023-04-20 21:32:29Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:29Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:29Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:29Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:30Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:30Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:30Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:30Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:30Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:31Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:31Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:31Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:31Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:31Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
Debug 2023-04-20 21:32:32Received Zigbee message from '0xa4c1382d119df935', type 'attributeReport', cluster 'genBasic', data '{"65506":54,"65508":0,"appVersion":77}' from endpoint 1 with groupID 0
5

Hello

didier02100
Ne confond pas zigbee2mqtt et broker mosquitto
ce sont deux choses differentes

Capture d’écran 2023-04-20 225134
Capture d’écran 2023-04-20 2251341339×802 96.4 KB

As tu confiruger correctement z2m et broker

fais nous voir tes fichiers yaml.

si tu as bien configuré ceci doit apparaître

Capture d’écran 2023-04-20 225500
Capture d’écran 2023-04-20 2255001330×460 81.7 KB

6

Bonjour, ClasscRed …
je n’ai pas

Capture d’écran 2023-04-20 225500
Capture d’écran 2023-04-20 2255001330×460 81.7 KB

j’ai seulement :
.
2

fichier config mosquitto broker :

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

.
fichiers 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
  user: mqtt
  password: didier
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220812104533-if00
  adapter: ezsp
frontend: true

.
fichier /config/zigbee2mqtt/configuration.yaml

mqtt:
  server: mqtt://core-mosquitto:1883
  user: mqtt
  password: didier
  serial: null
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220812104533-if00
adapter: ezsp
frontend:
  port: 8099
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220812104533-if00
  adapter: ezsp
advanced:
  homeassistant_legacy_entity_attributes: false
  legacy_api: false
  legacy_availability_payload: false
  log_level: debug
device_options:
  legacy: false
devices:
  '0x00124b00253d7d2c':
    friendly_name: 7D2C cuisine
  '0x00124b00253d7367':
    friendly_name: sonoff_7367
  '0x00158d0007059ce5':
    friendly_name: xiaomi_9ce5
  '0xa4c1382d119df935':
    friendly_name: prise_bureau_f935
groups:
  '1':
    friendly_name: cuisine

je sais pas pourquoi il y a 2

  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220812104533-if00
  adapter: ezsp

quand j’en enleve un , il revient !!!

7

Salut, as-tu résolu ton problème?

8

non, je refais une install complète , pour moi il y a conflit entre zigbee2mqtt et l’intégration sonoff Zigbee 3.0 dongle + …
1

9

Ca c’est l’intégration de HA pour le zigbee. c’est ZHA. Si tu veux installer Zigbee2mqtt, il faut que tu supprime celle-là.

10

c’est bien ce qu’il me semble , mais même en la suppriment ca ne vas pas … ils ont du se mélanger et se mordre le nez … c’est pour ca que je recommence … conflit de config …

11

Ok. N’hésite pas si tu as des soucis.
Regarde là, tu as un tuto mis à jour:

12

ok , merci du conseil … là j’essais pour voir si tous fonctionne avec Sonoff zigbee 3.0 ( et ca a l’air d’aller) et si c’est ok je recommencerais avec zigbee2mqtt …sur une nouvelle install SANS sonoffZigbee …
edit :
bon suite a une réinstallation neuve sans l’integration Sonoff Zigbee3.0 Dongle plus V2 , ben …
CA MARCHE DU PREMIER COUP !!! :grinning: :stuck_out_tongue_winking_eye:
j’ai suivi ton lien , Barbotx, super !! y a qu’a suivre … j’ aime bien des tuto comme çà …
Merci a tous …

1 « J'aime »