Avant toute chose merci de (re)prendre connaissance de la charte et de la respecter.
Pour résumer :
- Avant de poser une question, je cherche si la réponse existe
- Je suis poli, courtois et je respecte tout un chacun sur le forum
- Si un post m'agace : je m'en éloigne plutôt que de répondre d'une façon qui pourrait être mal interprétée


Il n'est jamais du luxe que de rappeler des choses simples :
Courtoisie, amabilité, politesse et bonne humeur sont les maîtres mots pour un forum sympathique, bienveillant et accueillant :)

Le groupe des Helpers est present pour vous aidez, n'hésitez pas à poser des questions ;)

Toute la communauté vous remercie

/!\ L’ancien forum passera en lecture seule en janvier 2020./!\
Merci de vous rendre sur https://community.jeedom.com maintenant pour vos prochains postes ;)

Plugin jMQTT

Retrouvez ici des sujets concernant le protocole MQTT et les modules domotiques de type MQTT utilisés avec JEEDOM
/!\ Plugin MQTT non officiel
weado
Timide
Messages : 205
Inscription : 15 janv. 2017, 22:19

Re: Plugin jMQTT

Message par weado » 08 févr. 2019, 09:29

Pour finir, le topic crée :
topic.PNG
topic.PNG (17.07 Kio) Consulté 412 fois

weado
Timide
Messages : 205
Inscription : 15 janv. 2017, 22:19

Re: Plugin jMQTT

Message par weado » 08 févr. 2019, 13:59

