Sauvegarde de la db de zigbee2mqtt

Désolé j’avais zappé la PR ! C’est propre :slight_smile:

Les cas que tu décris ci-dessus c’est si jamais l’utilisateur demande d’installer un container Z2M ?

Si je restaure une sauvegarde sur une instance Gladys vide, est-ce que le service va relancer les containers ?

A tester sinon, moi ça me parait bien !

Sinon je sais pas ce que t’en pense, mais j’ai jamais été fan de mettre du code bash dans Gladys (c’est pas compté dans les unit-tests du coup, c’est un peu bancal)

Je parle du fichier server/services/zigbee2mqtt/docker/gladys-z2m-zigbee2mqtt-env.sh, à mon sens ça devrait être un fichier JS ! :smiley: Bon ça concerne pas forcément cette PR mais typiquement si on pouvait le mettre en JS à un moment ça serait pas mal ^^

@AlexTrovato Petite relance par rapport à mon message ci-dessus !

Oups désolé j’ai oublié

On est obligé d’installer un container Z2M via Gladys actuellement.

Oui, si les conditions car ce sont les variables en db qui conditionnent la création des containers.

Si le container z2m est déjà la, il mettra a jour les valeurs networkId et les autres dans le container z2m et le redémarre, seulement si elles sont différentes.

EDIT : pour les scripts bash, je suis en train de migrer service par service.

1 Like

ça me parait bon du coup !

Ca serait chouette d’avoir des testeurs par contre, mais bon en ce moment c’est calme plat sur le forum ^^

Je peux tester semaine prochaine. Il faudrait juste réfléchir aux différents scénarios

J’ai reçu mon dongle sonoff ce matin mais pas encore les périphériques :wink:
Si je peux aider…

J’ai reçu un Sonoff ZBMini-L
Je peux donc tester ceci:

  • Restauration sans service ZigBee (au cas où mais pas sur que ce soit si utile) ;
  • Restauration après migration de matériel (d’un Pi à l’autre, 32bit et 64bit) ;
  • Restauration du même matos avec et sans changement de port USB.

Je ne sais pas tester

  • Restauration avec changement de dongle (même ou autre modèle)
    Vous pensez à autre chose?

Par contre, aucune idée de comment créer une image de test au départ d’une PR, si vous voyez où je veux en venir :wink:

Édit: Typo

Pour info, en général, je génère une image de test :wink:
Je suis en train d’en générer une plus à jour sur le core commun (intégrer les dernière modifications), elle devrait être dispo d’ici 1 heure.

1 Like

Protocole de test suivi:

  • install clean depuis ton image :whale: :white_check_mark:
  • activation du service zigbee2mqtt :white_check_mark:
  • ajout de périphériques et test du service zigbee2mqqt :white_check_mark:
  • arrêt de gladys (et de tous les containers) :white_check_mark:
  • suppression des fichiers de configuration z2m et du container gladys-z2m-zigbee2mqtt :white_check_mark:
  • réactivation du service Zigbee2mqtt :white_check_mark:
  • test du service zigbee2mqqt :no_entry:

Lors du premier lancement du service Zigbee2Mqtt, j’ai l’erreur suivante

2022-07-20T21:54:11+0200 <error> installZ2mContainer.js:77 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt failed to backup Docker container configuration Error: ENOENT: no such file or directory, open '/var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yaml'
    at Object.openSync (fs.js:498:3)
    at Object.readFileSync (fs.js:394:35)
    at Zigbee2mqttManager.installZ2mContainer (/src/server/services/zigbee2mqtt/lib/installZ2mContainer.js:70:36)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Zigbee2mqttManager.init (/src/server/services/zigbee2mqtt/lib/init.js:66:5)
    at async connect (/src/server/services/zigbee2mqtt/api/zigbee2mqtt.controller.js:34:5) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/var/lib/gladysassistant/zigbee2mqtt/z2m/configuration.yaml'
}

J’ai relancé et ça a marché. Mais les données en base sont bizarres

Si je supprime tout et restaure une sauvegarde, le fichier configuration.yaml contient

advanced:
  # Optional: ZigBee pan ID (default: shown below)
  # Setting pan_id: GENERATE will make Zigbee2MQTT generate a new panID on next startup
  pan_id: 0xGENERATE
  # Optional: ZigBee channel, changing requires re-pairing of all devices. (Note: use a ZLL channel: 11, 15, 20, or 25 to avoid Problems)
  # (default: 11)
  channel: 11
  # Optional: network encryption key, will improve security
  # Note: changing requires repairing of all devices (default: shown below)
  network_key: GENERATE
2 Likes

Tout apparaît comme si rien ne s’était passé

sauf que… Aucune réaction du périphérique lié
Voici le log du container Z2m après suppression du dossier Z2m (sudo rm -r /var/lib/gladysassistant/zigbee2mqtt/) et redémarrage de Gladys

Zigbee2MQTT:info  2022-07-25 19:43:52: Stopping zigbee-herdsman...
Using '/app/data' as data directory
Creating configuration file...
Zigbee2MQTT:info  2022-07-25 19:47:33: Logging to console and directory: '/app/data/log/2022-07-25.19-47-33' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:47:34: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:47:34: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-25 19:47:58: zigbee-herdsman started (reset)
Zigbee2MQTT:info  2022-07-25 19:47:58: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-25 19:47:58: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-07-25 19:47:58: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-07-25 19:47:58: Allowing new devices to join.
Zigbee2MQTT:warn  2022-07-25 19:47:58: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-07-25 19:47:58: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-25 19:47:58: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:error 2022-07-25 19:47:59: MQTT failed to connect: connect ECONNREFUSED 127.0.0.1:1883
Zigbee2MQTT:error 2022-07-25 19:47:59: Exiting...
Zigbee2MQTT:info  2022-07-25 19:47:59: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-07-25 19:48:11: Stopped zigbee-herdsman
Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-25 19:48:26: Logging to console and directory: '/app/data/log/2022-07-25.19-48-26' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:48:26: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:48:26: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-25 19:48:28: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-07-25 19:48:28: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-25 19:48:28: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-07-25 19:48:28: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-07-25 19:48:28: Allowing new devices to join.
Zigbee2MQTT:warn  2022-07-25 19:48:28: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-07-25 19:48:28: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-25 19:48:29: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:error 2022-07-25 19:48:29: MQTT failed to connect: connect ECONNREFUSED 127.0.0.1:1883
Zigbee2MQTT:error 2022-07-25 19:48:29: Exiting...
Zigbee2MQTT:info  2022-07-25 19:48:29: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-07-25 19:48:41: Stopped zigbee-herdsman

