Oui, c’est d’autant plus surprenant que si je lance npm start manuellement, toute les données remontent bien, je les vois dans Mqtt.
Par contre j’ai comme identifiant « jeedom » dans la configuration de MQTT
humm…
Genre en manuel, les messages sont visibles depuis MQTTexplorer par exemple ???
A ce stade, service ou manuel on passe par la même config
Oui, je comprends, je pensais que ça venait peut-être des droits comme je suis obligé de lancer npm start avec la commande sudo dans la console.
mais il me semble avoir déverrouillé les droits sur ce répertoire :
elkapo@ASUS:/opt/zigbee2mqtt$ ls -l
total 936
drwxrwxrwx 3 elkapo elkapo 4096 nov. 21 12:00 data
drwxrwxrwx 2 elkapo elkapo 4096 nov. 7 01:51 docker
drwxrwxrwx 2 elkapo elkapo 4096 nov. 7 01:51 images
-rwxrwxrwx 1 elkapo elkapo 1263 nov. 7 01:51 index.js
drwxrwxrwx 4 elkapo elkapo 4096 nov. 7 01:51 lib
-rwxrwxrwx 1 elkapo elkapo 35141 nov. 7 01:51 LICENSE
drwxrwxrwx 519 elkapo elkapo 20480 nov. 20 12:08 node_modules
-rwxrwxrwx 1 elkapo elkapo 852886 nov. 7 01:51 npm-shrinkwrap.json
-rwxrwxrwx 1 elkapo elkapo 1867 nov. 7 01:51 package.json
-rwxrwxrwx 1 elkapo elkapo 5739 nov. 7 01:51 README.md
drwxrwxrwx 2 elkapo elkapo 4096 nov. 7 01:51 scripts
drwxrwxrwx 5 elkapo elkapo 4096 nov. 7 01:51 test
-rwxrwxrwx 1 elkapo elkapo 708 nov. 7 01:51 update.sh
Faire
sudo xxxxx
ou être root et faire
xxxxx
C’est équivalent donc c’est pas la meilleure piste à explorer
si tu fais :
netstat -na |grep 1883
ça affiche quoi ?
Merci pour ta patience,
elkapo@ASUS:/opt/zigbee2mqtt$ netstat -na |grep 1883
tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:51166 127.0.0.1:1883 ESTABLISHED
tcp 0 0 127.0.0.1:1883 127.0.0.1:51166 ESTABLISHED
tcp6 0 0 :::1883 :::* LISTEN
tcp6 0 0 ::1:42436 ::1:1883 ESTABLISHED
tcp6 0 0 ::1:1883 ::1:42436 ESTABLISHED
unix 2 [ ] DGRAM 18839
De rien
Bon là comme ça j’ai pas d’idée… port 1883 est là donc mosquitto aussi…
Tu es certains de voir les messages : ceux avec une date actuelle, pas juste l’historique avec MQTTExplorer ?
j’ai par exemple un bouton xiaomi et lorsque je lance « sudo npm start » dans une console, je vois bien mes appuis instantanément ainsi que les remontées de mes sondes, c’est la troisième installation que je fais avec deux tutos de sites différents mais qui sont similaires et j’ai toujours le même problème. Je pourrais laisser la console ouverte et tout marcherait très bien, mais en cas de coupure de courant et de reboot de la machine, je pers mes capteurs. Étant à la campagne, c’est très fréquent l’hiver… Si on rajoute à ça une épouse frileuse, il me faut trouver une solution…
Sur le principe du service, il n’y même pas de discussion à avoir. Sans lui c’est presque inutile.
Après il y a des tutos pour changer de femme ou la réchauffer mais c’est pas non plus le sujet ici. 
Je reviens quand même sur cette histoire de date/historique… 11h25 et un post à 11h5X ça me parait pas un bon exemple.
(Re)Faite les tests avec MQTTexplorer, après un reboot par exemple…
Effectivement, je n’ai pas de log plus récent, j’ai tenté en arrêtant le service et en le redémarrant et en lançant la commande manuellement, mais pas de changement, je redémarre la machine pour y voir plus clair.
J’adore, mais nous approchons de la famille nombreuse et donc d’avoir moins de temps pour m’occuper de la domotique et il fera encore plus froid… Bref la spirale infernale 
1 « J'aime »
Il doit y avoir un décalage entre la génération du log et son écriture sur le disque car ils sont apparus au redémarrage, j’ai celui-ci:
debug 2020-11-21 12:48:03: Loaded state from file /opt/zigbee2mqtt/data/state.json
info 2020-11-21 12:48:03: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-11-21.12-48-02' filename: log.txt
debug 2020-11-21 12:48:03: Removing old log directory '/opt/zigbee2mqtt/data/log/2020-11-20.17-01-50'
error 2020-11-21 12:49:10: Failed to call 'OnEvent' 'stop' (TypeError: Cannot read property 'getDevices' of undefined
at Zigbee.getClients (/opt/zigbee2mqtt/lib/zigbee.js:136:30)
at OnEvent.stop (/opt/zigbee2mqtt/lib/extension/onEvent.js:23:42)
at Controller.callExtensionMethod (/opt/zigbee2mqtt/lib/controller.js:378:44))
debug 2020-11-21 12:49:10: Saving state to file /opt/zigbee2mqtt/data/state.json
error 2020-11-21 12:49:10: Not connected to MQTT server!
error 2020-11-21 12:49:10: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: 'offline
info 2020-11-21 12:49:10: Disconnecting from MQTT server
Celui-ci est avec npm start en manuel:
debug 2020-11-21 12:49:19: Loaded state from file /opt/zigbee2mqtt/data/state.json
info 2020-11-21 12:49:19: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-11-21.12-49-18' filename: log.txt
debug 2020-11-21 12:49:19: Removing old log directory '/opt/zigbee2mqtt/data/log/2020-11-21.09-08-56'
debug 2020-11-21 12:49:19: Removing old log directory '/opt/zigbee2mqtt/data/log/2020-11-20.17-01-50'
debug 2020-11-21 12:49:19: Removing old log directory '/opt/zigbee2mqtt/data/log/2020-11-20.16-58-54'
info 2020-11-21 12:49:19: Starting Zigbee2MQTT version 1.16.1 (commit #6b32f30)
info 2020-11-21 12:49:19: Starting zigbee-herdsman...
debug 2020-11-21 12:49:19: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null},"backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","databasePath":"/opt/zigbee2mqtt/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyACM0"}}'
info 2020-11-21 12:49:21: zigbee-herdsman started
info 2020-11-21 12:49:21: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"}'
debug 2020-11-21 12:49:21: Zigbee network parameters: {"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754}
info 2020-11-21 12:49:21: Currently 11 devices are joined:
info 2020-11-21 12:49:21: 0x00158d000288e09f (0x00158d000288e09f): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d0002c47e23 (0x00158d0002c47e23): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
info 2020-11-21 12:49:21: 0x00158d00033b3ba9 (0x00158d00033b3ba9): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d00036b477a (0x00158d00036b477a): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d00033b4c04 (0x00158d00033b4c04): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d00033b3aa5 (0x00158d00033b3aa5): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d00039fbf7c (0x00158d00039fbf7c): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d0002bf8ca6 (0x00158d0002bf8ca6): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d00033b3048 (0x00158d00033b3048): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d00033b4bf2 (0x00158d00033b4bf2): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 12:49:21: 0x00158d000288dd17 (0x00158d000288dd17): Not supported (Unknown)
warn 2020-11-21 12:49:21: `permit_join` set to `true` in configuration.yaml.
warn 2020-11-21 12:49:21: Allowing new devices to join.
warn 2020-11-21 12:49:21: Set `permit_join` to `false` once you joined all devices.
info 2020-11-21 12:49:21: Zigbee: allowing new devices to join.
info 2020-11-21 12:49:21: Connecting to MQTT server at mqtt://localhost
info 2020-11-21 12:49:21: Connected to MQTT server
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d000288e09f', payload '{"battery":100,"occupancy":false,"voltage":3225}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d0002c47e23', payload '{"battery":100,"voltage":3152}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b3ba9', payload '{"battery":100,"humidity":63.39,"temperature":18.39,"voltage":3055}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d00036b477a', payload '{"battery":38,"humidity":48.23,"temperature":18.44,"voltage":2875}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b4c04', payload '{"battery":97,"humidity":42.5,"temperature":19.25,"voltage":2995}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b3aa5', payload '{"battery":91,"humidity":62.05,"temperature":19.61,"voltage":2985}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d00039fbf7c', payload '{"battery":97,"contact":true,"voltage":2995}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d0002bf8ca6', payload '{"battery":74,"contact":true,"voltage":2955}'
info 2020-11-21 12:49:21: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b3048', payload '{"battery":86,"humidity":48.16,"temperature":19.16,"voltage":2975}'
info 2020-11-21 12:49:22: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b4bf2', payload '{"battery":86,"humidity":52.2,"temperature":18.56,"voltage":2975}'
info 2020-11-21 12:49:22: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"6b32f30","coordinator":{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"debug","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.16.1"}'
debug 2020-11-21 12:49:55: Saving state to file /opt/zigbee2mqtt/data/state.json
info 2020-11-21 12:49:55: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'
info 2020-11-21 12:49:55: Disconnecting from MQTT server
info 2020-11-21 12:49:55: zigbee-herdsman stopped
et le dernier en date en fermant la console :
debug 2020-11-21 12:51:04: Loaded state from file /opt/zigbee2mqtt/data/state.json
info 2020-11-21 12:51:04: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-11-21.12-51-03' filename: log.txt
debug 2020-11-21 12:51:04: Removing old log directory '/opt/zigbee2mqtt/data/log/2020-11-21.11-01-47'
debug 2020-11-21 12:56:05: Saving state to file /opt/zigbee2mqtt/data/state.json
OK, là le doute est moindre… Quelques remarques :
Les tous premiers message qui apparaissent en mode manuel, sont liées à la fin du fichier de configuration avec les références/Friendly-name => c’est pas une vraie communication entre les elements, mais uniquement zigbee2mqtt qui mets à jours les informations pour la suite.
ça, ça m’ennuie, ça ressemble à un souci d’accès à la clé /dev/ttyACM0
La seule explication qu’il ait 2 profils npm qui trainent… Pour en être sur ça vaudrait le coup de créer un utilisateur temporaire, de se connecter avec et de lancer le sudo npm start dans /opt/zigbee2mqtt
voilà le log avec le nouvel utilisateur :
debug 2020-11-21 13:40:48: Loaded state from file /opt/zigbee2mqtt/data/state.json
info 2020-11-21 13:40:48: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2020-11-21.13-40-47' filename: log.txt
debug 2020-11-21 13:40:48: Removing old log directory '/opt/zigbee2mqtt/data/log/2020-11-21.11-18-10'
debug 2020-11-21 13:40:48: Removing old log directory '/opt/zigbee2mqtt/data/log/2020-11-21.11-01-47'
info 2020-11-21 13:40:48: Starting Zigbee2MQTT version 1.16.1 (commit #6b32f30)
info 2020-11-21 13:40:48: Starting zigbee-herdsman...
debug 2020-11-21 13:40:48: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null},"backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","databasePath":"/opt/zigbee2mqtt/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyACM0"}}'
info 2020-11-21 13:40:51: zigbee-herdsman started
info 2020-11-21 13:40:51: Coordinator firmware version: '{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"}'
debug 2020-11-21 13:40:51: Zigbee network parameters: {"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754}
info 2020-11-21 13:40:51: Currently 11 devices are joined:
info 2020-11-21 13:40:51: 0x00158d000288e09f (0x00158d000288e09f): RTCGQ01LM - Xiaomi MiJia human body movement sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d0002c47e23 (0x00158d0002c47e23): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)
info 2020-11-21 13:40:51: 0x00158d00033b3ba9 (0x00158d00033b3ba9): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d00036b477a (0x00158d00036b477a): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d00033b4c04 (0x00158d00033b4c04): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d00033b3aa5 (0x00158d00033b3aa5): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d00039fbf7c (0x00158d00039fbf7c): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d0002bf8ca6 (0x00158d0002bf8ca6): MCCGQ01LM - Xiaomi MiJia door & window contact sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d00033b3048 (0x00158d00033b3048): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d00033b4bf2 (0x00158d00033b4bf2): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)
info 2020-11-21 13:40:51: 0x00158d000288dd17 (0x00158d000288dd17): Not supported (Unknown)
warn 2020-11-21 13:40:51: `permit_join` set to `true` in configuration.yaml.
warn 2020-11-21 13:40:51: Allowing new devices to join.
warn 2020-11-21 13:40:51: Set `permit_join` to `false` once you joined all devices.
info 2020-11-21 13:40:51: Zigbee: allowing new devices to join.
info 2020-11-21 13:40:51: Connecting to MQTT server at mqtt://localhost
info 2020-11-21 13:40:51: Connected to MQTT server
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d000288e09f', payload '{"battery":100,"occupancy":false,"voltage":3225}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d0002c47e23', payload '{"battery":100,"voltage":3152}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b3ba9', payload '{"battery":100,"humidity":63.39,"temperature":18.39,"voltage":3055}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d00036b477a', payload '{"battery":38,"humidity":48.23,"temperature":18.44,"voltage":2875}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b4c04', payload '{"battery":97,"humidity":42.5,"temperature":19.25,"voltage":2995}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b3aa5', payload '{"battery":91,"humidity":62.05,"temperature":19.61,"voltage":2985}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d00039fbf7c', payload '{"battery":97,"contact":true,"voltage":2995}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d0002bf8ca6', payload '{"battery":74,"contact":true,"voltage":2955}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b3048', payload '{"battery":86,"humidity":48.16,"temperature":19.16,"voltage":2975}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/0x00158d00033b4bf2', payload '{"battery":86,"humidity":52.2,"temperature":18.56,"voltage":2975}'
info 2020-11-21 13:40:51: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"commit":"6b32f30","coordinator":{"meta":{"maintrel":3,"majorrel":2,"minorrel":6,"product":0,"revision":20190608,"transportrev":2},"type":"zStack12"},"log_level":"debug","network":{"channel":11,"extendedPanID":"0xdddddddddddddddd","panID":6754},"permit_join":true,"version":"1.16.1"}'
Bon je vois pas…
Si tu lances bien uniquement la commande npm start en direct (et pas dans un script ou autre chose)… là je séche.
Merci beaucoup pour l’aide, je vais continuer ma prospection…
Bonjour j’ai exactement le meme souci
Avez vous trouvé une solution depuis ?
Merci d’avance
Bonjour,
Réutiliser un post vieux de 3 ans n’est pas une bonne idée surtout sans information sur votre system, version de jeedom, plugin utilisé et log en debug, copie de la page santé.
Merci d’ouvrir un sujet en donnant les informations manquantes
1 « J'aime »