Bon, suite à un échange avec Loic74 dans cette discussion (viewtopic.php?f=96&t=39063&p=695489#p695449) je comprend mieux mon erreur :
Même si on est dans topic sous Jeedom (dans mon cas mqtt_display), il est nécessaire d'indiquer le chemin complet du topic pour que celui-ci soit intégré dans le broker.
Ce qui donne :
Capture-2019-02-08-1.png
Capture-2019-02-08-1.png (8.08 Kio) Consulté 400 fois

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 09 févr. 2019, 10:11

Bonjour,
Je viens de publier une mise à jour de la beta qui améliore légèrement la charge CPU du plugin et affiche les mises à jour des valeurs dans le panneau commande des équipements.
Le changelog détaillé est .
domotruc
Plugins jMQTT, jElocky
domotruc.com

Loic74
Actif
Messages : 708
Inscription : 24 oct. 2017, 22:45
Localisation : Haute-Savoie
Contact :

Re: Plugin jMQTT

Message par Loic74 » 09 févr. 2019, 10:27

Bonjour
Cool, je voulais poser la question justement sur la màj des valeurs
---------------------------------------
Jeedom v3.3.19, VM sur Synology RS1619xs+, Arduinos, ETH-IO32B, MQTT, TTN, LoRa, Service Pack Power Ultimate
Ma présentation
Ma piscine connectée
ioBoard

Avatar de l’utilisateur
mairyj
Timide
Messages : 368
Inscription : 22 nov. 2014, 07:58
Localisation : Belgique

Re: Plugin jMQTT

Message par mairyj » 12 févr. 2019, 14:43

Bonjour,
tout d'abord merci pour ce plugin il est d'une simplicité vraiment génial ^^
Voila je chercher a récolté les infos de mes 3 onduleurs Solis. je pensais prendre un moniteur énergétique mais je suis tombé sur ceci :
https://github.com/dpoulson/ginlong-mqtt
malheureusement mais connaissance sont un peut limité pour intégrés ceci a mon jeedom. Est-ce que quelqu'un pourrais m'éguiller sur la marche suivre pour avoir les infos sur jeedom via mqtt?

merci d'avance pour vos réponses.
Jeedom 3.2.11 sur Z83II + Z-Stick Gen5 + OpenZwave
Philips Hue - Xiaomi Home - Zigate - RFXCom - RFLink - Milight - Harmony Hub - ESPEasy - Broadlink - Heatzy - Google Home - Alexa - Netatmo - Synology DS214Play

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 12 févr. 2019, 20:22

mairyj a écrit :
12 févr. 2019, 14:43
Bonjour,
tout d'abord merci pour ce plugin il est d'une simplicité vraiment génial ^^
Voila je chercher a récolté les infos de mes 3 onduleurs Solis. je pensais prendre un moniteur énergétique mais je suis tombé sur ceci :
https://github.com/dpoulson/ginlong-mqtt
malheureusement mais connaissance sont un peut limité pour intégrés ceci a mon jeedom. Est-ce que quelqu'un pourrais m'éguiller sur la marche suivre pour avoir les infos sur jeedom via mqtt?

merci d'avance pour vos réponses.

Bonjour mairy,
Merci pour les encouragements.
As tu vu ce lien qui complémente l'information du lien GitHub que tu as fourni ?

Ouvres un sujet dédié stp car ça risque de prendre un certain nombre de message et je préférerais ne pas encombrer ce fil.

Merci d'avance.
domotruc
Plugins jMQTT, jElocky
domotruc.com

Avatar de l’utilisateur
mairyj
Timide
Messages : 368
Inscription : 22 nov. 2014, 07:58
Localisation : Belgique

Re: Plugin jMQTT

Message par mairyj » 13 févr. 2019, 10:04

domotruc a écrit :
12 févr. 2019, 20:22
mairyj a écrit :
12 févr. 2019, 14:43
Bonjour,
tout d'abord merci pour ce plugin il est d'une simplicité vraiment génial ^^
Voila je chercher a récolté les infos de mes 3 onduleurs Solis. je pensais prendre un moniteur énergétique mais je suis tombé sur ceci :
https://github.com/dpoulson/ginlong-mqtt
malheureusement mais connaissance sont un peut limité pour intégrés ceci a mon jeedom. Est-ce que quelqu'un pourrais m'éguiller sur la marche suivre pour avoir les infos sur jeedom via mqtt?

merci d'avance pour vos réponses.

Bonjour mairy,
Merci pour les encouragements.
As tu vu ce lien qui complémente l'information du lien GitHub que tu as fourni ?

Ouvres un sujet dédié stp car ça risque de prendre un certain nombre de message et je préférerais ne pas encombrer ce fil.

Merci d'avance.
Je vais creer un sujet pour merci pour le liens je l'ai vu après avoir poster le message mais n'étant pas très doué en programmation de l'aide serait le bien venu ^^ merci en tous cas.
Jeedom 3.2.11 sur Z83II + Z-Stick Gen5 + OpenZwave
Philips Hue - Xiaomi Home - Zigate - RFXCom - RFLink - Milight - Harmony Hub - ESPEasy - Broadlink - Heatzy - Google Home - Alexa - Netatmo - Synology DS214Play

Loic74
Actif
Messages : 708
Inscription : 24 oct. 2017, 22:45
Localisation : Haute-Savoie
Contact :

Re: Plugin jMQTT

Message par Loic74 » 14 févr. 2019, 13:23

Bonjour domotruc

J'ai un petit souci lié à jMQTT, je ne sais pas qui/quoi est en cause: j'ai des déconnexions à répétition entre Jeedom (v3.2.16) et le broker, cf. log de Mosquitto ci-dessous. Il semble que Jeedom essaie de créer plusieurs connexions. Dans le plugin jMQTT l'identifiant renseigné est "jeedom". Je ne sais pas d'où il sort le "jeedom/1614/595dea3b"
1550146107: mosquitto version 1.4.10 (build date Wed, 06 Feb 2019 17:03:31 +0000) starting
1550146107: Config loaded from /etc/mosquitto/mosquitto.conf.
1550146107: Opening websockets listen socket on port 9001.
1550146107: Opening ipv4 listen socket on port 1883.
1550146107: Opening ipv6 listen socket on port 1883.
1550146128: New connection from 192.168.0.66 on port 1883.
1550146128: New client connected from 192.168.0.66 as CharNodeRed (c1, k60, u'admin').
1550146132: New connection from 192.168.0.21 on port 1883.
1550146132: New client connected from 192.168.0.21 as ArduinoPool2 (c1, k10, u'admin').
1550146259: New connection from 192.168.0.33 on port 1883.
1550146259: New client connected from 192.168.0.33 as MQTTfx (c1, k60, u'admin').
1550146432: New connection from 192.168.0.41 on port 1883.
1550146432: New client connected from 192.168.0.41 as jeedom (c1, k60, u'admin').
1550146442: New connection from 192.168.0.41 on port 1883.
1550146442: New client connected from 192.168.0.41 as jeedom/1614/595dea3b (c1, k60, u'admin').
1550146442: Client jeedom/1614/595dea3b disconnected.
1550146444: Socket error on client jeedom, disconnecting.
1550146502: New connection from 192.168.0.41 on port 1883.
Merci par avance
Loic74
---------------------------------------
Jeedom v3.3.19, VM sur Synology RS1619xs+, Arduinos, ETH-IO32B, MQTT, TTN, LoRa, Service Pack Power Ultimate
Ma présentation
Ma piscine connectée
ioBoard

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 14 févr. 2019, 20:45

Bonsoir Loic74,

Les connexions du type jeedom/1614/595dea3b sont liées aux messages publiés par jMQTT (via des commandes action). 1614 est l'identifiant de la commande. A chaque commande exécutée, le plugin ouvre une connexion dédiée, publie le message et la déconnecte.

Ce comportement est normal.

Ce qui ne l'est pas est le message 'Socket error on client jeedom, disconnecting', qui côté jMQTT se traduit j'imagine par l'arrêt du démon.
Quelle est la fréquence de ces déconnexions?

Rappelles moi ta configuration, un PI3?
Si tu peux me faire passer le log jMQTT en mode debug, le log du broker comme tu l'as fait, et l'enregistrement du flux MQTT (avec les dates, voir commande mosquitto_sub dans le chapitre FAQ de la doc du plugin), je regarderai.
domotruc
Plugins jMQTT, jElocky
domotruc.com

Loic74
Actif
Messages : 708
Inscription : 24 oct. 2017, 22:45
Localisation : Haute-Savoie
Contact :

Re: Plugin jMQTT

Message par Loic74 » 14 févr. 2019, 22:14

Merci Domotruc pour le retour rapide, comme d'habitude.

OK pour le comportement normal (néanmoins je suis curieux de savoir pourquoi une connexion dédiée est ouverte pour chaque commande).

Au sujet du Socket error en fait j'ai un comportement erratique de Mosquitto (je ne sais pas depuis quand) et j'ai parfois ce message sur presque toutes les connexions, pas seulement avec Jeedom, donc le pb n'est probablement pas lié au plugin jMQTT. Aujourd'hui le problème survenait très fréquemment et maintenant que j'essaie de capter les logs, il survient moins... Cf. logs. Très étrange.

Lorsque le socket error survient sur la conexion de Jeedom, le deamon tombe effectivement.

Jeedom tourne sur une VM sur mon Synology et Mosquitto et NodeRed sur une autre VM (Stretch), également sur le Synology.
J'ai fait une fresh install de Mosquitto + NodeRed sur un RPi pour voir, mais j'obtiens le même comportement.

Voici les logs.
Merci
Loic74


Log jMQTT

Code : Tout sélectionner

Log jMQTT

[2019-02-14 21:44:04][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 56)
[2019-02-14 21:44:04][DEBUG] : Payload {"status":"ONLINE","bcharge":"100.0","timeleft":"181.9","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"} for topic Home/UPS
[2019-02-14 21:44:04][INFO] : -> UPS|UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"181.9","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{status} "ONLINE"
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{bcharge} "100.0"
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{timeleft} "181.9"
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{battv} "26.4"
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{numxfers} "0"
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{tonbatt} "0"
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{cumonbatt} "0"
[2019-02-14 21:44:04][INFO] : -> UPS|UPS{xoffbatt} "N\/A"
[2019-02-14 21:44:18][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m57, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:44:18][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 57)
[2019-02-14 21:44:18][DEBUG] : Payload {"Tmp":543,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":813,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0} for topic Home/Pool
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool {"Tmp":543,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":813,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{Tmp} 543
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{pH} 740
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{FilUpT} 813
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{IO} 156
[2019-02-14 21:44:18][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:44:48][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m58, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:44:48][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 58)
[2019-02-14 21:44:48][DEBUG] : Payload {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":843,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0} for topic Home/Pool
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":843,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{Tmp} 541
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{pH} 740
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{FilUpT} 843
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{IO} 156
[2019-02-14 21:44:48][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:45:18][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m59, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:45:18][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 59)
[2019-02-14 21:45:18][DEBUG] : Payload {"Tmp":542,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":873,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0} for topic Home/Pool
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool {"Tmp":542,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":873,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{Tmp} 542
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{pH} 740
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{FilUpT} 873
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{IO} 156
[2019-02-14 21:45:18][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:45:48][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m60, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:45:48][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 60)
[2019-02-14 21:45:48][DEBUG] : Payload {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":903,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0} for topic Home/Pool
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":903,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{Tmp} 541
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{pH} 740
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{FilUpT} 903
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{IO} 156
[2019-02-14 21:45:48][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:46:04][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m61, 'Home/UPS', ... (133 bytes))
[2019-02-14 21:46:04][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 61)
[2019-02-14 21:46:04][DEBUG] : Payload {"status":"ONLINE","bcharge":"100.0","timeleft":"198.8","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"} for topic Home/UPS
[2019-02-14 21:46:04][INFO] : -> UPS|UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"198.8","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{status} "ONLINE"
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{bcharge} "100.0"
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{timeleft} "198.8"
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{battv} "26.4"
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{numxfers} "0"
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{tonbatt} "0"
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{cumonbatt} "0"
[2019-02-14 21:46:04][INFO] : -> UPS|UPS{xoffbatt} "N\/A"
[2019-02-14 21:46:09][DEBUG] : mosquitto: disconnectedunexpectedly
[2019-02-14 21:46:09][ERROR] : Erreur sur jMQTT::daemon() : The connection was lost.
[2019-02-14 21:49:28][INFO] : <- jPiscine|Home/Pool/API {"FiltPump":0}
[2019-02-14 21:49:28][DEBUG] : Publication du message Home/Pool/API {"FiltPump":0} (pid=1262, qos=1, retain=0)
[2019-02-14 21:49:28][DEBUG] : Message publié
[2019-02-14 21:50:01][DEBUG] : deamon_start
[2019-02-14 21:50:02][DEBUG] : daemon starts, pid is 9677
[2019-02-14 21:50:02][DEBUG] : status cmd: 553
[2019-02-14 21:50:02][INFO] : Connect to mosquitto: Host=192.168.0.38, Port=1883, Id=jeedom
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending CONNECT
[2019-02-14 21:50:02][INFO] : Equipment jeedom: subscribes to "jeedom/status/#" with Qos=1
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending SUBSCRIBE (Mid: 1, Topic: jeedom/status/#, QoS: 1)
[2019-02-14 21:50:02][INFO] : Equipment Home-VanneEau: subscribes to "Home/VanneEau/#" with Qos=1
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending SUBSCRIBE (Mid: 2, Topic: Home/VanneEau/#, QoS: 1)
[2019-02-14 21:50:02][INFO] : Equipment Feather_lora32u_node: subscribes to "Home/feather_lora32u_nodes" with Qos=1
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending SUBSCRIBE (Mid: 3, Topic: Home/feather_lora32u_nodes, QoS: 1)
[2019-02-14 21:50:02][INFO] : Equipment jPiscine: subscribes to "Home/Pool/#" with Qos=1
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending SUBSCRIBE (Mid: 4, Topic: Home/Pool/#, QoS: 1)
[2019-02-14 21:50:02][INFO] : Equipment UPS: subscribes to "Home/UPS" with Qos=1
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending SUBSCRIBE (Mid: 5, Topic: Home/UPS, QoS: 1)
[2019-02-14 21:50:02][INFO] : API is disable
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received CONNACK (0)
[2019-02-14 21:50:02][DEBUG] : mosquitto: connection response is Connection Accepted.
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending PUBLISH (d0, q1, r1, m6, 'jeedom/status', ... (6 bytes))
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received SUBACK
[2019-02-14 21:50:02][DEBUG] : mosquitto: topic subscription accepted, mid=1
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r1, m1, 'jeedom/status', ... (6 bytes))
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 1)
[2019-02-14 21:50:02][WARNING] : Message skipped: payload 90859966AE55 is not valid for topic jeedom/status
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received SUBACK
[2019-02-14 21:50:02][DEBUG] : mosquitto: topic subscription accepted, mid=2
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r1, m2, 'Home/VanneEau/status', ... (6 bytes))
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 2)
[2019-02-14 21:50:02][DEBUG] : Payload online for topic Home/VanneEau/status
[2019-02-14 21:50:02][INFO] : -> Home-VanneEau|status online
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r1, m3, 'Home/VanneEau/pos', ... (3 bytes))
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 3)
[2019-02-14 21:50:02][WARNING] : Message skipped: payload D0EC98 is not valid for topic Home/VanneEau/pos
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received SUBACK
[2019-02-14 21:50:02][DEBUG] : mosquitto: topic subscription accepted, mid=3
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received SUBACK
[2019-02-14 21:50:02][DEBUG] : mosquitto: topic subscription accepted, mid=4
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r1, m4, 'Home/Pool/status', ... (6 bytes))
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 4)
[2019-02-14 21:50:02][DEBUG] : Payload online for topic Home/Pool/status
[2019-02-14 21:50:02][INFO] : -> jPiscine|Pool/status online
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received SUBACK
[2019-02-14 21:50:02][DEBUG] : mosquitto: topic subscription accepted, mid=5
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received PUBACK (Mid: 6)
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m5, 'jeedom/status', ... (6 bytes))
[2019-02-14 21:50:02][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 5)
[2019-02-14 21:50:02][DEBUG] : Payload online for topic jeedom/status
[2019-02-14 21:50:02][INFO] : -> jeedom|status online
[2019-02-14 21:50:05][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m6, 'Home/UPS', ... (133 bytes))
[2019-02-14 21:50:05][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 6)
[2019-02-14 21:50:05][DEBUG] : Payload {"status":"ONLINE","bcharge":"100.0","timeleft":"200.1","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"} for topic Home/UPS
[2019-02-14 21:50:05][INFO] : -> UPS|UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"200.1","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{status} "ONLINE"
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{bcharge} "100.0"
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{timeleft} "200.1"
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{battv} "26.4"
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{numxfers} "0"
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{tonbatt} "0"
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{cumonbatt} "0"
[2019-02-14 21:50:05][INFO] : -> UPS|UPS{xoffbatt} "N\/A"
[2019-02-14 21:50:18][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m7, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:50:18][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 7)
[2019-02-14 21:50:18][DEBUG] : Payload {"Tmp":556,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0} for topic Home/Pool
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool {"Tmp":556,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{Tmp} 556
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{pH} 742
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{FilUpT} 1120
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{IO} 28
[2019-02-14 21:50:18][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:50:48][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m8, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:50:48][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 8)
[2019-02-14 21:50:48][DEBUG] : Payload {"Tmp":566,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0} for topic Home/Pool
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool {"Tmp":566,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{Tmp} 566
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{pH} 742
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{FilUpT} 1120
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{IO} 28
[2019-02-14 21:50:48][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:51:18][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m9, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:51:18][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 9)
[2019-02-14 21:51:18][DEBUG] : Payload {"Tmp":578,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0} for topic Home/Pool
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool {"Tmp":578,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{Tmp} 578
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{pH} 742
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{FilUpT} 1120
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{IO} 28
[2019-02-14 21:51:18][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:51:48][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m10, 'Home/Pool', ... (100 bytes))
[2019-02-14 21:51:48][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 10)
[2019-02-14 21:51:48][DEBUG] : Payload {"Tmp":588,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0} for topic Home/Pool
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool {"Tmp":588,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{Tmp} 588
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{pH} 742
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{pHEr} 0
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{Orp} 721
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{OrpEr} 0
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{FilUpT} 1120
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{PhUpT} 0
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{ChlUpT} 0
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{IO} 28
[2019-02-14 21:51:48][INFO] : -> jPiscine|Pool{IO2} 0
[2019-02-14 21:52:05][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m11, 'Home/UPS', ... (133 bytes))
[2019-02-14 21:52:05][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 11)
[2019-02-14 21:52:05][DEBUG] : Payload {"status":"ONLINE","bcharge":"100.0","timeleft":"200.1","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"} for topic Home/UPS
[2019-02-14 21:52:05][INFO] : -> UPS|UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"200.1","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{status} "ONLINE"
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{bcharge} "100.0"
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{timeleft} "200.1"
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{battv} "26.4"
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{numxfers} "0"
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{tonbatt} "0"
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{cumonbatt} "0"
[2019-02-14 21:52:05][INFO] : -> UPS|UPS{xoffbatt} "N\/A"
[2019-02-14 21:52:09][INFO] : <- jPiscine|Home/Pool/API {"FiltPump":1}
[2019-02-14 21:52:09][DEBUG] : Publication du message Home/Pool/API {"FiltPump":1} (pid=1669, qos=1, retain=0)
[2019-02-14 21:52:09][DEBUG] : Message publié
[2019-02-14 21:52:09][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m12, 'Home/Pool/API', ... (14 bytes))
[2019-02-14 21:52:09][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 12)
[2019-02-14 21:52:09][DEBUG] : Payload {"FiltPump":1} for topic Home/Pool/API
[2019-02-14 21:52:09][DEBUG] : jPiscine|Filt_ON is an action command: skip
[2019-02-14 21:52:09][DEBUG] : mosquitto: Client jeedom received PUBLISH (d0, q1, r0, m13, 'Home/Pool', ... (101 bytes))
[2019-02-14 21:52:09][DEBUG] : mosquitto: Client jeedom sending PUBACK (Mid: 13)
[2019-02-14 21:52:09][DEBUG] : Payload {"Tmp":596,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0} for topic
Log Broker (NB: un script python tourne sur 192.168.0.66. Il est normal qu'il se connecte, publie, puis se déconnecte toutes les 2 minutes)

Code : Tout sélectionner

Log Broker (NB: un script python tourne sur 192.168.0.66. Il est normal qu'il se connecte, publie, puis se déconnecte toutes les 2 minutes)

1550177184: mosquitto version 1.4.10 (build date Wed, 06 Feb 2019 17:03:31 +0000) starting
1550177184: Config loaded from /etc/mosquitto/mosquitto.conf.
1550177184: Opening websockets listen socket on port 9001.
1550177184: Opening ipv4 listen socket on port 1883.
1550177184: Opening ipv6 listen socket on port 1883.
1550177185: New connection from 192.168.0.41 on port 1883.
1550177185: New connection from 192.168.0.41 on port 1883.
1550177185: New client connected from 192.168.0.41 as mosqsub|8612-DS716 (c1, k60, u'admin').
1550177185: Sending CONNACK to mosqsub|8612-DS716 (0, 0)
1550177185: New client connected from 192.168.0.41 as mosqsub|7536-DS716 (c1, k60, u'admin').
1550177185: Sending CONNACK to mosqsub|7536-DS716 (0, 0)
1550177185: Received SUBSCRIBE from mosqsub|8612-DS716
1550177185: 	# (QoS 0)
1550177185: mosqsub|8612-DS716 0 #
1550177185: Sending SUBACK to mosqsub|8612-DS716
1550177185: Received SUBSCRIBE from mosqsub|7536-DS716
1550177185: 	# (QoS 0)
1550177185: mosqsub|7536-DS716 0 #
1550177185: Sending SUBACK to mosqsub|7536-DS716
1550177185: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r1, m0, 'jeedom/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r1, m0, 'Home/VanneEau/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r1, m0, 'Home/VanneEau/pos', ... (3 bytes))
1550177185: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r1, m0, 'Home/Chauffage/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r1, m0, 'Home/Pool/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r1, m0, 'Home/NodeRed', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r1, m0, 'CharJeedom/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r1, m0, 'jeedom/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r1, m0, 'Home/VanneEau/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r1, m0, 'Home/VanneEau/pos', ... (3 bytes))
1550177185: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r1, m0, 'Home/Chauffage/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r1, m0, 'Home/Pool/status', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r1, m0, 'Home/NodeRed', ... (6 bytes))
1550177185: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r1, m0, 'CharJeedom/status', ... (6 bytes))
1550177186: New connection from 192.168.0.21 on port 1883.
1550177186: New client connected from 192.168.0.21 as ArduinoPool2 (c1, k60, u'admin').
1550177186: Sending CONNACK to ArduinoPool2 (0, 0)
1550177186: Received SUBSCRIBE from ArduinoPool2
1550177186: 	Home/Pool/API (QoS 0)
1550177186: ArduinoPool2 0 Home/Pool/API
1550177186: Sending SUBACK to ArduinoPool2
1550177186: Received PUBLISH from ArduinoPool2 (d0, q1, r1, m48, 'Home/Pool/status', ... (6 bytes))
1550177186: Sending PUBACK to ArduinoPool2 (Mid: 48)
1550177186: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool/status', ... (6 bytes))
1550177186: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool/status', ... (6 bytes))
1550177186: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m49, 'Home/Pool', ... (100 bytes))
1550177186: Sending PUBACK to ArduinoPool2 (Mid: 49)
1550177186: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177186: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177186: New connection from 192.168.0.15 on port 1883.
1550177186: New client connected from 192.168.0.15 as Arduino (c1, k60, u'admin').
1550177186: Sending CONNACK to Arduino (0, 0)
1550177186: Received SUBSCRIBE from Arduino
1550177186: 	Home/VanneEau/Api (QoS 0)
1550177186: Arduino 0 Home/VanneEau/Api
1550177186: Sending SUBACK to Arduino
1550177186: Received SUBSCRIBE from Arduino
1550177186: 	Home/Chauffage/Api (QoS 0)
1550177186: Arduino 0 Home/Chauffage/Api
1550177186: Sending SUBACK to Arduino
1550177186: Received PUBLISH from Arduino (d0, q1, r1, m4, 'Home/VanneEau/status', ... (6 bytes))
1550177186: Sending PUBACK to Arduino (Mid: 4)
1550177186: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/VanneEau/status', ... (6 bytes))
1550177186: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/VanneEau/status', ... (6 bytes))
1550177186: Received PUBLISH from Arduino (d0, q1, r1, m5, 'Home/Chauffage/status', ... (6 bytes))
1550177186: Sending PUBACK to Arduino (Mid: 5)
1550177186: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Chauffage/status', ... (6 bytes))
1550177186: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Chauffage/status', ... (6 bytes))
1550177197: New connection from 192.168.0.38 on port 1883.
1550177197: New client connected from 192.168.0.38 as CharNodeRed (c1, k60, u'admin').
1550177197: Sending CONNACK to CharNodeRed (0, 0)
1550177197: Received SUBSCRIBE from CharNodeRed
1550177197: 	Home/VanneEau/status (QoS 1)
1550177197: CharNodeRed 1 Home/VanneEau/status
1550177197: Sending SUBACK to CharNodeRed
1550177197: Sending PUBLISH to CharNodeRed (d0, q1, r1, m1, 'Home/VanneEau/status', ... (6 bytes))
1550177197: Received SUBSCRIBE from CharNodeRed
1550177197: 	Home/CharNode1/API (QoS 1)
1550177197: CharNodeRed 1 Home/CharNode1/API
1550177197: Sending SUBACK to CharNodeRed
1550177197: Received PUBLISH from CharNodeRed (d0, q1, r1, m32380, 'Home/NodeRed', ... (6 bytes))
1550177197: Sending PUBACK to CharNodeRed (Mid: 32380)
1550177197: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/NodeRed', ... (6 bytes))
1550177197: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/NodeRed', ... (6 bytes))
1550177197: Received PUBACK from CharNodeRed (Mid: 1)
1550177208: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m50, 'Home/Pool', ... (100 bytes))
1550177208: Sending PUBACK to ArduinoPool2 (Mid: 50)
1550177208: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177208: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177232: Received PINGREQ from Arduino
1550177232: Sending PINGRESP to Arduino
1550177238: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m51, 'Home/Pool', ... (100 bytes))
1550177238: Sending PUBACK to ArduinoPool2 (Mid: 51)
1550177238: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177238: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177245: Received PINGREQ from mosqsub|8612-DS716
1550177245: Sending PINGRESP to mosqsub|8612-DS716
1550177245: Received PINGREQ from mosqsub|7536-DS716
1550177245: Sending PINGRESP to mosqsub|7536-DS716
1550177257: Received PINGREQ from CharNodeRed
1550177257: Sending PINGRESP to CharNodeRed
1550177268: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m52, 'Home/Pool', ... (101 bytes))
1550177268: Sending PUBACK to ArduinoPool2 (Mid: 52)
1550177268: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177268: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177278: Received PINGREQ from Arduino
1550177278: Sending PINGRESP to Arduino
1550177283: New connection from 192.168.0.66 on port 1883.
1550177284: Socket error on client <unknown>, disconnecting.
1550177284: New connection from 192.168.0.66 on port 1883.
1550177284: New client connected from 192.168.0.66 as HomeUPS (c1, k60, u'admin').
1550177284: Sending CONNACK to HomeUPS (0, 0)
1550177284: Received PUBLISH from HomeUPS (d0, q1, r0, m1, 'Home/UPS', ... (133 bytes))
1550177284: Sending PUBACK to HomeUPS (Mid: 1)
1550177284: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/UPS', ... (133 bytes))
1550177284: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/UPS', ... (133 bytes))
1550177284: Received DISCONNECT from HomeUPS
1550177284: Client HomeUPS disconnected.
1550177298: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m53, 'Home/Pool', ... (101 bytes))
1550177298: Sending PUBACK to ArduinoPool2 (Mid: 53)
1550177298: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177298: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177305: Received PINGREQ from mosqsub|8612-DS716
1550177305: Sending PINGRESP to mosqsub|8612-DS716
1550177305: Received PINGREQ from mosqsub|7536-DS716
1550177305: Sending PINGRESP to mosqsub|7536-DS716
1550177317: Received PINGREQ from CharNodeRed
1550177317: Sending PINGRESP to CharNodeRed
1550177323: Received PINGREQ from Arduino
1550177323: Sending PINGRESP to Arduino
1550177328: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m54, 'Home/Pool', ... (101 bytes))
1550177328: Sending PUBACK to ArduinoPool2 (Mid: 54)
1550177328: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177328: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177358: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m55, 'Home/Pool', ... (101 bytes))
1550177358: Sending PUBACK to ArduinoPool2 (Mid: 55)
1550177358: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177358: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177365: Received PINGREQ from mosqsub|8612-DS716
1550177365: Sending PINGRESP to mosqsub|8612-DS716
1550177365: Received PINGREQ from mosqsub|7536-DS716
1550177365: Sending PINGRESP to mosqsub|7536-DS716
1550177368: New connection from 192.168.0.41 on port 1883.
1550177368: New client connected from 192.168.0.41 as jeedom/1324/543caee0 (c1, k60, u'admin').
1550177368: Sending CONNACK to jeedom/1324/543caee0 (0, 0)
1550177368: Received PUBLISH from jeedom/1324/543caee0 (d0, q1, r0, m1, 'Home/Pool/API', ... (14 bytes))
1550177368: Sending PUBACK to jeedom/1324/543caee0 (Mid: 1)
1550177368: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool/API', ... (14 bytes))
1550177368: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool/API', ... (14 bytes))
1550177368: Sending PUBLISH to ArduinoPool2 (d0, q0, r0, m0, 'Home/Pool/API', ... (14 bytes))
1550177368: Received DISCONNECT from jeedom/1324/543caee0
1550177368: Client jeedom/1324/543caee0 disconnected.
1550177368: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m56, 'Home/Pool', ... (100 bytes))
1550177368: Sending PUBACK to ArduinoPool2 (Mid: 56)
1550177368: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177368: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177368: Received PINGREQ from Arduino
1550177368: Sending PINGRESP to Arduino
1550177377: Received PINGREQ from CharNodeRed
1550177377: Sending PINGRESP to CharNodeRed
1550177388: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m57, 'Home/Pool', ... (100 bytes))
1550177388: Sending PUBACK to ArduinoPool2 (Mid: 57)
1550177388: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177388: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177402: New connection from 192.168.0.41 on port 1883.
1550177402: New client connected from 192.168.0.41 as jeedom (c1, k60, u'admin').
1550177402: Sending CONNACK to jeedom (0, 0)
1550177402: Received SUBSCRIBE from jeedom
1550177402: 	jeedom/status/# (QoS 1)
1550177402: jeedom 1 jeedom/status/#
1550177402: Sending SUBACK to jeedom
1550177402: Sending PUBLISH to jeedom (d0, q1, r1, m1, 'jeedom/status', ... (6 bytes))
1550177402: Received SUBSCRIBE from jeedom
1550177402: 	Home/VanneEau/# (QoS 1)
1550177402: jeedom 1 Home/VanneEau/#
1550177402: Sending SUBACK to jeedom
1550177402: Sending PUBLISH to jeedom (d0, q1, r1, m2, 'Home/VanneEau/status', ... (6 bytes))
1550177402: Sending PUBLISH to jeedom (d0, q1, r1, m3, 'Home/VanneEau/pos', ... (3 bytes))
1550177402: Received SUBSCRIBE from jeedom
1550177402: 	Home/feather_lora32u_nodes (QoS 1)
1550177402: jeedom 1 Home/feather_lora32u_nodes
1550177402: Sending SUBACK to jeedom
1550177402: Received SUBSCRIBE from jeedom
1550177402: 	Home/Pool/# (QoS 1)
1550177402: jeedom 1 Home/Pool/#
1550177402: Sending SUBACK to jeedom
1550177402: Sending PUBLISH to jeedom (d0, q1, r1, m4, 'Home/Pool/status', ... (6 bytes))
1550177402: Received SUBSCRIBE from jeedom
1550177402: 	Home/UPS (QoS 1)
1550177402: jeedom 1 Home/UPS
1550177402: Sending SUBACK to jeedom
1550177402: Received PUBLISH from jeedom (d0, q1, r1, m6, 'jeedom/status', ... (6 bytes))
1550177402: Sending PUBACK to jeedom (Mid: 6)
1550177402: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'jeedom/status', ... (6 bytes))
1550177402: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'jeedom/status', ... (6 bytes))
1550177402: Sending PUBLISH to jeedom (d0, q1, r0, m5, 'jeedom/status', ... (6 bytes))
1550177402: Received PUBACK from jeedom (Mid: 1)
1550177402: Received PUBACK from jeedom (Mid: 2)
1550177402: Received PUBACK from jeedom (Mid: 3)
1550177402: Received PUBACK from jeedom (Mid: 4)
1550177402: Received PUBACK from jeedom (Mid: 5)
1550177404: New connection from 192.168.0.66 on port 1883.
1550177405: Socket error on client <unknown>, disconnecting.
1550177405: New connection from 192.168.0.66 on port 1883.
1550177405: New client connected from 192.168.0.66 as HomeUPS (c1, k60, u'admin').
1550177405: Sending CONNACK to HomeUPS (0, 0)
1550177405: Received PUBLISH from HomeUPS (d0, q1, r0, m1, 'Home/UPS', ... (133 bytes))
1550177405: Sending PUBACK to HomeUPS (Mid: 1)
1550177405: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/UPS', ... (133 bytes))
1550177405: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/UPS', ... (133 bytes))
1550177405: Sending PUBLISH to jeedom (d0, q1, r0, m6, 'Home/UPS', ... (133 bytes))
1550177405: Received PUBACK from jeedom (Mid: 6)
1550177405: Received DISCONNECT from HomeUPS
1550177405: Client HomeUPS disconnected.
1550177414: Received PINGREQ from Arduino
1550177414: Sending PINGRESP to Arduino
1550177418: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m58, 'Home/Pool', ... (100 bytes))
1550177418: Sending PUBACK to ArduinoPool2 (Mid: 58)
1550177418: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177418: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177418: Sending PUBLISH to jeedom (d0, q1, r0, m7, 'Home/Pool', ... (100 bytes))
1550177418: Received PUBACK from jeedom (Mid: 7)
1550177425: Received PINGREQ from mosqsub|7536-DS716
1550177425: Sending PINGRESP to mosqsub|7536-DS716
1550177425: Received PINGREQ from mosqsub|8612-DS716
1550177425: Sending PINGRESP to mosqsub|8612-DS716
1550177437: Received PINGREQ from CharNodeRed
1550177437: Sending PINGRESP to CharNodeRed
1550177448: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m59, 'Home/Pool', ... (100 bytes))
1550177448: Sending PUBACK to ArduinoPool2 (Mid: 59)
1550177448: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177448: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177448: Sending PUBLISH to jeedom (d0, q1, r0, m8, 'Home/Pool', ... (100 bytes))
1550177448: Received PUBACK from jeedom (Mid: 8)
1550177460: Received PINGREQ from Arduino
1550177460: Sending PINGRESP to Arduino
1550177478: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m60, 'Home/Pool', ... (100 bytes))
1550177478: Sending PUBACK to ArduinoPool2 (Mid: 60)
1550177478: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177478: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177478: Sending PUBLISH to jeedom (d0, q1, r0, m9, 'Home/Pool', ... (100 bytes))
1550177478: Received PUBACK from jeedom (Mid: 9)
1550177485: Received PINGREQ from mosqsub|7536-DS716
1550177485: Sending PINGRESP to mosqsub|7536-DS716
1550177485: Received PINGREQ from mosqsub|8612-DS716
1550177485: Sending PINGRESP to mosqsub|8612-DS716
1550177497: Received PINGREQ from CharNodeRed
1550177497: Sending PINGRESP to CharNodeRed
1550177506: Received PINGREQ from Arduino
1550177506: Sending PINGRESP to Arduino
1550177508: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m61, 'Home/Pool', ... (100 bytes))
1550177508: Sending PUBACK to ArduinoPool2 (Mid: 61)
1550177508: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177508: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (100 bytes))
1550177508: Sending PUBLISH to jeedom (d0, q1, r0, m10, 'Home/Pool', ... (100 bytes))
1550177508: Received PUBACK from jeedom (Mid: 10)
1550177524: New connection from 192.168.0.66 on port 1883.
1550177525: Socket error on client <unknown>, disconnecting.
1550177525: New connection from 192.168.0.66 on port 1883.
1550177525: New client connected from 192.168.0.66 as HomeUPS (c1, k60, u'admin').
1550177525: Sending CONNACK to HomeUPS (0, 0)
1550177525: Received PUBLISH from HomeUPS (d0, q1, r0, m1, 'Home/UPS', ... (133 bytes))
1550177525: Sending PUBACK to HomeUPS (Mid: 1)
1550177525: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/UPS', ... (133 bytes))
1550177525: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/UPS', ... (133 bytes))
1550177525: Sending PUBLISH to jeedom (d0, q1, r0, m11, 'Home/UPS', ... (133 bytes))
1550177525: Received PUBACK from jeedom (Mid: 11)
1550177525: Received DISCONNECT from HomeUPS
1550177525: Client HomeUPS disconnected.
1550177529: New connection from 192.168.0.41 on port 1883.
1550177529: New client connected from 192.168.0.41 as jeedom/1323/d79193c4 (c1, k60, u'admin').
1550177529: Sending CONNACK to jeedom/1323/d79193c4 (0, 0)
1550177529: Received PUBLISH from jeedom/1323/d79193c4 (d0, q1, r0, m1, 'Home/Pool/API', ... (14 bytes))
1550177529: Sending PUBACK to jeedom/1323/d79193c4 (Mid: 1)
1550177529: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool/API', ... (14 bytes))
1550177529: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool/API', ... (14 bytes))
1550177529: Sending PUBLISH to ArduinoPool2 (d0, q0, r0, m0, 'Home/Pool/API', ... (14 bytes))
1550177529: Sending PUBLISH to jeedom (d0, q1, r0, m12, 'Home/Pool/API', ... (14 bytes))
1550177529: Received DISCONNECT from jeedom/1323/d79193c4
1550177529: Client jeedom/1323/d79193c4 disconnected.
1550177529: Received PUBACK from jeedom (Mid: 12)
1550177529: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m62, 'Home/Pool', ... (101 bytes))
1550177529: Sending PUBACK to ArduinoPool2 (Mid: 62)
1550177529: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177529: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177529: Sending PUBLISH to jeedom (d0, q1, r0, m13, 'Home/Pool', ... (101 bytes))
1550177529: Received PUBACK from jeedom (Mid: 13)
1550177538: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m63, 'Home/Pool', ... (101 bytes))
1550177538: Sending PUBACK to ArduinoPool2 (Mid: 63)
1550177538: Sending PUBLISH to mosqsub|8612-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177538: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177538: Sending PUBLISH to jeedom (d0, q1, r0, m14, 'Home/Pool', ... (101 bytes))
1550177538: Received PUBACK from jeedom (Mid: 14)
1550177545: Received PINGREQ from mosqsub|7536-DS716
1550177545: Sending PINGRESP to mosqsub|7536-DS716
1550177545: Received PINGREQ from mosqsub|8612-DS716
1550177545: Sending PINGRESP to mosqsub|8612-DS716
1550177552: Received PINGREQ from Arduino
1550177552: Sending PINGRESP to Arduino
1550177553: Socket error on client mosqsub|8612-DS716, disconnecting.
1550177557: Received PINGREQ from CharNodeRed
1550177557: Sending PINGRESP to CharNodeRed
1550177568: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m64, 'Home/Pool', ... (101 bytes))
1550177568: Sending PUBACK to ArduinoPool2 (Mid: 64)
1550177568: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177568: Sending PUBLISH to jeedom (d0, q1, r0, m15, 'Home/Pool', ... (101 bytes))
1550177568: Received PUBACK from jeedom (Mid: 15)
1550177598: Received PINGREQ from Arduino
1550177598: Sending PINGRESP to Arduino
1550177598: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m65, 'Home/Pool', ... (101 bytes))
1550177598: Sending PUBACK to ArduinoPool2 (Mid: 65)
1550177598: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177598: Sending PUBLISH to jeedom (d0, q1, r0, m16, 'Home/Pool', ... (101 bytes))
1550177598: Received PUBACK from jeedom (Mid: 16)
1550177605: Received PINGREQ from mosqsub|7536-DS716
1550177605: Sending PINGRESP to mosqsub|7536-DS716
1550177617: Received PINGREQ from CharNodeRed
1550177617: Sending PINGRESP to CharNodeRed
1550177628: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m66, 'Home/Pool', ... (101 bytes))
1550177628: Sending PUBACK to ArduinoPool2 (Mid: 66)
1550177628: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177628: Sending PUBLISH to jeedom (d0, q1, r0, m17, 'Home/Pool', ... (101 bytes))
1550177628: Received PUBACK from jeedom (Mid: 17)
1550177643: Received PINGREQ from Arduino
1550177643: Sending PINGRESP to Arduino
1550177644: New connection from 192.168.0.66 on port 1883.
1550177645: Socket error on client <unknown>, disconnecting.
1550177645: New connection from 192.168.0.66 on port 1883.
1550177645: New client connected from 192.168.0.66 as HomeUPS (c1, k60, u'admin').
1550177645: Sending CONNACK to HomeUPS (0, 0)
1550177645: Received PUBLISH from HomeUPS (d0, q1, r0, m1, 'Home/UPS', ... (133 bytes))
1550177645: Sending PUBACK to HomeUPS (Mid: 1)
1550177645: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/UPS', ... (133 bytes))
1550177645: Sending PUBLISH to jeedom (d0, q1, r0, m18, 'Home/UPS', ... (133 bytes))
1550177645: Received PUBACK from jeedom (Mid: 18)
1550177645: Received DISCONNECT from HomeUPS
1550177645: Client HomeUPS disconnected.
1550177658: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m67, 'Home/Pool', ... (101 bytes))
1550177658: Sending PUBACK to ArduinoPool2 (Mid: 67)
1550177658: Sending PUBLISH to mosqsub|7536-DS716 (d0, q0, r0, m0, 'Home/Pool', ... (101 bytes))
1550177658: Sending PUBLISH to jeedom (d0, q1, r0, m19, 'Home/Pool', ... (101 bytes))
1550177658: Received PUBACK from jeedom (Mid: 19)
1550177665: Received PINGREQ from mosqsub|7536-DS716
1550177665: Sending PINGRESP to mosqsub|7536-DS716
1550177677: Received PINGREQ from CharNodeRed
1550177677: Sending PINGRESP to CharNodeRed
1550177688: Received PUBLISH from ArduinoPool2 (d0, q1, r0, m68, 'Home/Pool', ... (101 bytes))
Flux JMQTT