Après redémarrage manuel du container :

Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-25 19:51:59: Logging to console and directory: '/app/data/log/2022-07-25.19-51-59' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:51:59: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:51:59: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-25 19:52:02: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-07-25 19:52:02: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-25 19:52:02: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-07-25 19:52:02: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-07-25 19:52:02: Allowing new devices to join.
Zigbee2MQTT:warn  2022-07-25 19:52:02: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-07-25 19:52:02: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-25 19:52:02: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:error 2022-07-25 19:52:02: MQTT failed to connect: connect ECONNREFUSED 127.0.0.1:1883
Zigbee2MQTT:error 2022-07-25 19:52:02: Exiting...
Zigbee2MQTT:info  2022-07-25 19:52:02: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-07-25 19:52:14: Stopped zigbee-herdsman
Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-25 19:52:29: Logging to console and directory: '/app/data/log/2022-07-25.19-52-29' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:52:29: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:52:29: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-25 19:52:32: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-07-25 19:52:32: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-25 19:52:32: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-07-25 19:52:32: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-07-25 19:52:32: Allowing new devices to join.
Zigbee2MQTT:warn  2022-07-25 19:52:32: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-07-25 19:52:32: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-25 19:52:32: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:error 2022-07-25 19:52:33: MQTT failed to connect: connect ECONNREFUSED 127.0.0.1:1883
Zigbee2MQTT:error 2022-07-25 19:52:33: Exiting...
Zigbee2MQTT:info  2022-07-25 19:52:33: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-07-25 19:52:45: Stopped zigbee-herdsman
Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-25 19:53:00: Logging to console and directory: '/app/data/log/2022-07-25.19-52-59' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:53:00: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:53:00: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-25 19:53:02: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-07-25 19:53:02: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-25 19:53:02: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-07-25 19:53:02: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-07-25 19:53:02: Allowing new devices to join.
Zigbee2MQTT:warn  2022-07-25 19:53:02: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-07-25 19:53:02: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-25 19:53:02: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:error 2022-07-25 19:53:03: MQTT failed to connect: connect ECONNREFUSED 127.0.0.1:1883
Zigbee2MQTT:error 2022-07-25 19:53:03: Exiting...
Zigbee2MQTT:info  2022-07-25 19:53:03: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-07-25 19:53:15: Stopped zigbee-herdsman
Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-25 19:53:30: Logging to console and directory: '/app/data/log/2022-07-25.19-53-30' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:53:30: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:53:30: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-25 19:53:33: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-07-25 19:53:33: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-25 19:53:33: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-07-25 19:53:33: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-07-25 19:53:33: Allowing new devices to join.
Zigbee2MQTT:warn  2022-07-25 19:53:33: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-07-25 19:53:33: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-25 19:53:33: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:error 2022-07-25 19:53:33: MQTT failed to connect: connect ECONNREFUSED 127.0.0.1:1883
Zigbee2MQTT:error 2022-07-25 19:53:34: Exiting...
Zigbee2MQTT:info  2022-07-25 19:53:34: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-07-25 19:53:46: Stopped zigbee-herdsman
Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-25 19:54:01: Logging to console and directory: '/app/data/log/2022-07-25.19-54-00' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:54:01: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:54:01: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:error 2022-07-25 19:54:03: Not connected to MQTT server!
Zigbee2MQTT:error 2022-07-25 19:54:03: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: '{"state":"offline"}
Zigbee2MQTT:info  2022-07-25 19:54:03: Disconnecting from MQTT server
TypeError: Cannot read properties of undefined (reading 'end')
    at MQTT.disconnect (/app/lib/mqtt.ts:111:21)
    at Controller.stop (/app/lib/controller.ts:197:9)
    at stop (/app/index.js:113:5)
    at process.handleQuit (/app/index.js:119:9)
Using '/app/data' as data directory
Zigbee2MQTT:info  2022-07-25 19:54:18: Logging to console and directory: '/app/data/log/2022-07-25.19-54-18' filename: log.txt
Zigbee2MQTT:info  2022-07-25 19:54:18: Starting Zigbee2MQTT version 1.26.0 (commit #cd23aea)
Zigbee2MQTT:info  2022-07-25 19:54:18: Starting zigbee-herdsman (0.14.40)
Zigbee2MQTT:info  2022-07-25 19:54:20: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-07-25 19:54:20: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-07-25 19:54:20: Currently 0 devices are joined:
Zigbee2MQTT:warn  2022-07-25 19:54:20: `permit_join` set to  `true` in configuration.yaml.
Zigbee2MQTT:warn  2022-07-25 19:54:20: Allowing new devices to join.
Zigbee2MQTT:warn  2022-07-25 19:54:20: Set `permit_join` to `false` once you joined all devices.
Zigbee2MQTT:info  2022-07-25 19:54:20: Zigbee: allowing new devices to join.
Zigbee2MQTT:info  2022-07-25 19:54:21: Connecting to MQTT server at mqtt://localhost
Zigbee2MQTT:error 2022-07-25 19:54:21: MQTT failed to connect: connect ECONNREFUSED 127.0.0.1:1883
Zigbee2MQTT:error 2022-07-25 19:54:21: Exiting...
Zigbee2MQTT:info  2022-07-25 19:54:21: Stopping zigbee-herdsman...
Zigbee2MQTT:info  2022-07-25 19:54:33: Stopped zigbee-herdsman
Using '/app/data' as data directory

Et le log de Gladys :

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js
2022-07-25T21:47:06+0200 <info> job.purge.js:17 (Job.purge) Deleting all background jobs created before = Mon Jul 18 2022 21:47:06 GMT+0200 (Central European Summer Time)
Initialising OpenZWave 1.6.0 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2022-07-25T21:47:14+0200 <info> index.js:14 (Object.start) starting Alexa service
2022-07-25T21:47:14+0200 <info> index.js:19 (Object.start) Starting example service
2022-07-25T21:47:14+0200 <info> index.js:64 (Object.start) Starting CalDAV service
2022-07-25T21:47:15+0200 <info> index.js:16 (Object.start) Starting zwave service
2022-07-25T21:47:15+0200 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2022-07-25T21:47:15+0200 <info> index.js:14 (Object.start) starting GoogleActions service
2022-07-25T21:47:15+0200 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2022-07-25T21:47:15+0200 <info> installMqttContainer.js:104 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2022-07-25T21:47:15+0200 <info> installZ2mContainer.js:88 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container is starting...
2022-07-25T21:47:21+0200 <info> installZ2mContainer.js:94 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2022-07-25T21:47:21+0200 <info> connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker...
2022-07-25T21:47:22+0200 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2022-07-25T21:47:22+0200 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2022-07-25T21:47:22+0200 <info> index.js:18 (Object.start) Starting TP-Link service
2022-07-25T21:47:22+0200 <info> index.js:17 (Object.start) Starting eWeLink service
2022-07-25T21:47:22+0200 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2022-07-25T21:47:22+0200 <info> index.js:15 (Object.start) Starting Bluetooth service
2022-07-25T21:47:23+0200 <error> index.js:20 (process.<anonymous>) uncaughtException catched: uncaughtException
2022-07-25T21:47:23+0200 <error> index.js:21 (process.<anonymous>) Error: ENODEV, No such device
    at Hci.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
    at NobleBindings.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
    at /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/noble.js:60:24
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  errno: 19,
  code: 'ENODEV',
  syscall: 'bind'
}
2022-07-25T21:47:23+0200 <info> index.js:15 (Object.start) Starting Tasmota service
2022-07-25T21:47:23+0200 <info> index.js:14 (Object.start) Starting Xiaomi service
2022-07-25T21:47:23+0200 <info> index.js:13 (Object.start) Starting usb service
2022-07-25T21:47:24+0200 <info> index.js:19 (Object.start) Starting Telegram service
2022-07-25T21:47:24+0200 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2022-07-25T21:47:24+0200 <info> index.js:16 (Object.start) Starting RTSP service
2022-07-25T21:47:24+0200 <info> index.js:18 (Object.start) Starting Philips Hue service
2022-07-25T21:47:24+0200 <info> index.js:16 (Object.start) Starting MQTT service
2022-07-25T21:47:24+0200 <info> updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...
2022-07-25T21:47:24+0200 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.
2022-07-25T21:47:24+0200 <info> index.js:20 (Object.start) Starting Open Weather service
2022-07-25T21:47:24+0200 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2022-07-25T21:47:24+0200 <info> scene.dailyUpdate.js:58 () Sunrise today is at 6:1 today, in your timezone = Europe/Luxembourg
2022-07-25T21:47:24+0200 <info> scene.dailyUpdate.js:59 () Sunset today is at 21:38 today, in your timezone = Europe/Luxembourg

Hope it helps !

Après redémarrage complet du pi :


image
Donc voici son log :

1658775498: mosquitto version 2.0.14 starting
1658775498: Config loaded from /mosquitto/config/mosquitto.conf.
1658775498: Opening ipv4 listen socket on port 1884.
1658775498: Opening ipv6 listen socket on port 1884.
1658775498: mosquitto version 2.0.14 running
1658775504: mosquitto version 2.0.14 terminating
1658775505: mosquitto version 2.0.14 starting
1658775505: Config loaded from /mosquitto/config/mosquitto.conf.
1658775505: Opening ipv4 listen socket on port 1884.
1658775505: Opening ipv6 listen socket on port 1884.
1658775505: mosquitto version 2.0.14 running
1658775609: New connection from 127.0.0.1:60738 on port 1884.
1658775609: New client connected from 127.0.0.1:60738 as gladys-main-instance-341414 (p2, c1, k60, u'gladys').
1658775643: New connection from 127.0.0.1:60740 on port 1884.
1658775643: New client connected from 127.0.0.1:60740 as mqttjs_9c41c1bd (p2, c1, k60, u'z2m').
1658778196: Client gladys-main-instance-341414 closed its connection.
1658778232: Client mqttjs_9c41c1bd disconnected.
1658778442: New connection from 127.0.0.1:60742 on port 1884.
1658778442: New client connected from 127.0.0.1:60742 as gladys-main-instance-66014 (p2, c1, k60, u'gladys').
1658779732: mosquitto version 2.0.14 terminating
1658779782: Error: Unable to open config file /mosquitto/config/mosquitto.conf.
1658779783: Error: Unable to open config file /mosquitto/config/mosquitto.conf.
1658779785: Error: Unable to open config file /mosquitto/config/mosquitto.conf.
1658779786: Error: Unable to open config file /mosquitto/config/mosquitto.conf.

J’imagine qu’il faut donc restaurer ça aussi.
L’interface Z2m est inaccessible

Merci pour ces infos. Je vais regarder d’avantages, et je vous préviendrais pour une seconde phase de test. Merci encore.

3 Likes

Et encore un peu :wink:
Le fichier z2m/configuration.yaml avant :

homeassistant: false
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://localhost:1884
  user: z2m
  password: L2LwEonI4RMeDhkvL5BP
serial:
  port: /dev/ttyACM0
frontend:
  port: 8080
map_options:
  graphviz:
    colors:
      fill:
        enddevice: '#fff8ce'
        coordinator: '#e04e5d'
        router: '#4ea3e0'
      font:
        coordinator: '#ffffff'
        router: '#ffffff'
        enddevice: '#000000'
      line:
        active: '#009900'
        inactive: '#994444'
advanced:
  pan_id: 48208 
 channel: 11
  network_key:
    - 85
    - 174
    - 157
    - 235
    - 124
    - 251
    - 237
    - 225
    - 131
    - 189
    - 177
    - 21
    - 138
    - 254
    - 205
    - 168
  homeassistant_legacy_entity_attributes: false
  legacy_api: false
  legacy_availability_payload: false
device_options:
  legacy: false
devices:
  '0xXXXXXXXXXX':
    friendly_name: '0xXXXXXXXXXXX'

Et après :

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://localhost
serial:
  port: /dev/ttyACM0
advanced:
  homeassistant_legacy_entity_attributes: false
  legacy_api: false
  legacy_availability_payload: false
device_options:
  legacy: false

Bonjour à tous,


Il aurait fallu supprimer le container z2m, car Gladys n’inscrit pas le fichier de configuration si le container existe, mais tu as supprimé le fichier configuration.yml

Je vais donc gérer également ce cas.

:warning: maintenant tu as les variables de configuration stockée en DB, je te conseille de les supprimer avant le prochain test avec les correctifs : Z2M_CONFIG_NETWORK Z2M_CONFIG_CHANNEL Z2M_CONFIG_PAN_ID

Et pour information, GENERATED est la valeur par défaut de z2m, ainsi au startup, GENERATED sera modifié par une vraie valeur (je dois donc récupérer les valeurs après le démarrage du container).


Il aurait fallu :

  • stopper Gladys
  • supprimer le container z2m
  • supprimer les fichiers de config z2m
  • redémarrer Gladys

Car, comme dit précédemment, Gladys vérifie sur le container z2m existe, afin de savoir s’il faut le configurer ou non.
Je vais changer ce comportement, ainsi le fichier sera vérifié quoi qu’il arrive.

Le second fichier de config n’a donc pas été généré par Gladys (pour les raisons énoncées précédemment), mais c’est le fichier par défaut de z2m.

Pareil que pour @cicoub13
:warning: maintenant tu as les variables de configuration stockée en DB, je te conseille de les supprimer avant le prochain test avec les correctifs : Z2M_CONFIG_NETWORK Z2M_CONFIG_CHANNEL Z2M_CONFIG_PAN_ID

Je conseille donc soit de supprimer les variables Gladys, soit de repartir d’une DB neuve.


Nouvelle image atrovato/gladys:zigbee2mqtt en cours de génération (dispo d’ici 1h30), pensez à bien supprimer le container ET l’image déjà téléchargée de la version de test de Gladys avant de tester à nouveau.

Merci à tous.

1 Like

Au départ d’une image propre.
Installation de la dernière image
Configuration du device z2m
Suppression des containers et des dossiers z2m
Redémarrage
Échec.
Voici la totale:

pi@raspberrypi:~ $ docker stop gladys
gladys

pi@raspberrypi:~ $ docker stop gladys-z2m-mqtt               
gladys-z2m-mqtt                                              

pi@raspberrypi:~ $ docker stop gladys-z2m-zigbee2mqtt        
gladys-z2m-zigbee2mqtt                                       

pi@raspberrypi:~ $ docker rm gladys-z2m-zigbee2mqtt          
gladys-z2m-zigbee2mqtt                                       

pi@raspberrypi:~ $ docker rm gladys-z2m-mqtt                 
gladys-z2m-mqtt                                              

pi@raspberrypi:~ $ sudo rm -r /var/lib/gladysassistant/zigbee2mqtt/                                                       

pi@raspberrypi:~ $ ls /var/lib/gladysassistant/              
gladys-production.db                                         

pi@raspberrypi:~ $ docker start gladys                       
gladys                                                       

pi@raspberrypi:~ $ docker ps                                 CONTAINER ID   IMAGE                         COMMAND                  CREATED          STATUS          PORTS     NAMES
3a4c5e9d8091   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   10 minutes ago   Up 19 seconds             gladys

pi@raspberrypi:~ $ docker ps
CONTAINER ID   IMAGE                         COMMAND                  CREATED          STATUS          PORTS     NAMES
c4f45dfc24ae   eclipse-mosquitto:2           "/docker-entrypoint.…"   3 seconds ago    Up 2 seconds              gladys-z2m-mqtt
3a4c5e9d8091   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   10 minutes ago   Up 45 seconds             gladys

pi@raspberrypi:~ $ docker ps
CONTAINER ID   IMAGE                         COMMAND                  CREATED          STATUS              PORTS     NAMES
4dda4261f43c   koenkk/zigbee2mqtt:latest     "docker-entrypoint.s…"   25 seconds ago   Up 1 second                   gladys-z2m-zigbee2mqtt
c4f45dfc24ae   eclipse-mosquitto:2           "/docker-entrypoint.…"   40 seconds ago   Up 31 seconds                 gladys-z2m-mqtt
3a4c5e9d8091   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   11 minutes ago   Up About a minute             gladys

pi@raspberrypi:~ $ docker ps                                 CONTAINER ID   IMAGE                         COMMAND                  CREATED              STATUS              PORTS     NAMES
4dda4261f43c   koenkk/zigbee2mqtt:latest     "docker-entrypoint.s…"   51 seconds ago       Up 1 second                   gladys-z2m-zigbee2mqtt
c4f45dfc24ae   eclipse-mosquitto:2           "/docker-entrypoint.…"   About a minute ago   Up 57 seconds                 gladys-z2m-mqtt
3a4c5e9d8091   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   11 minutes ago       Up About a minute             gladys

Les logs

Gladys :