Code : Tout sélectionner

Flux JMQTT

Last login: Thu Feb 14 20:20:03 2019 from 192.168.0.31
root@DS716:~# mosquitto_sub -h 192.168.0.38 -u "XXX" -P "XXXX" -t "#" -v| xargs -d$'\n' -L1 bash -c 'date "+%Y-%m-%d %T.%3N $0"' | tee /tmp/mosquitto_sub.log
2019-02-14 20:42:40.732 jeedom/status onlineT.%3N $0"' | tee /tmp/mosquitto_sub.                                                                                        2019-02-14 20:42:40.734 Home/VanneEau/status online
2019-02-14 20:42:40.736 Home/VanneEau/pos 0~F
2019-02-14 20:42:40.738 Home/Chauffage/status online
2019-02-14 20:42:40.740 Home/Pool/status online
2019-02-14 20:42:40.742 Home/NodeRed online
2019-02-14 20:42:40.744 CharJeedom/status ▒|F▒▒U
2019-02-14 20:42:48.457 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":728,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:43:15.047 Home/Pool/API {"FiltPump":0}
2019-02-14 20:43:15.621 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":755,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:43:18.456 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":755,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:43:19.472 Home/Pool/API {"FiltPump":1}
2019-02-14 20:43:19.820 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":755,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:43:48.455 Home/Pool {"Tmp":543,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":783,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:44:04.854 Home/UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"181.9","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
2019-02-14 20:44:18.456 Home/Pool {"Tmp":543,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":813,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:44:48.454 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":843,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:45:18.454 Home/Pool {"Tmp":542,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":873,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:45:48.454 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":903,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:46:04.658 Home/UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"198.8","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
2019-02-14 20:46:26.255 jeedom/status ▒▒▒f▒U
2019-02-14 20:46:26.257 Home/VanneEau/status ▒▒f▒U
2019-02-14 20:46:26.259 Home/VanneEau/pos ▒▒
2019-02-14 20:46:26.260 Home/Chauffage/status ▒▒▒f▒U
2019-02-14 20:46:26.262 Home/Pool/status p▒f▒U
2019-02-14 20:46:26.264 Home/NodeRed ▒f▒U
2019-02-14 20:46:26.265 CharJeedom/status 0▒f▒U
2019-02-14 20:46:26.463 Home/Pool/status online
2019-02-14 20:46:26.467 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":932,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:46:26.630 Home/VanneEau/status online
2019-02-14 20:46:26.632 Home/Chauffage/status online
2019-02-14 20:46:37.751 Home/NodeRed online
2019-02-14 20:46:48.452 Home/Pool {"Tmp":540,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":961,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:47:18.452 Home/Pool {"Tmp":540,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":991,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:47:48.452 Home/Pool {"Tmp":542,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1021,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:48:04.482 Home/UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"197.7","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
2019-02-14 20:48:18.451 Home/Pool {"Tmp":540,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1051,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:48:48.451 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1081,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:49:18.451 Home/Pool {"Tmp":540,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1111,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:49:28.180 Home/Pool/API {"FiltPump":0}
2019-02-14 20:49:28.385 Home/Pool {"Tmp":540,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:49:48.450 Home/Pool {"Tmp":541,"pH":740,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:50:02.093 jeedom/status online
2019-02-14 20:50:05.311 Home/UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"200.1","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
2019-02-14 20:50:18.450 Home/Pool {"Tmp":556,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:50:48.449 Home/Pool {"Tmp":566,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:51:18.450 Home/Pool {"Tmp":578,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:51:48.449 Home/Pool {"Tmp":588,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":28,"IO2":0}
2019-02-14 20:52:05.149 Home/UPS {"status":"ONLINE","bcharge":"100.0","timeleft":"200.1","battv":"26.4","numxfers":"0","tonbatt":"0","cumonbatt":"0","xoffbatt":"N/A"}
2019-02-14 20:52:09.512 Home/Pool/API {"FiltPump":1}
2019-02-14 20:52:09.821 Home/Pool {"Tmp":596,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1120,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
2019-02-14 20:52:18.449 Home/Pool {"Tmp":596,"pH":742,"pHEr":0,"Orp":721,"OrpEr":0,"FilUpT":1128,"PhUpT":0,"ChlUpT":0,"IO":156,"IO2":0}
---------------------------------------
Jeedom v3.3.19, VM sur Synology RS1619xs+, Arduinos, ETH-IO32B, MQTT, TTN, LoRa, Service Pack Power Ultimate
Ma présentation
Ma piscine connectée
ioBoard

coolfunk
Timide
Messages : 30
Inscription : 30 nov. 2018, 12:41
Localisation : Essonne

Re: Plugin jMQTT

Message par coolfunk » 14 févr. 2019, 23:41

Salut,

j'ai installé le plugin avec une sonde Xiaomi sans problème (tout fonctionne).
Mais lorsque j'essai d'en connecter une 2eme, elle n'est pas détectée sur via le plugin.
Elle est détectée sur mon PI pourtant.

cvdenzen
Timide
Messages : 8
Inscription : 15 févr. 2019, 00:50

Re: Plugin jMQTT

Message par cvdenzen » 15 févr. 2019, 01:10

J'aimerais poser le statut de ma lumière dans un variable. Le statut est publié au topic mqtt "f0/kaku_switch_old/state/3/0", payload "on" (allumé) et "f0/kaku_switch_old/state/3/0", payload "off" (éteint).
J'ai créé un équipement jMQTT qui n'a qu'un seul commande "info", avec valeur "on". Je ne trouve pas le valeur "off", bien que ce message est publié.
Je ne comprends pas comment je pourrais changer un variable (p.e. statusLampAchterdeur) quand les messages mqtt sont reçus.
(mon français n'est pas parfait, je suis néerlandais).
Carl.

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 15 févr. 2019, 06:52

Loic74 a écrit :
14 févr. 2019, 22:14
Merci Domotruc pour le retour rapide, comme d'habitude.

OK pour le comportement normal (néanmoins je suis curieux de savoir pourquoi une connexion dédiée est ouverte pour chaque commande).
C'est lié à l'architecture dynamique de Jeedom : chaque tâche s’exécute sur un processus linux différent (tu les vois les processus actifs dans le menu Moteur de tâche). Ces processus ne partagent pas de données autrement que par le cache et la BD Jeedom. Je crée donc une connexion au broker par processus.
Au sujet du Socket error en fait j'ai un comportement erratique de Mosquitto (je ne sais pas depuis quand) et j'ai parfois ce message sur presque toutes les connexions, pas seulement avec Jeedom, donc le pb n'est probablement pas lié au plugin jMQTT. Aujourd'hui le problème survenait très fréquemment et maintenant que j'essaie de capter les logs, il survient moins... Cf. logs. Très étrange.

Lorsque le socket error survient sur la conexion de Jeedom, le deamon tombe effectivement.

Jeedom tourne sur une VM sur mon Synology et Mosquitto et NodeRed sur une autre VM (Stretch), également sur le Synology.
J'ai fait une fresh install de Mosquitto + NodeRed sur un RPi pour voir, mais j'obtiens le même comportement.
Plusieurs personnes ont ce problème de déconnexion, j'ai essayé de nombreuses fois de reproduire, sur RPi3, VM, docker, sans succès.

J'ai synchronisé les logs que tu m'as passés (fichier joint). Mais le log mosquitto démarre après la déconnexion du démon. On dirait que tu as redémarré mosquitto et que c'est ce qui a déconnecté jMQTT.

Ces messages sont bizarres:

Code : Tout sélectionner

14/02/19 21:48:03	MOSQUITTO	New connection from 192.168.0.66 on port 1883.
14/02/19 21:48:04	MOSQUITTO	Socket error on client <unknown>, disconnecting.
14/02/19 21:48:04	MOSQUITTO	New connection from 192.168.0.66 on port 1883.
14/02/19 21:48:04	MOSQUITTO	New client connected from 192.168.0.66 as HomeUPS (c1, k60, u'admin').
On dirait que ton script python ne se déconnecte pas proprement et qu'il se déconnecte lui même à la connexion suivante.

As tu googlé "mosquitto socket error" : il y a pas mal de choses, assez disparates, qui pourraient te faire tilt para rapport à ta conf.
Pièces jointes
Analyse Loic74.zip
(17.25 Kio) Téléchargé 8 fois
domotruc
Plugins jMQTT, jElocky
domotruc.com

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 15 févr. 2019, 06:59

coolfunk a écrit :
14 févr. 2019, 23:41
Salut,

j'ai installé le plugin avec une sonde Xiaomi sans problème (tout fonctionne).
Mais lorsque j'essai d'en connecter une 2eme, elle n'est pas détectée sur via le plugin.
Elle est détectée sur mon PI pourtant.
Bonjour,
Il faudrait que tu fournisses plus d'information pour aider. Idéalement:
* le log du plugin en mode debug à partir du lancement du démon pour voir à quel topic il souscrit; et
* parallèlement le traffic MQTT enregistré via la commande présente dans la doc du plugin, chapitre FAQ.

Cordialement
domotruc
Plugins jMQTT, jElocky
domotruc.com

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 15 févr. 2019, 07:08

cvdenzen a écrit :
15 févr. 2019, 01:10
J'aimerais poser le statut de ma lumière dans un variable. Le statut est publié au topic mqtt "f0/kaku_switch_old/state/3/0", payload "on" (allumé) et "f0/kaku_switch_old/state/3/0", payload "off" (éteint).
J'ai créé un équipement jMQTT qui n'a qu'un seul commande "info", avec valeur "on". Je ne trouve pas le valeur "off", bien que ce message est publié.
Hi Carl,
We can do it in english if you prefer, even if your french is not so bad at all ;)

This is the normal behaviour : one single command by topic. The value gives the status (on or off). If you make the equipment and the command visible on your dashboard, you will see the transition between on and off.

I will publish an update of the plugin this week-end that will display the refresh of the value in the equipment page.
Je ne comprends pas comment je pourrais changer un variable (p.e. statusLampAchterdeur) quand les messages mqtt sont reçus.
(mon français n'est pas parfait, je suis néerlandais).
Carl.
I do not understand that point. Could you clarity and explain your need?
Have a good day.
domotruc
Plugins jMQTT, jElocky
domotruc.com

Loic74
Actif
Messages : 708
Inscription : 24 oct. 2017, 22:45
Localisation : Haute-Savoie
Contact :

Re: Plugin jMQTT

Message par Loic74 » 15 févr. 2019, 07:55

Merci bien Domotruc

- OK pour le comportement normal, j'ai compris
- sympa le merge dans Excel, je vais utiliser cette approche pour investiguer et ferai un retour si je progresse. Ca marchotte en l'état mais j'aimerais que ce soit nickel... Effectivement j'avais redémarré le broker afin d'afficher plus de comportements.

Bonne journée

NB: petite suggestion pour la doc: indiquer aux utilisateurs de rajouter les options -u et -p pour au besoin pour la commande mosquitto_sub si besoin d'authentification sur le broker
---------------------------------------
Jeedom v3.3.19, VM sur Synology RS1619xs+, Arduinos, ETH-IO32B, MQTT, TTN, LoRa, Service Pack Power Ultimate
Ma présentation
Ma piscine connectée
ioBoard

coolfunk
Timide
Messages : 30
Inscription : 30 nov. 2018, 12:41
Localisation : Essonne

Re: Plugin jMQTT

Message par coolfunk » 15 févr. 2019, 09:45

Merci Domotruc,

en fait entre temps j'ai trouvé la solution, les deux capteurs sont reconnus.
Mais maintenant j'ai un problème de remonté d'infos, dans l'onglet commande en face de chaque commande, il y a une valeur fixe et elle ne varie pas.
Alors que celle-ci varie bien sur le RPI.

J'ai essayer plusieurs choses il ne se passe rien en particulier.
J'ai également joint une image du mode debug du plugin, et on voit que mosquitto and Jeedom passent leur temps a envoyer des requetes.
Pièces jointes
Capture2.JPG
Capture2.JPG (98.3 Kio) Consulté 223 fois
Capture1.JPG
Capture1.JPG (79.95 Kio) Consulté 231 fois

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 16 févr. 2019, 07:31

Bonjour coolfunk,
ces éléments n'aident pas vraiment.
Ce bout de log de plugin montrent le trafic de maintien de la connexion entre jMQTT et le broker Mosquitto (le keepalive), qui se met en place quand il n'y pas d'autre trafic, i.e. quand le broker ne reçoit aucun message auquel jMQTT a souscrit.
Il me faudrait vraiment le log complet, en debug, récupéré après avoir relancé le démon pour voir à quels topics jMQTT souscrit.
Tu n'aurais pas supprimé les commandes zigbee2mqtt/Sonde_temp_salon, par hasard, après avoir activé le parseJson pour inclure celles de ta capture d'écran?
Fais moi aussi passé stp le fichier export de l'équipement (en cliquant sur Export en haut de la page de l'équipement).
domotruc
Plugins jMQTT, jElocky
domotruc.com

Avatar de l’utilisateur
domotruc
Timide
Messages : 252
Inscription : 23 févr. 2018, 08:35
Contact :

Re: Plugin jMQTT

Message par domotruc » 16 févr. 2019, 07:56

Bonjour,
Une mise à jour du plugin est disponible, voir le changelog détaillé ici.
L'évolution fonctionnelle principale est l'affichage des mises à jour de valeurs dans le panneau commande des équipements.
domotruc
Plugins jMQTT, jElocky
domotruc.com

coolfunk
Timide
Messages : 30
Inscription : 30 nov. 2018, 12:41
Localisation : Essonne

Re: Plugin jMQTT

Message par coolfunk » 16 févr. 2019, 09:21

Bonjour Domotruc,

je ne pense pas avoir supprimer les commandes non, enfin je n'espère pas.
Je joins le fichier export.

Encore merci à toi

domotruc a écrit :
16 févr. 2019, 07:31
Bonjour coolfunk,
ces éléments n'aident pas vraiment.
Ce bout de log de plugin montrent le trafic de maintien de la connexion entre jMQTT et le broker Mosquitto (le keepalive), qui se met en place quand il n'y pas d'autre trafic, i.e. quand le broker ne reçoit aucun message auquel jMQTT a souscrit.
Il me faudrait vraiment le log complet, en debug, récupéré après avoir relancé le démon pour voir à quels topics jMQTT souscrit.
Tu n'aurais pas supprimé les commandes zigbee2mqtt/Sonde_temp_salon, par hasard, après avoir activé le parseJson pour inclure celles de ta capture d'écran?
Fais moi aussi passé stp le fichier export de l'équipement (en cliquant sur Export en haut de la page de l'équipement).
Pièces jointes
[Maison][zigbee2mqtt].zip
(1.48 Kio) Téléchargé 6 fois

Répondre

Revenir vers « [Plugin Tiers] MQTT »

Qui est en ligne ?

Utilisateurs parcourant ce forum : Aucun utilisateur inscrit et 1 invité