pi@raspberrypi:~ $ docker logs gladys

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

2022-07-31T18:21:06+0200 <info> 20210129155044-multi-user.js:23 (Object.up) Multi-user migration: 0 users found
2022-07-31T18:21:07+0200 <info> job.purge.js:17 (Job.purge) Deleting all background jobs created before = Sun Jul 24 2022 18:21:07 GMT+0200 (Central European Summer Time)
Initialising OpenZWave 1.6.0 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2022-07-31T18:21:14+0200 <info> index.js:14 (Object.start) starting Alexa service
2022-07-31T18:21:14+0200 <info> index.js:64 (Object.start) Starting CalDAV service
2022-07-31T18:21:14+0200 <info> index.js:20 (Object.start) Starting Open Weather service
2022-07-31T18:21:14+0200 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2022-07-31T18:21:15+0200 <info> index.js:21 (Object.start) Starting example service
2022-07-31T18:21:15+0200 <info> index.js:14 (Object.start) starting GoogleActions service
2022-07-31T18:21:15+0200 <info> init.js:31 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle not attached
2022-07-31T18:21:15+0200 <info> index.js:18 (Object.start) Starting TP-Link service
2022-07-31T18:21:15+0200 <info> index.js:17 (Object.start) Starting eWeLink service
2022-07-31T18:21:15+0200 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2022-07-31T18:21:15+0200 <info> index.js:15 (Object.start) Starting Bluetooth service
2022-07-31T18:21:16+0200 <error> index.js:20 (process.<anonymous>) uncaughtException catched: uncaughtException
2022-07-31T18:21:16+0200 <error> index.js:21 (process.<anonymous>) Error: ENODEV, No such device
    at Hci.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
    at NobleBindings.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
    at /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/noble.js:60:24
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  errno: 19,
  code: 'ENODEV',
  syscall: 'bind'
}
2022-07-31T18:21:16+0200 <info> index.js:15 (Object.start) Starting Tasmota service
2022-07-31T18:21:16+0200 <info> index.js:16 (Object.start) Starting zwave service
2022-07-31T18:21:16+0200 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2022-07-31T18:21:16+0200 <info> index.js:14 (Object.start) Starting Xiaomi service
2022-07-31T18:21:16+0200 <info> index.js:13 (Object.start) Starting usb service
2022-07-31T18:21:16+0200 <info> index.js:19 (Object.start) Starting Telegram service
2022-07-31T18:21:16+0200 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2022-07-31T18:21:16+0200 <info> index.js:16 (Object.start) Starting RTSP service
2022-07-31T18:21:16+0200 <info> index.js:18 (Object.start) Starting Philips Hue service
2022-07-31T18:21:17+0200 <info> index.js:16 (Object.start) Starting MQTT service
2022-07-31T18:21:17+0200 <info> updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...2022-07-31T18:21:17+0200 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.2022-07-31T18:21:17+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval hourly
2022-07-31T18:21:17+0200 <info> index.js:63 (Server.<anonymous>) Server listening on port 80
2022-07-31T18:21:24+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval hourly
2022-07-31T18:21:24+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval daily
2022-07-31T18:21:32+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval daily
2022-07-31T18:21:32+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval monthly
2022-07-31T18:21:39+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval monthly
2022-07-31T18:22:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sun, 31 Jul 2022 16:22:00 GMT
2022-07-31T18:22:19+0200 <info> scene.dailyUpdate.js:58 () Sunrise today is at 6:9 today, in your timezone = Europe/Paris
2022-07-31T18:22:19+0200 <info> scene.dailyUpdate.js:59 () Sunset today is at 21:29 today, in your timezone = Europe/Paris2022-07-31T18:22:19+0200 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2022-07-31T18:22:19+0200 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
2022-07-31T18:22:59+0200 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2022-07-31T18:22:59+0200 <info> installMqttContainer.js:28 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...
2022-07-31T18:22:59+0200 <info> installMqttContainer.js:29 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:2 image...
2022-07-31T18:23:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sun, 31 Jul 2022 16:23:00 GMT
2022-07-31T18:23:04+0200 <info> installMqttContainer.js:33 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2022-07-31T18:23:04+0200 <info> installMqttContainer.js:40 (Zigbee2mqttManager.installMqttContainer) Creating container with data in "/var/lib/gladysassistant" on host...
2022-07-31T18:23:04+0200 <info> installMqttContainer.js:54 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-07-31T18:23:10+0200 <info> installMqttContainer.js:61 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...2022-07-31T18:23:11+0200 <info> installMqttContainer.js:70 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-07-31T18:23:17+0200 <info> installMqttContainer.js:74 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started and configured
2022-07-31T18:23:17+0200 <info> installZ2mContainer.js:33 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2022-07-31T18:23:17+0200 <info> installZ2mContainer.js:34 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2022-07-31T18:23:19+0200 <info> installZ2mContainer.js:37 (Zigbee2mqttManager.installZ2mContainer) Configuration of Device /dev/ttyUSB0
2022-07-31T18:23:19+0200 <info> installZ2mContainer.js:42 (Zigbee2mqttManager.installZ2mContainer) Creation of container...
2022-07-31T18:23:19+0200 <info> installZ2mContainer.js:45 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed and configured as Docker container
2022-07-31T18:23:19+0200 <info> installZ2mContainer.js:58 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2022-07-31T18:23:19+0200 <info> installZ2mContainer.js:72 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container is starting...
2022-07-31T18:23:25+0200 <info> installZ2mContainer.js:78 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2022-07-31T18:23:25+0200 <info> connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker...
2022-07-31T18:23:26+0200 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2022-07-31T18:23:26+0200 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2022-07-31T18:24:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sun, 31 Jul 2022 16:24:00 GMT
2022-07-31T18:25:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sun, 31 Jul 2022 16:25:00 GMT
2022-07-31T18:26:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sun, 31 Jul 2022 16:26:00 GMT
2022-07-31T18:26:28+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:29+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:30+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:30+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:31+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:32+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:33+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:33+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:34+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:26:35+0200 <warn> handleMqttMessage.js:100 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-07-31T18:27:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sun, 31 Jul 2022 16:27:00 GMT
2022-07-31T18:27:12+0200 <info> index.js:25 (shutdown) SIGTERM received.
2022-07-31T18:27:12+0200 <info> index.js:31 (shutdown) Closing database connection.

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

2022-07-31T18:30:51+0200 <info> job.purge.js:17 (Job.purge) Deleting all background jobs created before = Sun Jul 24 2022 18:30:51 GMT+0200 (Central European Summer Time)
Initialising OpenZWave 1.6.0 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2022-07-31T18:30:58+0200 <info> index.js:14 (Object.start) starting Alexa service
2022-07-31T18:30:58+0200 <info> index.js:16 (Object.start) Starting RTSP service
2022-07-31T18:30:58+0200 <info> index.js:13 (Object.start) Starting usb service
2022-07-31T18:30:58+0200 <info> index.js:19 (Object.start) Starting Telegram service
2022-07-31T18:30:58+0200 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2022-07-31T18:30:58+0200 <info> index.js:14 (Object.start) starting GoogleActions service
2022-07-31T18:30:59+0200 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2022-07-31T18:30:59+0200 <info> installMqttContainer.js:28 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...
2022-07-31T18:30:59+0200 <info> installMqttContainer.js:29 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:2 image...
2022-07-31T18:31:01+0200 <info> installMqttContainer.js:33 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2022-07-31T18:31:01+0200 <info> installMqttContainer.js:40 (Zigbee2mqttManager.installMqttContainer) Creating container with data in "/var/lib/gladysassistant" on host...
2022-07-31T18:31:01+0200 <info> installMqttContainer.js:54 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-07-31T18:31:07+0200 <info> installMqttContainer.js:61 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...2022-07-31T18:31:08+0200 <info> installMqttContainer.js:70 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-07-31T18:31:14+0200 <info> installMqttContainer.js:74 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started and configured
2022-07-31T18:31:14+0200 <info> installZ2mContainer.js:33 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2022-07-31T18:31:14+0200 <info> installZ2mContainer.js:34 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2022-07-31T18:31:16+0200 <info> installZ2mContainer.js:37 (Zigbee2mqttManager.installZ2mContainer) Configuration of Device /dev/ttyUSB0
2022-07-31T18:31:16+0200 <info> installZ2mContainer.js:42 (Zigbee2mqttManager.installZ2mContainer) Creation of container...
2022-07-31T18:31:16+0200 <info> installZ2mContainer.js:45 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed and configured as Docker container
2022-07-31T18:31:16+0200 <info> installZ2mContainer.js:58 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2022-07-31T18:31:16+0200 <info> installZ2mContainer.js:72 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container is starting...
2022-07-31T18:31:22+0200 <info> installZ2mContainer.js:78 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2022-07-31T18:31:22+0200 <info> connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker...
2022-07-31T18:31:23+0200 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2022-07-31T18:31:23+0200 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2022-07-31T18:31:23+0200 <info> index.js:18 (Object.start) Starting TP-Link service
2022-07-31T18:31:23+0200 <info> index.js:17 (Object.start) Starting eWeLink service
2022-07-31T18:31:23+0200 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2022-07-31T18:31:23+0200 <info> index.js:15 (Object.start) Starting Bluetooth service
2022-07-31T18:31:24+0200 <error> index.js:20 (process.<anonymous>) uncaughtException catched: uncaughtException
2022-07-31T18:31:24+0200 <error> index.js:21 (process.<anonymous>) Error: ENODEV, No such device
    at Hci.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
    at NobleBindings.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
    at /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/noble.js:60:24
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  errno: 19,
  code: 'ENODEV',
  syscall: 'bind'
}
2022-07-31T18:31:24+0200 <info> index.js:15 (Object.start) Starting Tasmota service
2022-07-31T18:31:24+0200 <info> index.js:16 (Object.start) Starting zwave service
2022-07-31T18:31:24+0200 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2022-07-31T18:31:24+0200 <info> index.js:14 (Object.start) Starting Xiaomi service
2022-07-31T18:31:24+0200 <info> index.js:20 (Object.start) Starting Open Weather service
2022-07-31T18:31:24+0200 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2022-07-31T18:31:24+0200 <info> index.js:18 (Object.start) Starting Philips Hue service
2022-07-31T18:31:25+0200 <info> index.js:16 (Object.start) Starting MQTT service
2022-07-31T18:31:25+0200 <info> updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...2022-07-31T18:31:25+0200 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.2022-07-31T18:31:25+0200 <info> index.js:64 (Object.start) Starting CalDAV service
2022-07-31T18:31:25+0200 <info> index.js:21 (Object.start) Starting example service
2022-07-31T18:31:25+0200 <info> scene.dailyUpdate.js:58 () Sunrise today is at 6:9 today, in your timezone = Europe/Paris
2022-07-31T18:31:25+0200 <info> scene.dailyUpdate.js:59 () Sunset today is at 21:29 today, in your timezone = Europe/Paris2022-07-31T18:31:25+0200 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2022-07-31T18:31:25+0200 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 3 hours.
2022-07-31T18:31:25+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval hourly
2022-07-31T18:31:26+0200 <info> index.js:63 (Server.<anonymous>) Server listening on port 80
2022-07-31T18:31:34+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval hourly
2022-07-31T18:31:34+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval daily
2022-07-31T18:31:43+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval daily
2022-07-31T18:31:44+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval monthly
2022-07-31T18:31:52+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval monthly
2022-07-31T18:32:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sun, 31 Jul 2022 16:32:00 GMT
2022-07-31T18:32:19+0200 <warn> scene.executeActions.js:37 (executeAction) BadParameters [Error]: Zigbee2mqtt expose not found: "zigbee2mqtt:0x00124b0024c06f1c:switch:binary:state" with property "state"
    at Zigbee2mqttManager.setValue (/src/server/services/zigbee2mqtt/lib/setValue.js:38:11)
    at DeviceManager.setValue (/src/server/lib/device/device.setValue.js:21:24)
    at Object.device.set-value (/src/server/lib/scene/scene.actions.js:30:24)
    at executeAction (/src/server/lib/scene/scene.executeActions.js:32:35)
    at SceneManager.executeSingleAction (/src/server/lib/scene/scene.executeSingleAction.js:17:11)
    at EventEmitter.<anonymous> (/src/server/utils/functionsWrapper.js:13:13)
    at EventEmitter.emit (events.js:400:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)
2022-07-31T18:32:21+0200 <warn> scene.executeActions.js:37 (executeAction) BadParameters [Error]: Zigbee2mqtt expose not found: "zigbee2mqtt:0x00124b0024c06f1c:switch:binary:state" with property "state"
    at Zigbee2mqttManager.setValue (/src/server/services/zigbee2mqtt/lib/setValue.js:38:11)
    at DeviceManager.setValue (/src/server/lib/device/device.setValue.js:21:24)
    at Object.device.set-value (/src/server/lib/scene/scene.actions.js:30:24)
    at executeAction (/src/server/lib/scene/scene.executeActions.js:32:35)
    at SceneManager.executeSingleAction (/src/server/lib/scene/scene.executeSingleAction.js:17:11)
    at EventEmitter.<anonymous> (/src/server/utils/functionsWrapper.js:13:13)
    at EventEmitter.emit (events.js:400:28)
    at Event.emit (/src/server/lib/event/index.js:18:16)

Z2m :


pi@raspberrypi:~ $ docker logs gladys-z2m-zigbee2mqtt
Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Using '/app/data' as data directory


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
            READ THIS CAREFULLY

Refusing to start because configuration is not valid, found the following errors:
- advanced.pan_id: should be number or 'GENERATE' (is '0xGENERATE')

If you don't know how to solve this, read https://www.zigbee2mqtt.io/guide/configuration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Z2m MQTT :

pi@raspberrypi:~ $ docker logs gladys-z2m-mqtt
1659285062: mosquitto version 2.0.14 starting
1659285062: Config loaded from /mosquitto/config/mosquitto.conf.
1659285062: Opening ipv4 listen socket on port 1884.
1659285062: Opening ipv6 listen socket on port 1884.
1659285062: mosquitto version 2.0.14 running
1659285068: mosquitto version 2.0.14 terminating
1659285069: mosquitto version 2.0.14 starting
1659285069: Config loaded from /mosquitto/config/mosquitto.conf.
1659285069: Opening ipv4 listen socket on port 1884.
1659285069: Opening ipv6 listen socket on port 1884.
1659285069: mosquitto version 2.0.14 running
1659285083: New connection from 127.0.0.1:37116 on port 1884.1659285083: New client connected from 127.0.0.1:37116 as gladys-main-instance-113944 (p2, c1, k60, u'gladys').
pi@raspberrypi:~ $

Édit : Facilité de lecture

1 Like

Ton image z2m et la config générée par mon ancienne image de test etaient deja la ?

Non, tout était propre.
Pas de container présent, dossier /var/lib/gladysassistant effacé.
J’ai juste fait un Docker pull sur l’image citée plus haut
Puis un Docker run avec les paramètres habituels (proposés sur la page Docker de gladysassistant.com/fr)
Création de compte/maison etc. fictifs
Ajout et config du dongle sonoff et services.
Ajout du périphérique ZigBee
Test
Arrêt des containers
Suppression des dossiers/sous dossiers comme montré dans le commentaire précédent :wink:

2 Likes

Hey hey bonjour,
j’ai tenté une autre modification, je te laisse réessayer tout comme tu sais faire :wink:
N’oublies pas de bien supprimer le container et l’image de ton docker :slight_smile:

2 Likes

Ça fonctionne !
Les logs arrivent…

Gladys:

pi@Nichoir2:~ $ docker logs gladys

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

2022-08-26T18:44:34+0200 <info> 20210129155044-multi-user.js:23 (Object.up) Multi-user migration: 0 users found
2022-08-26T18:44:35+0200 <info> job.purge.js:17 (Job.purge) Deleting all background jobs created before = Fri Aug 19 2022 18:44:35 GMT+0200 (Central European Summer Time)
Initialising OpenZWave 1.6.0 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2022-08-26T18:44:43+0200 <info> index.js:14 (Object.start) starting Alexa service
2022-08-26T18:44:43+0200 <info> index.js:14 (Object.start) starting GoogleActions service
2022-08-26T18:44:43+0200 <info> init.js:31 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle not attached
2022-08-26T18:44:43+0200 <info> index.js:18 (Object.start) Starting TP-Link service
2022-08-26T18:44:43+0200 <info> index.js:17 (Object.start) Starting eWeLink service
2022-08-26T18:44:43+0200 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2022-08-26T18:44:43+0200 <info> index.js:15 (Object.start) Starting Bluetooth service
2022-08-26T18:44:44+0200 <error> index.js:20 (process.<anonymous>) uncaughtException catched: uncaughtException
2022-08-26T18:44:44+0200 <error> index.js:21 (process.<anonymous>) Error: ENODEV, No such device
    at Hci.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
    at NobleBindings.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
    at /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/noble.js:60:24
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  errno: 19,
  code: 'ENODEV',
  syscall: 'bind'
}
2022-08-26T18:44:44+0200 <info> index.js:15 (Object.start) Starting Tasmota service
2022-08-26T18:44:44+0200 <info> index.js:16 (Object.start) Starting zwave service
2022-08-26T18:44:45+0200 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2022-08-26T18:44:45+0200 <info> index.js:14 (Object.start) Starting Xiaomi service
2022-08-26T18:44:45+0200 <info> index.js:13 (Object.start) Starting usb service
2022-08-26T18:44:45+0200 <info> index.js:19 (Object.start) Starting Telegram service
2022-08-26T18:44:45+0200 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2022-08-26T18:44:45+0200 <info> index.js:16 (Object.start) Starting RTSP service
2022-08-26T18:44:45+0200 <info> index.js:18 (Object.start) Starting Philips Hue service
2022-08-26T18:44:45+0200 <info> index.js:16 (Object.start) Starting MQTT service
2022-08-26T18:44:45+0200 <info> updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...2022-08-26T18:44:45+0200 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.2022-08-26T18:44:45+0200 <info> index.js:20 (Object.start) Starting Open Weather service
2022-08-26T18:44:45+0200 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2022-08-26T18:44:45+0200 <info> index.js:64 (Object.start) Starting CalDAV service
2022-08-26T18:44:45+0200 <info> index.js:21 (Object.start) Starting example service
2022-08-26T18:44:46+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval hourly
2022-08-26T18:44:46+0200 <info> index.js:63 (Server.<anonymous>) Server listening on port 8088
2022-08-26T18:44:53+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval hourly
2022-08-26T18:44:53+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval daily
2022-08-26T18:45:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:45:00 GMT
2022-08-26T18:45:00+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval daily
2022-08-26T18:45:00+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval monthly
2022-08-26T18:45:06+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval monthly
2022-08-26T18:46:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:46:00 GMT
2022-08-26T18:47:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:47:00 GMT
2022-08-26T18:48:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:48:00 GMT
2022-08-26T18:49:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:49:00 GMT
2022-08-26T18:50:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:50:00 GMT
2022-08-26T18:51:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:51:00 GMT
2022-08-26T18:51:56+0200 <info> scene.dailyUpdate.js:58 () Sunrise today is at 6:48 today, in your timezone = Europe/Paris2022-08-26T18:51:56+0200 <info> scene.dailyUpdate.js:59 () Sunset today is at 20:42 today, in your timezone = Europe/Paris2022-08-26T18:51:56+0200 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2022-08-26T18:51:56+0200 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 2 hours.
2022-08-26T18:52:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:52:00 GMT
2022-08-26T18:53:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:53:00 GMT
2022-08-26T18:53:45+0200 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2022-08-26T18:53:45+0200 <info> installMqttContainer.js:28 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...
2022-08-26T18:53:45+0200 <info> installMqttContainer.js:29 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:2 image...
2022-08-26T18:53:54+0200 <info> installMqttContainer.js:33 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2022-08-26T18:53:54+0200 <info> installMqttContainer.js:40 (Zigbee2mqttManager.installMqttContainer) Creating container with data in "/var/lib/gladysassistant" on host...
2022-08-26T18:53:58+0200 <info> installMqttContainer.js:54 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-08-26T18:54:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:54:00 GMT
2022-08-26T18:54:04+0200 <info> installMqttContainer.js:61 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...2022-08-26T18:54:05+0200 <info> installMqttContainer.js:70 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-08-26T18:54:11+0200 <info> installMqttContainer.js:74 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started and configured
2022-08-26T18:54:11+0200 <info> installZ2mContainer.js:33 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2022-08-26T18:54:11+0200 <info> installZ2mContainer.js:34 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2022-08-26T18:54:13+0200 <info> installZ2mContainer.js:37 (Zigbee2mqttManager.installZ2mContainer) Configuration of Device /dev/ttyUSB0
2022-08-26T18:54:13+0200 <info> installZ2mContainer.js:42 (Zigbee2mqttManager.installZ2mContainer) Creation of container...
2022-08-26T18:54:15+0200 <info> installZ2mContainer.js:45 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed and configured as Docker container
2022-08-26T18:54:15+0200 <info> installZ2mContainer.js:58 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2022-08-26T18:54:15+0200 <info> installZ2mContainer.js:72 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container is starting...
2022-08-26T18:54:21+0200 <info> installZ2mContainer.js:78 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2022-08-26T18:54:21+0200 <info> connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker...
2022-08-26T18:54:22+0200 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2022-08-26T18:54:22+0200 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2022-08-26T18:55:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:55:00 GMT
2022-08-26T18:56:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:56:00 GMT
2022-08-26T18:56:09+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T18:56:09+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T18:56:09+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T18:56:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T18:56:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T18:56:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T18:56:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T18:56:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T18:56:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T18:56:27+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T18:56:27+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T18:56:27+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T18:56:27+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T18:56:27+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T18:56:27+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T18:56:28+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T18:56:28+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T18:56:28+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T18:56:28+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T18:56:28+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T18:56:28+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T18:57:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 16:57:00 GMT
2022-08-26T18:57:06+0200 <info> index.js:25 (shutdown) SIGTERM received.
2022-08-26T18:57:06+0200 <info> index.js:31 (shutdown) Closing database connection.

> gladys-server@ start:prod /src/server
> cross-env NODE_ENV=production node index.js

2022-08-26T18:59:39+0200 <info> job.purge.js:17 (Job.purge) Deleting all background jobs created before = Fri Aug 19 2022 18:59:39 GMT+0200 (Central European Summer Time)
Initialising OpenZWave 1.6.0 binary addon for Node.JS.
        OpenZWave Security API is ENABLED
        ZWave device db    : /usr/local/etc/openzwave
        User settings path : /src/server/services/zwave/node_modules/openzwave-shared/build/Release/../../
        Option Overrides : --Logging false --ConsoleOutput false --SaveConfiguration true
2022-08-26T18:59:46+0200 <info> index.js:14 (Object.start) starting Alexa service
2022-08-26T18:59:46+0200 <info> index.js:20 (Object.start) Starting Open Weather service
2022-08-26T18:59:46+0200 <info> service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2022-08-26T18:59:46+0200 <info> index.js:64 (Object.start) Starting CalDAV service
2022-08-26T18:59:46+0200 <info> index.js:16 (Object.start) Starting MQTT service
2022-08-26T18:59:46+0200 <info> updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes...2022-08-26T18:59:46+0200 <info> service.start.js:40 (Service.start) Service mqtt is not configured, so it was not started.2022-08-26T18:59:46+0200 <info> index.js:14 (Object.start) starting GoogleActions service
2022-08-26T18:59:47+0200 <info> init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2022-08-26T18:59:47+0200 <info> installMqttContainer.js:28 (Zigbee2mqttManager.installMqttContainer) MQTT broker is being installed as Docker container...
2022-08-26T18:59:47+0200 <info> installMqttContainer.js:29 (Zigbee2mqttManager.installMqttContainer) Pulling eclipse-mosquitto:2 image...
2022-08-26T18:59:50+0200 <info> installMqttContainer.js:33 (Zigbee2mqttManager.installMqttContainer) Preparing broker environment...
2022-08-26T18:59:50+0200 <info> installMqttContainer.js:40 (Zigbee2mqttManager.installMqttContainer) Creating container with data in "/var/lib/gladysassistant" on host...
2022-08-26T18:59:51+0200 <info> installMqttContainer.js:54 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-08-26T18:59:57+0200 <info> installMqttContainer.js:61 (Zigbee2mqttManager.installMqttContainer) Creating user/pass...2022-08-26T18:59:58+0200 <info> installMqttContainer.js:70 (Zigbee2mqttManager.installMqttContainer) MQTT broker is restarting...
2022-08-26T19:00:04+0200 <info> installMqttContainer.js:74 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started and configured
2022-08-26T19:00:04+0200 <info> installZ2mContainer.js:33 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt is being installed as Docker container...
2022-08-26T19:00:04+0200 <info> installZ2mContainer.js:34 (Zigbee2mqttManager.installZ2mContainer) Pulling koenkk/zigbee2mqtt:latest image...
2022-08-26T19:00:06+0200 <info> installZ2mContainer.js:37 (Zigbee2mqttManager.installZ2mContainer) Configuration of Device /dev/ttyUSB0
2022-08-26T19:00:06+0200 <info> installZ2mContainer.js:42 (Zigbee2mqttManager.installZ2mContainer) Creation of container...
2022-08-26T19:00:08+0200 <info> installZ2mContainer.js:45 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt successfully installed and configured as Docker container
2022-08-26T19:00:08+0200 <info> installZ2mContainer.js:58 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2022-08-26T19:00:08+0200 <info> installZ2mContainer.js:72 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container is starting...
2022-08-26T19:00:13+0200 <info> installZ2mContainer.js:78 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2022-08-26T19:00:13+0200 <info> connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker...
2022-08-26T19:00:14+0200 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2022-08-26T19:00:14+0200 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2022-08-26T19:00:14+0200 <info> index.js:18 (Object.start) Starting TP-Link service
2022-08-26T19:00:14+0200 <info> index.js:17 (Object.start) Starting eWeLink service
2022-08-26T19:00:14+0200 <info> service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2022-08-26T19:00:14+0200 <info> index.js:15 (Object.start) Starting Bluetooth service
2022-08-26T19:00:15+0200 <error> index.js:20 (process.<anonymous>) uncaughtException catched: uncaughtException
2022-08-26T19:00:15+0200 <error> index.js:21 (process.<anonymous>) Error: ENODEV, No such device
    at Hci.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:100:35)
    at NobleBindings.init (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:78:13)
    at /src/server/services/bluetooth/node_modules/@abandonware/noble/lib/noble.js:60:24
    at processTicksAndRejections (internal/process/task_queues.js:77:11) {
  errno: 19,
  code: 'ENODEV',
  syscall: 'bind'
}
2022-08-26T19:00:16+0200 <info> index.js:15 (Object.start) Starting Tasmota service
2022-08-26T19:00:16+0200 <info> index.js:16 (Object.start) Starting zwave service
2022-08-26T19:00:16+0200 <info> service.start.js:40 (Service.start) Service zwave is not configured, so it was not started.
2022-08-26T19:00:16+0200 <info> index.js:14 (Object.start) Starting Xiaomi service
2022-08-26T19:00:16+0200 <info> index.js:13 (Object.start) Starting usb service
2022-08-26T19:00:16+0200 <info> index.js:19 (Object.start) Starting Telegram service
2022-08-26T19:00:16+0200 <info> service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2022-08-26T19:00:16+0200 <info> index.js:16 (Object.start) Starting RTSP service
2022-08-26T19:00:16+0200 <info> index.js:18 (Object.start) Starting Philips Hue service
2022-08-26T19:00:16+0200 <info> index.js:21 (Object.start) Starting example service
2022-08-26T19:00:16+0200 <info> scene.dailyUpdate.js:58 () Sunrise today is at 6:48 today, in your timezone = Europe/Paris2022-08-26T19:00:16+0200 <info> scene.dailyUpdate.js:59 () Sunset today is at 20:42 today, in your timezone = Europe/Paris2022-08-26T19:00:16+0200 <info> scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2022-08-26T19:00:16+0200 <info> scene.dailyUpdate.js:81 () Sunset is scheduled, in 2 hours.
2022-08-26T19:00:17+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval hourly
2022-08-26T19:00:17+0200 <info> index.js:63 (Server.<anonymous>) Server listening on port 8088
2022-08-26T19:00:25+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval hourly
2022-08-26T19:00:25+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval daily
2022-08-26T19:00:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T19:00:26+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T19:00:32+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval daily
2022-08-26T19:00:32+0200 <info> device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval monthly
2022-08-26T19:00:39+0200 <info> device.calculateAggregate.js:105 (ChildProcess.<anonymous>) device.calculateAggregate: Finishing processing for interval monthly
2022-08-26T19:01:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 17:01:00 GMT
2022-08-26T19:01:03+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T19:01:03+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T19:01:03+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T19:01:03+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T19:01:03+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T19:01:03+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T19:01:04+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T19:01:04+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T19:01:04+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T19:01:04+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature linkquality not configured in Gladys.
2022-08-26T19:01:04+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update not configured in Gladys.
2022-08-26T19:01:04+0200 <warn> handleMqttMessage.js:101 () Zigbee2mqtt device 0x00124b0024c06f1c, feature update_available not configured in Gladys.
2022-08-26T19:02:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 17:02:00 GMT
2022-08-26T19:03:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 17:03:00 GMT
2022-08-26T19:04:00+0200 <info> scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 26 Aug 2022 17:04:00 GMT
pi@Nichoir2:~ $

Installation et suppression :

pi@Nichoir2:~ $ docker ps -a
CONTAINER ID   IMAGE                 COMMAND                  CREATED       STATUS       PORTS                                                              NAMES
pi@Nichoir2:~ $ ls /var/lib                                  adguard     dhcp       man-db  polkit-1     ucf              alsa        dhcpcd     misc    private      usb_modeswitch   apache2     docker     motion  python       vim              apt         dpkg       nfs     raspberrypi                   containerd  git        pam     sudo                          dbus        logrotate  php     systemd
pi@Nichoir2:~ $ docker run -d --log-driver json-file --log-opt max-size=10m --cgroupns=host --restart=always --privileged --network=host --name gladys -e NODE_ENV=production -e SERVER_PORT=8088 -e TZ=Europe/Paris -e SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistant:/var/lib/gladysassistant -v /dev:/dev -v /run/udev:/run/udev:ro atrovato/gladys:zigbee2mqtt
Unable to find image 'atrovato/gladys:zigbee2mqtt' locally
zigbee2mqtt: Pulling from atrovato/gladys
c6556b3b6858: Already exists
03a5d5e3efc3: Pull complete
49e084b1c42c: Pull complete
2375b3b7af35: Pull complete
969b14474fbc: Pull complete
f51fe98a8646: Pull complete
ca5405dd3a9c: Pull complete
ff9801df0f01: Pull complete
6830d33b7911: Pull complete
4f4fb700ef54: Pull complete
812d1e8d26b2: Pull complete
846852f36f43: Pull complete
b050eef54dd7: Pull complete
Digest: sha256:4f6ccdfdf75da02ecfd9a55209e9505fde9dee85705bf0aaab65d736a45fb544
Status: Downloaded newer image for atrovato/gladys:zigbee2mqtt
af7ee97862bb5c50867252125da59da869c73800485c421a1bf4c00c9cbeecdf

Après, configuration de Gladys :

pi@Nichoir2:~ $ docker ps -a                                 CONTAINER ID   IMAGE                         COMMAND                  CREATED         STATUS         PORTS                                                              NAMES
af7ee97862bb   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   2 minutes ago   Up 2 minutes                                                                      gladys
pi@Nichoir2:~ $ docker ps                                    CONTAINER ID   IMAGE                         COMMAND                  CREATED          STATUS          PORTS                                                              NAMES
03dcc3670763   koenkk/zigbee2mqtt:latest     "docker-entrypoint.s…"   2 minutes ago    Up 2 minutes                                                                       gladys-z2m-zigbee2mqtt
79e88a87cebe   eclipse-mosquitto:2           "/docker-entrypoint.…"   2 minutes ago    Up 2 minutes                                                                       gladys-z2m-mqtt
af7ee97862bb   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   12 minutes ago   Up 12 minutes                                                                      gladys

Suppression, restauration:

pi@Nichoir2:~ $ docker stop gladys
gladys
pi@Nichoir2:~ $ docker stop gladys-z2m-mqtt
gladys-z2m-mqtt
pi@Nichoir2:~ $ docker stop gladys-z2m-zigbee2mqtt
gladys-z2m-zigbee2mqtt
pi@Nichoir2:~ $ docker rm gladys-z2m-zigbee2mqtt
gladys-z2m-zigbee2mqtt
pi@Nichoir2:~ $ docker rm gladys-z2m-mqtt
gladys-z2m-mqtt
pi@Nichoir2:~ $ docker ps -a
CONTAINER ID   IMAGE                         COMMAND                  CREATED          STATUS                          PORTS                                                              NAMES
af7ee97862bb   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   15 minutes ago   Exited (0) About a minute ago         gladys
pi@Nichoir2:~ $ docker start gladys
gladys
pi@Nichoir2:~ $ docker ps
CONTAINER ID   IMAGE                         COMMAND                  CREATED          STATUS              PORTS                                                              NAMES
4c2287d6de77   koenkk/zigbee2mqtt:latest     "docker-entrypoint.s…"   20 seconds ago   Up 17 seconds                                                                          gladys-z2m-zigbee2mqtt
825510b5fb4a   eclipse-mosquitto:2           "/docker-entrypoint.…"   36 seconds ago   Up 26 seconds                                                                          gladys-z2m-mqtt
af7ee97862bb   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   16 minutes ago   Up About a minute                                                                      gladys
pi@Nichoir2:~ $ docker ps
CONTAINER ID   IMAGE                         COMMAND                  CREATED              STATUS              PORTS                                                              NAMES4c2287d6de77   koenkk/zigbee2mqtt:latest     "docker-entrypoint.s…"   About a minute ago   Up About a minute                                                                      gladys-z2m-zigbee2mqtt
825510b5fb4a   eclipse-mosquitto:2           "/docker-entrypoint.…"   About a minute ago   Up About a minute                                                                      gladys-z2m-mqtt
af7ee97862bb   atrovato/gladys:zigbee2mqtt   "docker-entrypoint.s…"   17 minutes ago       Up 2 minutes                                                                           gladys
pi@Nichoir2:~ $

Les containers:
MQTT:

pi@Nichoir2:~ $ docker logs gladys-z2m-mqtt
1661533192: mosquitto version 2.0.15 starting
1661533192: Config loaded from /mosquitto/config/mosquitto.conf.
1661533192: Opening ipv4 listen socket on port 1884.
1661533192: Opening ipv6 listen socket on port 1884.
1661533192: mosquitto version 2.0.15 running
1661533198: mosquitto version 2.0.15 terminating
1661533199: mosquitto version 2.0.15 starting
1661533199: Config loaded from /mosquitto/config/mosquitto.conf.
1661533199: Opening ipv4 listen socket on port 1884.
1661533199: Opening ipv6 listen socket on port 1884.
1661533199: mosquitto version 2.0.15 running
1661533214: New connection from 127.0.0.1:44118 on port 1884.1661533214: New client connected from 127.0.0.1:44118 as gladys-main-instance-732597 (p2, c1, k60, u'gladys').
1661533226: New connection from 127.0.0.1:51906 on port 1884.1661533226: New client connected from 127.0.0.1:51906 as mqttjs_dcbffe1a (p2, c1, k60, u'z2m').

ZigBee

pi@Nichoir2:~ $ docker logs gladys-z2m-zigbee2mqtt
Using '/app/data' as data directory
Zigbee2MQTT:info  2022-08-26 17:00:22: Logging to console and directory: '/app/data/log/2022-08-26.17-00-22' filename: log.txt
Zigbee2MQTT:info  2022-08-26 17:00:22: Starting Zigbee2MQTT version 1.27.0 (commit #a9b8808)
Zigbee2MQTT:info  2022-08-26 17:00:22: Starting zigbee-herdsman (0.14.46)
Zigbee2MQTT:info  2022-08-26 17:00:25: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2022-08-26 17:00:25: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20210708,"transportrev":2},"type":"zStack3x0"}'
Zigbee2MQTT:info  2022-08-26 17:00:25: Currently 1 devices are joined:
Zigbee2MQTT:info  2022-08-26 17:00:25: 0x00124b0024c06f1c (0x00124b0024c06f1c): ZBMINI-L - SONOFF Zigbee smart switch (no neutral) (EndDevice)
Zigbee2MQTT:info  2022-08-26 17:00:25: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2022-08-26 17:00:25: Connecting to MQTT server at mqtt://localhost:1884
Zigbee2MQTT:info  2022-08-26 17:00:26: Connected to MQTT server
Zigbee2MQTT:info  2022-08-26 17:00:26: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
Zigbee2MQTT:info  2022-08-26 17:00:26: Started frontend on port 0.0.0.0:8080
Zigbee2MQTT:info  2022-08-26 17:00:26: MQTT publish: topic 'zigbee2mqtt/0x00124b0024c06f1c', payload '{"state":"OFF","update":{"state":"idle"},"update_available":false}'
Zigbee2MQTT:info  2022-08-26 17:01:03: MQTT publish: topic 'zigbee2mqtt/0x00124b0024c06f1c', payload '{"linkquality":54,"state":"ON","update":{"state":"idle"},"update_available":false}'
Zigbee2MQTT:info  2022-08-26 17:01:03: MQTT publish: topic 'zigbee2mqtt/0x00124b0024c06f1c', payload '{"linkquality":69,"state":"ON","update":{"state":"idle"},"update_available":false}'
Zigbee2MQTT:info  2022-08-26 17:01:04: MQTT publish: topic 'zigbee2mqtt/0x00124b0024c06f1c', payload '{"linkquality":69,"state":"OFF","update":{"state":"idle"},"update_available":false}'
Zigbee2MQTT:info  2022-08-26 17:01:04: MQTT publish: topic 'zigbee2mqtt/0x00124b0024c06f1c', payload '{"linkquality":66,"state":"OFF","update":{"state":"idle"},"update_available":false}'
pi@Nichoir2:~ $

Désolé, cest pas tout dans l’ordre mais je suis sur un smartphone :smiley:

1 Like

Je suis sur smartphone aussi, j’ai surtout lu « ça fonctionne » :smiley:
J’analyserai les logs demain.
Merci

1 Like