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 :)

Toute la communauté vous remercie

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
Loic74
Actif
Messages : 661
Inscription : 24 oct. 2017, 22:45
Localisation : Haute-Savoie
Contact :

Re: Plugin jMQTT

Message par Loic74 » 11 juil. 2019, 13:46

Bonjour Domotruc,
J'ai mis à jour jMQTT.

J'ai toujours mon problème de second broker dont le status est sur offline alors que l'échange de données avec ce broker fonctionne bien.

Remarque:
Le boker initial a un fonctionnement correct pour l'état STATUS et je vois dans sa config qu'il est abonné au topic "Jeedom/Status/#"
Pour le second boker, dont le STATUS a toujours une valeur OFFLINE, je vois dans sa config qu'il est abonné au topic "Jeedom/#" (pourquoi cette différence?)

Son log ne montre rien de particulier, sinon:

[2019-07-11 13:41:04][DEBUG] : broker msg: Client jeedom sending PINGREQ
[2019-07-11 13:41:04][DEBUG] : broker msg: Client jeedom received PINGRESP

Merci

Loic
---------------------------------------
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

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

Re: Plugin jMQTT

Message par domotruc » 11 juil. 2019, 19:12

Bonjour Loïc,
Bizarre en effet le topic de la commande status. Peux-tu m'envoyer le log du broker en debug après l'avoir redémarré, ainsi que le fichier export de ce même broker.
Merci
domotruc
Plugins jMQTT, jElocky
domotruc.com

arnox
Timide
Messages : 58
Inscription : 09 sept. 2018, 00:10

Re: Plugin jMQTT

Message par arnox » 11 juil. 2019, 22:36

Salut Domotruc
J'ai le meme soucis de broker offline. J'ai un seul broker, et tout fonctionne normalement (les interrupteurs, thermometres, et autres trucs MQTT) hormis le fait que le broker apparait offline.
Rien vu d'anormal dans le log:
[2019-07-11 16:22:59][INFO] : Installation des dépendances, voir log dédié (jMQTT_dep)
[2019-07-11 16:28:52][DEBUG] : Lancement de : /var/www/html/core/class/../../core/php/jeePlugin.php plugin_id=jMQTT function=remove callInstallFunction=1
[2019-07-11 16:28:56][INFO] : Début d'activation du plugin
[2019-07-11 16:28:57][INFO] : Info sur le démon : Array ( [launchable_message] => [launchable] => nok [state] => nok [log] => nok [auto] => 0 )
[2019-07-11 16:28:57][DEBUG] : Lancement de : /var/www/html/core/class/../../core/php/jeePlugin.php plugin_id=jMQTT function=install callInstallFunction=1
[2019-07-11 16:28:57][DEBUG] : multi-broker version is already installed
[2019-07-11 16:28:58][INFO] : vérifie le démon jeedom

J'ai relancé l'install des dépendances, redémarré jeedom, redémarré le raspi... il reste désepérement offline... Franchement ca ne me generait pas plus que ca si ca n'avait pas d'impact sur le reste du plugin, mais le bouton "inclusion" se retrouve grisé et donc inutilisable...
Une idée?

arnox
Timide
Messages : 58
Inscription : 09 sept. 2018, 00:10

Re: Plugin jMQTT

Message par arnox » 11 juil. 2019, 22:43

Tiens, encore un autre truc bizarre que je viens juste de découvrir: si je créé un 2nd broker avec les memes parametres, le premier apparait Online, et le second est offline...
Image

Akoua
Timide
Messages : 24
Inscription : 05 oct. 2018, 14:11

Re: Plugin jMQTT

Message par Akoua » 12 juil. 2019, 07:46

Bjr Domotruc,

J'ai aussi avez la nouvelle version le broker qui passe offline ... Par sécurité, je vais passer la liaison entre Jeedom et VenusGX en filaire plutôt qu'en Wifi dans les prochains jours pour voir si cela améliore le problème mais je n'avez pas constaté ces pertes de connections avant la mise à jour "multi broker" ... Etre ces coupures, le système fonctionne correctement.

[2019-07-12 07:21:32][DEBUG] : broker msg: disconnected unexpectedly
[2019-07-12 07:21:32][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:21:32][INFO] : relance le démon dans 15s

[2019-07-12 07:33:20][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:33:42][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:34:10][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:34:33][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:34:59][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:35:25][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:35:51][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:36:18][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:36:43][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:37:08][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:37:34][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:38:00][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:38:26][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:38:52][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:39:18][WARNING] : exception thrown by MQTT client: The connection was lost.
[2019-07-12 07:39:44][WARNING] : exception thrown by MQTT client: The connection was lost.
https://akoua-energies.com/

Jeedom v3.3.27, VM sur Synology, VenusGX, Wes V2

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

Re: Plugin jMQTT

Message par Loic74 » 12 juil. 2019, 14:12

domotruc a écrit :
11 juil. 2019, 19:12
Bonjour Loïc,
Bizarre en effet le topic de la commande status. Peux-tu m'envoyer le log du broker en debug après l'avoir redémarré, ainsi que le fichier export de ce même broker.
Merci
Bonjour Domotruc,

Voici le log:
[2019-07-12 14:08:07][DEBUG] : broker msg: Client jeedom sending PINGREQ
[2019-07-12 14:08:07][DEBUG] : broker msg: Client jeedom received PINGRESP
[2019-07-12 14:08:11][INFO] : arrête le démon
[2019-07-12 14:08:12][INFO] : démarre le démon
[2019-07-12 14:08:12][DEBUG] : daemon starts, pid is 20349
[2019-07-12 14:08:12][DEBUG] : status cmd id: 1712, topic: jeedom/status
[2019-07-12 14:08:12][INFO] : Connect to mosquitto: Host=eu.thethings.network, Port=1883, Id=jeedom
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom sending CONNECT
[2019-07-12 14:08:14][INFO] : Equipment CharNode: subscribes to "+/devices/+/up" with Qos=1
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom sending SUBSCRIBE (Mid: 1, Topic: +/devices/+/up, QoS: 1)
[2019-07-12 14:08:14][INFO] : Equipment TTN_Broker: subscribes to "jeedom/#" with Qos=1
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom sending SUBSCRIBE (Mid: 2, Topic: jeedom/#, QoS: 1)
[2019-07-12 14:08:14][INFO] : API is disable
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom received CONNACK (0)
[2019-07-12 14:08:14][DEBUG] : broker msg: connection response is Connection Accepted.
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom sending PUBLISH (d0, q1, r1, m3, 'jeedom/status', ... (6 bytes))
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom received SUBACK
[2019-07-12 14:08:14][DEBUG] : broker msg: topic subscription accepted, mid=1
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom received SUBACK
[2019-07-12 14:08:14][DEBUG] : broker msg: topic subscription accepted, mid=2
[2019-07-12 14:08:14][DEBUG] : broker msg: Client jeedom received PUBACK (Mid: 3)
[2019-07-12 14:09:14][DEBUG] : broker msg: Client jeedom sending PINGREQ
[2019-07-12 14:09:14][DEBUG] : broker msg: Client jeedom received PINGRESP
Et l'export:

Code : Tout sélectionner

{
    "name": "TTN_Broker",
    "eqType_name": "jMQTT",
    "configuration": {
        "type": "broker",
        "brkId": "191",
        "createtime": "2019-07-05 21:06:03",
        "auto_add_cmd": "0",
        "Qos": "1",
        "updatetime": "2019-07-12 14:08:14",
        "mqttAddress": "eu.thethings.network",
        "mqttId": "jeedom",
        "mqttUser": "feather_lora32u_nodes",
        "mqttPass": "XXXXXXXXXXXXXXXXXXXXXXXXXXX",
        "api": "disable",
        "lastClientConnectTime": 1562933294
    },
    "category": {
        "heating": "0",
        "security": "0",
        "energy": "0",
        "light": "0",
        "automatism": "0",
        "multimedia": "0",
        "default": "0"
    },
    "display": {
        "showObjectNameOnview": 1,
        "showObjectNameOndview": 1,
        "showObjectNameOnmview": 1,
        "height": "auto",
        "width": "auto",
        "layout::dashboard::table::parameters": {
            "center": 1,
            "styletd": "padding:3px;"
        },
        "layout::mobile::table::parameters": {
            "center": 1,
            "styletd": "padding:3px;"
        },
        "layout::dashboard::table::cmd::1712::line": 1,
        "layout::dashboard::table::cmd::1712::column": 1,
        "layout::mobile::table::cmd::1712::line": 1,
        "layout::mobile::table::cmd::1712::column": 1
    },
    "status": {
        "lastCommunication": "2019-07-09 21:48:26"
    },
    "cmd": [
        {
            "logicalId": "jeedom\/status",
            "eqType": "jMQTT",
            "name": "status",
            "type": "info",
            "subType": "string",
            "isHistorized": "0",
            "configuration": {
                "topic": "jeedom\/status",
                "parseJson": "0",
                "irremovable": 1
            },
            "template": [],
            "display": {
                "invertBinary": "0"
            },
            "isVisible": "1",
            "alert": []
        }
    ]
}
---------------------------------------
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

ebac1
Timide
Messages : 7
Inscription : 06 avr. 2019, 18:05

Re: Plugin jMQTT

Message par ebac1 » 12 juil. 2019, 15:47

Bonjour,
Merci je vais essayer ce WE

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

Re: Plugin jMQTT

Message par domotruc » 12 juil. 2019, 22:24

Bonsoir,
Merci pour les éléments @Loïc. J'ai une piste que je ne pourrai confirmer et corriger que Dimanche au mieux.
domotruc
Plugins jMQTT, jElocky
domotruc.com

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

Re: Plugin jMQTT

Message par domotruc » 14 juil. 2019, 09:59

Bonjour,
J'ai publié une correction du problème de broker restant offline.
Pour ceux que cela intéresse, le détail est sur GitHub.
domotruc
Plugins jMQTT, jElocky
domotruc.com

AngelofDeath51
Timide
Messages : 6
Inscription : 27 oct. 2016, 18:14
Contact :

Re: Plugin jMQTT

Message par AngelofDeath51 » 14 juil. 2019, 15:38

Bonjour,

Merci pour les mises à jours et les corrections, avez-vous pu investiguer sur l'autre soucis remonté, à savoir l'intégralité des objets JMQTT qui "disparaissent"?

Bonne journée,

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

Re: Plugin jMQTT

Message par domotruc » 14 juil. 2019, 17:44

AngelofDeath51 a écrit :
14 juil. 2019, 15:38
Bonjour,

Merci pour les mises à jours et les corrections, avez-vous pu investiguer sur l'autre soucis remonté, à savoir l'intégralité des objets JMQTT qui "disparaissent"?

Bonne journée,
Bonjour,
Seul kemar m'a envoyé des données suite à ce post.
J'ai échangé avec lui en MP. Sa base de donnée, avant migration de jMQTT vers la version multi-broker, est corrompue ce qui interrompt cette migration et fait perdre des modules. Pour le moment, je n'ai pas de solution. Je ne sais pas si son cas est représentatif des autres utilisateurs ayant un problème similaire.
Faites-moi passer vos données, je regarderai.
domotruc
Plugins jMQTT, jElocky
domotruc.com

Raph53
Timide
Messages : 24
Inscription : 01 févr. 2019, 17:55

Re: Plugin jMQTT

Message par Raph53 » 14 juil. 2019, 17:53

Bonjour j'utilise le plugin jmqq, a jour dans sa dernière version je n'ai pas de pb particulier tout marche de mon coté et pas d'objet qui ont disparu.
si vous besoin de log dites moi si ça peut aider

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

Re: Plugin jMQTT

Message par domotruc » 14 juil. 2019, 18:23

Raph53 a écrit :
14 juil. 2019, 17:53
Bonjour j'utilise le plugin jmqq, a jour dans sa dernière version je n'ai pas de pb particulier tout marche de mon coté et pas d'objet qui ont disparu.
si vous besoin de log dites moi si ça peut aider
Bonjour,
J'ai besoin de logs (procédure dans ce message) de personnes qui rencontrent des problèmes de migration à la version multi broker et qui sont obligées de revenir à une sauvegarde avant migration.
Merci pour la proposition en tous cas.
domotruc
Plugins jMQTT, jElocky
domotruc.com

arnox
Timide
Messages : 58
Inscription : 09 sept. 2018, 00:10

Re: Plugin jMQTT

Message par arnox » 15 juil. 2019, 01:46

@domotruc
Merci pour la MaJ... Malheureusement, le Broker est toujours Offline...
Voici mon log:
[2019-07-14 19:43:32][DEBUG] : Payload 0 for topic SV_8/relay/0
[2019-07-14 19:43:32][INFO] : -> SV_8|relay/0 0
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/app', ... (7 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload ESPURNA for topic SV_8/app
[2019-07-14 19:43:32][INFO] : -> SV_8|app ESPURNA
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/version', ... (6 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 1.13.3 for topic SV_8/version
[2019-07-14 19:43:32][INFO] : -> SV_8|version 1.13.3
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/board', ... (15 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload ITEAD_SONOFF_SV for topic SV_8/board
[2019-07-14 19:43:32][INFO] : -> SV_8|board ITEAD_SONOFF_SV
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/host', ... (14 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload ESPURNA-68444E for topic SV_8/host
[2019-07-14 19:43:32][INFO] : -> SV_8|host ESPURNA-68444E
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/ip', ... (12 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 192.168.1.52 for topic SV_8/ip
[2019-07-14 19:43:32][INFO] : -> SV_8|ip 192.168.1.52
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/mac', ... (17 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 80:7D:3A:68:44:4E for topic SV_8/mac
[2019-07-14 19:43:32][INFO] : -> SV_8|mac 80:7D:3A:68:44:4E
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/rssi', ... (3 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload -63 for topic SV_8/rssi
[2019-07-14 19:43:32][INFO] : -> SV_8|rssi -63
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/uptime', ... (7 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 1677013 for topic SV_8/uptime
[2019-07-14 19:43:32][INFO] : -> SV_8|uptime 1677013
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/datetime', ... (19 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 2019-04-14 18:31:27 for topic SV_8/datetime
[2019-07-14 19:43:32][INFO] : -> SV_8|datetime 2019-04-14 18:31:27
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/freeheap', ... (4 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 9312 for topic SV_8/freeheap
[2019-07-14 19:43:32][INFO] : -> SV_8|freeheap 9312
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/vcc', ... (4 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 3146 for topic SV_8/vcc
[2019-07-14 19:43:32][INFO] : -> SV_8|vcc 3146
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/status', ... (1 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 1 for topic SV_8/status
[2019-07-14 19:43:32][INFO] : -> SV_8|status 1
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'SV_8/loadavg', ... (1 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload 1 for topic SV_8/loadavg
[2019-07-14 19:43:32][INFO] : -> SV_8|loadavg 1
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received SUBACK
[2019-07-14 19:43:32][DEBUG] : broker msg: topic subscription accepted, mid=13
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received SUBACK
[2019-07-14 19:43:32][DEBUG] : broker msg: topic subscription accepted, mid=14
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'zigbee2mqtt/bridge/state', ... (6 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload online for topic zigbee2mqtt/bridge/state
[2019-07-14 19:43:32][INFO] : -> zigbee2mqtt|bridgestate online
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r1, m0, 'zigbee2mqtt/bridge/config', ... (99 bytes))
[2019-07-14 19:43:32][DEBUG] : Payload {"version":"1.5.0","commit":"31b8352","coordinator":20190223,"log_level":"info","permit_join":true} for topic zigbee2mqtt/bridge/config
[2019-07-14 19:43:32][INFO] : -> zigbee2mqtt|bridgeconfig {"version":"1.5.0","commit":"31b8352","coordinator":20190223,"log_level":"info","permit_join":true}
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received SUBACK
[2019-07-14 19:43:32][DEBUG] : broker msg: topic subscription accepted, mid=15
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBACK (Mid: 16)
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m21, 'Dual/board', ... (20 bytes))
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 21)
[2019-07-14 19:43:32][DEBUG] : Payload ITEAD_SONOFF_DUAL_R2 for topic Dual/board
[2019-07-14 19:43:32][INFO] : -> Dual|board ITEAD_SONOFF_DUAL_R2
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m22, 'Dual/host', ... (14 bytes))
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 22)
[2019-07-14 19:43:32][DEBUG] : Payload ESPURNA-86C724 for topic Dual/host
[2019-07-14 19:43:32][INFO] : -> Dual|host ESPURNA-86C724
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m23, 'Dual/ssid', ... (5 bytes))
[2019-07-14 19:43:32][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 23)
[2019-07-14 19:43:32][DEBUG] : Payload Arnox for topic Dual/ssid
[2019-07-14 19:43:33][INFO] : -> Dual|ssid Arnox
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m24, 'Dual/ip', ... (12 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 24)
[2019-07-14 19:43:33][DEBUG] : Payload 192.168.1.12 for topic Dual/ip
[2019-07-14 19:43:33][INFO] : -> Dual|ip 192.168.1.12
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m25, 'Dual/mac', ... (17 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 25)
[2019-07-14 19:43:33][DEBUG] : Payload DC:4F:22:86:C7:24 for topic Dual/mac
[2019-07-14 19:43:33][INFO] : -> Dual|mac DC:4F:22:86:C7:24
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m26, 'Dual/rssi', ... (3 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 26)
[2019-07-14 19:43:33][DEBUG] : Payload -71 for topic Dual/rssi
[2019-07-14 19:43:33][INFO] : -> Dual|rssi -71
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m27, 'Dual/uptime', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 27)
[2019-07-14 19:43:33][DEBUG] : Payload 4138648 for topic Dual/uptime
[2019-07-14 19:43:33][INFO] : -> Dual|uptime 4138648
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m28, 'Dual/datetime', ... (19 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 28)
[2019-07-14 19:43:33][DEBUG] : Payload 2019-07-15 01:40:51 for topic Dual/datetime
[2019-07-14 19:43:33][INFO] : -> Dual|datetime 2019-07-15 01:40:51
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m29, 'Dual/freeheap', ... (5 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 29)
[2019-07-14 19:43:33][DEBUG] : Payload 22600 for topic Dual/freeheap
[2019-07-14 19:43:33][INFO] : -> Dual|freeheap 22600
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m30, 'Dual/vcc', ... (4 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 30)
[2019-07-14 19:43:33][DEBUG] : Payload 3190 for topic Dual/vcc
[2019-07-14 19:43:33][INFO] : -> Dual|vcc 3190
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m31, 'Dual/status', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 31)
[2019-07-14 19:43:33][DEBUG] : Payload 1 for topic Dual/status
[2019-07-14 19:43:33][INFO] : -> Dual|status 1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m32, 'Dual/loadavg', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 32)
[2019-07-14 19:43:33][DEBUG] : Payload 3 for topic Dual/loadavg
[2019-07-14 19:43:33][INFO] : -> Dual|loadavg 3
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m33, 'jeedom/status', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 33)
[2019-07-14 19:43:33][DEBUG] : Payload offline for topic jeedom/status
[2019-07-14 19:43:33][INFO] : -> jeedom|status offline
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m34, 'SV_1/relay/0', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 34)
[2019-07-14 19:43:33][DEBUG] : Payload 0 for topic SV_1/relay/0
[2019-07-14 19:43:33][INFO] : -> SV_1|relay/0 0
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m35, 'SV_1/app', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 35)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA for topic SV_1/app
[2019-07-14 19:43:33][INFO] : -> SV_1|app ESPURNA
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m36, 'SV_1/version', ... (6 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 36)
[2019-07-14 19:43:33][DEBUG] : Payload 1.13.5 for topic SV_1/version
[2019-07-14 19:43:33][INFO] : -> SV_1|version 1.13.5
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m37, 'SV_1/board', ... (15 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 37)
[2019-07-14 19:43:33][DEBUG] : Payload ITEAD_SONOFF_SV for topic SV_1/board
[2019-07-14 19:43:33][INFO] : -> SV_1|board ITEAD_SONOFF_SV
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m38, 'SV_1/host', ... (14 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 38)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA-02A7E9 for topic SV_1/host
[2019-07-14 19:43:33][INFO] : -> SV_1|host ESPURNA-02A7E9
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m39, 'SV_1/ssid', ... (5 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 39)
[2019-07-14 19:43:33][DEBUG] : Payload Arnox for topic SV_1/ssid
[2019-07-14 19:43:33][INFO] : -> SV_1|ssid Arnox
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m40, 'SV_1/ip', ... (12 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 40)
[2019-07-14 19:43:33][DEBUG] : Payload 192.168.1.13 for topic SV_1/ip
[2019-07-14 19:43:33][INFO] : -> SV_1|ip 192.168.1.13
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m41, 'SV_1/mac', ... (17 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 41)
[2019-07-14 19:43:33][DEBUG] : Payload CC:50:E3:02:A7:E9 for topic SV_1/mac
[2019-07-14 19:43:33][INFO] : -> SV_1|mac CC:50:E3:02:A7:E9
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m42, 'SV_1/rssi', ... (3 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 42)
[2019-07-14 19:43:33][DEBUG] : Payload -59 for topic SV_1/rssi
[2019-07-14 19:43:33][INFO] : -> SV_1|rssi -59
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m43, 'SV_1/uptime', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 43)
[2019-07-14 19:43:33][DEBUG] : Payload 5296590 for topic SV_1/uptime
[2019-07-14 19:43:33][INFO] : -> SV_1|uptime 5296590
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m44, 'SV_1/datetime', ... (19 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 44)
[2019-07-14 19:43:33][DEBUG] : Payload 2019-07-15 01:41:04 for topic SV_1/datetime
[2019-07-14 19:43:33][INFO] : -> SV_1|datetime 2019-07-15 01:41:04
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m45, 'SV_1/freeheap', ... (5 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 45)
[2019-07-14 19:43:33][DEBUG] : Payload 23640 for topic SV_1/freeheap
[2019-07-14 19:43:33][INFO] : -> SV_1|freeheap 23640
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m46, 'SV_1/vcc', ... (4 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 46)
[2019-07-14 19:43:33][DEBUG] : Payload 3174 for topic SV_1/vcc
[2019-07-14 19:43:33][INFO] : -> SV_1|vcc 3174
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m47, 'SV_1/status', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 47)
[2019-07-14 19:43:33][DEBUG] : Payload 1 for topic SV_1/status
[2019-07-14 19:43:33][INFO] : -> SV_1|status 1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m48, 'SV_1/loadavg', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 48)
[2019-07-14 19:43:33][DEBUG] : Payload 1 for topic SV_1/loadavg
[2019-07-14 19:43:33][INFO] : -> SV_1|loadavg 1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m49, 'SV_2/relay/0', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 49)
[2019-07-14 19:43:33][DEBUG] : Payload 0 for topic SV_2/relay/0
[2019-07-14 19:43:33][INFO] : -> SV_2|relay/0 0
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m50, 'SV_2/app', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 50)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA for topic SV_2/app
[2019-07-14 19:43:33][INFO] : -> SV_2|app ESPURNA
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m51, 'SV_2/version', ... (6 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 51)
[2019-07-14 19:43:33][DEBUG] : Payload 1.13.5 for topic SV_2/version
[2019-07-14 19:43:33][INFO] : -> SV_2|version 1.13.5
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m52, 'SV_2/board', ... (15 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 52)
[2019-07-14 19:43:33][DEBUG] : Payload ITEAD_SONOFF_SV for topic SV_2/board
[2019-07-14 19:43:33][INFO] : -> SV_2|board ITEAD_SONOFF_SV
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m53, 'SV_2/host', ... (14 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 53)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA-4B8277 for topic SV_2/host
[2019-07-14 19:43:33][INFO] : -> SV_2|host ESPURNA-4B8277
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m54, 'SV_2/ssid', ... (5 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 54)
[2019-07-14 19:43:33][DEBUG] : Payload Arnox for topic SV_2/ssid
[2019-07-14 19:43:33][INFO] : -> SV_2|ssid Arnox
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m55, 'SV_2/ip', ... (12 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 55)
[2019-07-14 19:43:33][DEBUG] : Payload 192.168.1.14 for topic SV_2/ip
[2019-07-14 19:43:33][INFO] : -> SV_2|ip 192.168.1.14
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m56, 'SV_2/mac', ... (17 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 56)
[2019-07-14 19:43:33][DEBUG] : Payload DC:4F:22:4B:82:77 for topic SV_2/mac
[2019-07-14 19:43:33][INFO] : -> SV_2|mac DC:4F:22:4B:82:77
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m57, 'SV_2/rssi', ... (3 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 57)
[2019-07-14 19:43:33][DEBUG] : Payload -63 for topic SV_2/rssi
[2019-07-14 19:43:33][INFO] : -> SV_2|rssi -63
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m58, 'SV_2/uptime', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 58)
[2019-07-14 19:43:33][DEBUG] : Payload 8815722 for topic SV_2/uptime
[2019-07-14 19:43:33][INFO] : -> SV_2|uptime 8815722
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m59, 'SV_2/datetime', ... (19 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 59)
[2019-07-14 19:43:33][DEBUG] : Payload 2019-07-15 01:40:50 for topic SV_2/datetime
[2019-07-14 19:43:33][INFO] : -> SV_2|datetime 2019-07-15 01:40:50
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m60, 'SV_2/freeheap', ... (5 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 60)
[2019-07-14 19:43:33][DEBUG] : Payload 23152 for topic SV_2/freeheap
[2019-07-14 19:43:33][INFO] : -> SV_2|freeheap 23152
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m61, 'SV_2/vcc', ... (4 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 61)
[2019-07-14 19:43:33][DEBUG] : Payload 3163 for topic SV_2/vcc
[2019-07-14 19:43:33][INFO] : -> SV_2|vcc 3163
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m62, 'SV_2/status', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 62)
[2019-07-14 19:43:33][DEBUG] : Payload 1 for topic SV_2/status
[2019-07-14 19:43:33][INFO] : -> SV_2|status 1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m63, 'SV_2/loadavg', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 63)
[2019-07-14 19:43:33][DEBUG] : Payload 1 for topic SV_2/loadavg
[2019-07-14 19:43:33][INFO] : -> SV_2|loadavg 1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m64, 'SV_3/relay/0', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 64)
[2019-07-14 19:43:33][DEBUG] : Payload 0 for topic SV_3/relay/0
[2019-07-14 19:43:33][INFO] : -> SV_3|relay/0 0
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m65, 'SV_3/app', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 65)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA for topic SV_3/app
[2019-07-14 19:43:33][INFO] : -> SV_3|app ESPURNA
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m66, 'SV_3/version', ... (6 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 66)
[2019-07-14 19:43:33][DEBUG] : Payload 1.13.5 for topic SV_3/version
[2019-07-14 19:43:33][INFO] : -> SV_3|version 1.13.5
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m67, 'SV_3/board', ... (15 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 67)
[2019-07-14 19:43:33][DEBUG] : Payload ITEAD_SONOFF_SV for topic SV_3/board
[2019-07-14 19:43:33][INFO] : -> SV_3|board ITEAD_SONOFF_SV
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m68, 'SV_3/host', ... (14 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 68)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA-02ABF1 for topic SV_3/host
[2019-07-14 19:43:33][INFO] : -> SV_3|host ESPURNA-02ABF1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m69, 'SV_3/ssid', ... (5 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 69)
[2019-07-14 19:43:33][DEBUG] : Payload Arnox for topic SV_3/ssid
[2019-07-14 19:43:33][INFO] : -> SV_3|ssid Arnox
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m70, 'SV_3/ip', ... (12 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 70)
[2019-07-14 19:43:33][DEBUG] : Payload 192.168.1.15 for topic SV_3/ip
[2019-07-14 19:43:33][INFO] : -> SV_3|ip 192.168.1.15
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m71, 'SV_3/mac', ... (17 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 71)
[2019-07-14 19:43:33][DEBUG] : Payload CC:50:E3:02:AB:F1 for topic SV_3/mac
[2019-07-14 19:43:33][INFO] : -> SV_3|mac CC:50:E3:02:AB:F1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m72, 'SV_3/rssi', ... (3 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 72)
[2019-07-14 19:43:33][DEBUG] : Payload -68 for topic SV_3/rssi
[2019-07-14 19:43:33][INFO] : -> SV_3|rssi -68
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m73, 'SV_3/uptime', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 73)
[2019-07-14 19:43:33][DEBUG] : Payload 8815538 for topic SV_3/uptime
[2019-07-14 19:43:33][INFO] : -> SV_3|uptime 8815538
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m74, 'SV_3/datetime', ... (19 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 74)
[2019-07-14 19:43:33][DEBUG] : Payload 2019-07-15 01:40:53 for topic SV_3/datetime
[2019-07-14 19:43:33][INFO] : -> SV_3|datetime 2019-07-15 01:40:53
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m75, 'SV_3/freeheap', ... (5 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 75)
[2019-07-14 19:43:33][DEBUG] : Payload 22464 for topic SV_3/freeheap
[2019-07-14 19:43:33][INFO] : -> SV_3|freeheap 22464
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m76, 'SV_3/vcc', ... (4 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 76)
[2019-07-14 19:43:33][DEBUG] : Payload 3174 for topic SV_3/vcc
[2019-07-14 19:43:33][INFO] : -> SV_3|vcc 3174
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m77, 'SV_3/status', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 77)
[2019-07-14 19:43:33][DEBUG] : Payload 1 for topic SV_3/status
[2019-07-14 19:43:33][INFO] : -> SV_3|status 1
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m78, 'SV_3/loadavg', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 78)
[2019-07-14 19:43:33][DEBUG] : Payload 2 for topic SV_3/loadavg
[2019-07-14 19:43:33][INFO] : -> SV_3|loadavg 2
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m79, 'SV_4/relay/0', ... (1 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 79)
[2019-07-14 19:43:33][DEBUG] : Payload 0 for topic SV_4/relay/0
[2019-07-14 19:43:33][INFO] : -> SV_4|relay/0 0
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m80, 'SV_4/app', ... (7 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 80)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA for topic SV_4/app
[2019-07-14 19:43:33][INFO] : -> SV_4|app ESPURNA
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m81, 'SV_4/version', ... (6 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 81)
[2019-07-14 19:43:33][DEBUG] : Payload 1.13.5 for topic SV_4/version
[2019-07-14 19:43:33][INFO] : -> SV_4|version 1.13.5
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m82, 'SV_4/board', ... (15 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 82)
[2019-07-14 19:43:33][DEBUG] : Payload ITEAD_SONOFF_SV for topic SV_4/board
[2019-07-14 19:43:33][INFO] : -> SV_4|board ITEAD_SONOFF_SV
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m83, 'SV_4/host', ... (14 bytes))
[2019-07-14 19:43:33][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 83)
[2019-07-14 19:43:33][DEBUG] : Payload ESPURNA-02AB8B for topic SV_4/host
[2019-07-14 19:43:34][INFO] : -> SV_4|host ESPURNA-02AB8B
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m84, 'SV_4/ssid', ... (5 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 84)
[2019-07-14 19:43:34][DEBUG] : Payload Arnox for topic SV_4/ssid
[2019-07-14 19:43:34][INFO] : -> SV_4|ssid Arnox
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m85, 'SV_4/ip', ... (12 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 85)
[2019-07-14 19:43:34][DEBUG] : Payload 192.168.1.16 for topic SV_4/ip
[2019-07-14 19:43:34][INFO] : -> SV_4|ip 192.168.1.16
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m86, 'SV_4/mac', ... (17 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 86)
[2019-07-14 19:43:34][DEBUG] : Payload CC:50:E3:02:AB:8B for topic SV_4/mac
[2019-07-14 19:43:34][INFO] : -> SV_4|mac CC:50:E3:02:AB:8B
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m87, 'SV_4/rssi', ... (3 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 87)
[2019-07-14 19:43:34][DEBUG] : Payload -35 for topic SV_4/rssi
[2019-07-14 19:43:34][INFO] : -> SV_4|rssi -35
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m88, 'SV_4/uptime', ... (7 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 88)
[2019-07-14 19:43:34][DEBUG] : Payload 1549118 for topic SV_4/uptime
[2019-07-14 19:43:34][INFO] : -> SV_4|uptime 1549118
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m89, 'SV_4/datetime', ... (19 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 89)
[2019-07-14 19:43:34][DEBUG] : Payload 2019-07-15 01:40:52 for topic SV_4/datetime
[2019-07-14 19:43:34][INFO] : -> SV_4|datetime 2019-07-15 01:40:52
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m90, 'SV_4/freeheap', ... (5 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 90)
[2019-07-14 19:43:34][DEBUG] : Payload 23592 for topic SV_4/freeheap
[2019-07-14 19:43:34][INFO] : -> SV_4|freeheap 23592
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m91, 'SV_4/vcc', ... (4 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 91)
[2019-07-14 19:43:34][DEBUG] : Payload 3171 for topic SV_4/vcc
[2019-07-14 19:43:34][INFO] : -> SV_4|vcc 3171
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m92, 'SV_4/status', ... (1 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 92)
[2019-07-14 19:43:34][DEBUG] : Payload 1 for topic SV_4/status
[2019-07-14 19:43:34][INFO] : -> SV_4|status 1
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m93, 'SV_4/loadavg', ... (1 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 93)
[2019-07-14 19:43:34][DEBUG] : Payload 1 for topic SV_4/loadavg
[2019-07-14 19:43:34][INFO] : -> SV_4|loadavg 1
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m94, 'SV_5/relay/0', ... (1 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 94)
[2019-07-14 19:43:34][DEBUG] : Payload 0 for topic SV_5/relay/0
[2019-07-14 19:43:34][INFO] : -> SV_5|relay/0 0
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m95, 'SV_5/app', ... (7 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 95)
[2019-07-14 19:43:34][DEBUG] : Payload ESPURNA for topic SV_5/app
[2019-07-14 19:43:34][INFO] : -> SV_5|app ESPURNA
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m96, 'SV_5/version', ... (6 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 96)
[2019-07-14 19:43:34][DEBUG] : Payload 1.13.5 for topic SV_5/version
[2019-07-14 19:43:34][INFO] : -> SV_5|version 1.13.5
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m97, 'SV_5/board', ... (15 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 97)
[2019-07-14 19:43:34][DEBUG] : Payload ITEAD_SONOFF_SV for topic SV_5/board
[2019-07-14 19:43:34][INFO] : -> SV_5|board ITEAD_SONOFF_SV
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m98, 'SV_5/host', ... (14 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 98)
[2019-07-14 19:43:34][DEBUG] : Payload ESPURNA-02ABF0 for topic SV_5/host
[2019-07-14 19:43:34][INFO] : -> SV_5|host ESPURNA-02ABF0
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m99, 'SV_5/ssid', ... (5 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 99)
[2019-07-14 19:43:34][DEBUG] : Payload Arnox for topic SV_5/ssid
[2019-07-14 19:43:34][INFO] : -> SV_5|ssid Arnox
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m100, 'SV_5/ip', ... (12 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 100)
[2019-07-14 19:43:34][DEBUG] : Payload 192.168.1.17 for topic SV_5/ip
[2019-07-14 19:43:34][INFO] : -> SV_5|ip 192.168.1.17
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m101, 'SV_5/mac', ... (17 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 101)
[2019-07-14 19:43:34][DEBUG] : Payload CC:50:E3:02:AB:F0 for topic SV_5/mac
[2019-07-14 19:43:34][INFO] : -> SV_5|mac CC:50:E3:02:AB:F0
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m102, 'SV_5/rssi', ... (3 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 102)
[2019-07-14 19:43:34][DEBUG] : Payload -75 for topic SV_5/rssi
[2019-07-14 19:43:34][INFO] : -> SV_5|rssi -75
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m103, 'SV_5/uptime', ... (7 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 103)
[2019-07-14 19:43:34][DEBUG] : Payload 8814816 for topic SV_5/uptime
[2019-07-14 19:43:34][INFO] : -> SV_5|uptime 8814816
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m104, 'SV_5/datetime', ... (19 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 104)
[2019-07-14 19:43:34][DEBUG] : Payload 2019-07-15 01:40:52 for topic SV_5/datetime
[2019-07-14 19:43:34][INFO] : -> SV_5|datetime 2019-07-15 01:40:52
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m105, 'SV_5/freeheap', ... (5 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 105)
[2019-07-14 19:43:34][DEBUG] : Payload 22832 for topic SV_5/freeheap
[2019-07-14 19:43:34][INFO] : -> SV_5|freeheap 22832
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m106, 'SV_5/vcc', ... (4 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 106)
[2019-07-14 19:43:34][DEBUG] : Payload 3223 for topic SV_5/vcc
[2019-07-14 19:43:34][INFO] : -> SV_5|vcc 3223
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m107, 'SV_5/status', ... (1 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 107)
[2019-07-14 19:43:34][DEBUG] : Payload 1 for topic SV_5/status
[2019-07-14 19:43:34][INFO] : -> SV_5|status 1
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m108, 'SV_5/loadavg', ... (1 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 108)
[2019-07-14 19:43:34][DEBUG] : Payload 3 for topic SV_5/loadavg
[2019-07-14 19:43:34][INFO] : -> SV_5|loadavg 3
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m109, 'Transfo Cuisine/relay/0', ... (1 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 109)
[2019-07-14 19:43:34][DEBUG] : Payload 0 for topic Transfo Cuisine/relay/0
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|relay/0 0
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m110, 'Transfo Cuisine/app', ... (7 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 110)
[2019-07-14 19:43:34][DEBUG] : Payload ESPURNA for topic Transfo Cuisine/app
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|app ESPURNA
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m111, 'Transfo Cuisine/version', ... (6 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 111)
[2019-07-14 19:43:34][DEBUG] : Payload 1.13.5 for topic Transfo Cuisine/version
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|version 1.13.5
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m112, 'Transfo Cuisine/board', ... (18 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 112)
[2019-07-14 19:43:34][DEBUG] : Payload ITEAD_SONOFF_BASIC for topic Transfo Cuisine/board
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|board ITEAD_SONOFF_BASIC
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m113, 'Transfo Cuisine/host', ... (13 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 113)
[2019-07-14 19:43:34][DEBUG] : Payload ESPURNA8AC810 for topic Transfo Cuisine/host
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|host ESPURNA8AC810
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m114, 'Transfo Cuisine/ssid', ... (5 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 114)
[2019-07-14 19:43:34][DEBUG] : Payload Arnox for topic Transfo Cuisine/ssid
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|ssid Arnox
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m115, 'Transfo Cuisine/ip', ... (12 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 115)
[2019-07-14 19:43:34][DEBUG] : Payload 192.168.1.10 for topic Transfo Cuisine/ip
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|ip 192.168.1.10
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m116, 'Transfo Cuisine/mac', ... (17 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 116)
[2019-07-14 19:43:34][DEBUG] : Payload 68:C6:3A:8A:C8:10 for topic Transfo Cuisine/mac
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|mac 68:C6:3A:8A:C8:10
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m117, 'Transfo Cuisine/rssi', ... (3 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 117)
[2019-07-14 19:43:34][DEBUG] : Payload -71 for topic Transfo Cuisine/rssi
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|rssi -71
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m118, 'Transfo Cuisine/uptime', ... (2 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 118)
[2019-07-14 19:43:34][DEBUG] : Payload 27 for topic Transfo Cuisine/uptime
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|uptime 27
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m119, 'Transfo Cuisine/datetime', ... (19 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 119)
[2019-07-14 19:43:34][DEBUG] : Payload 2019-04-29 13:52:50 for topic Transfo Cuisine/datetime
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|datetime 2019-04-29 13:52:50
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q1, r1, m120, 'Transfo Cuisine/freeheap', ... (5 bytes))
[2019-07-14 19:43:34][DEBUG] : broker msg: Client jeedom sending PUBACK (Mid: 120)
[2019-07-14 19:43:34][DEBUG] : Payload 23544 for topic Transfo Cuisine/freeheap
[2019-07-14 19:43:34][INFO] : -> Transfo Cuisine|freeheap 23544
[2019-07-14 19:44:05][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r0, m0, 'zigbee2mqtt/0x00158d0002e3572f', ... (80 bytes))
[2019-07-14 19:44:05][DEBUG] : Payload {"illuminance":6,"linkquality":47,"occupancy":true,"battery":100,"voltage":3045} for topic zigbee2mqtt/0x00158d0002e3572f
[2019-07-14 19:44:05][INFO] : -> zigbee2mqtt|Mouvement Garage {"illuminance":6,"linkquality":47,"occupancy":true,"battery":100,"voltage":3045}
[2019-07-14 19:44:05][INFO] : -> zigbee2mqtt|Mouvement Garage{illuminance} 6
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{linkquality} 47
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{occupancy} true
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{battery} 100
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{voltage} 3045
[2019-07-14 19:44:06][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r0, m0, 'zigbee2mqtt/0x00158d0002e3572f', ... (80 bytes))
[2019-07-14 19:44:06][DEBUG] : Payload {"illuminance":7,"linkquality":44,"occupancy":true,"battery":100,"voltage":3045} for topic zigbee2mqtt/0x00158d0002e3572f
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage {"illuminance":7,"linkquality":44,"occupancy":true,"battery":100,"voltage":3045}
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{illuminance} 7
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{linkquality} 44
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{occupancy} true
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{battery} 100
[2019-07-14 19:44:06][INFO] : -> zigbee2mqtt|Mouvement Garage{voltage} 3045
[2019-07-14 19:44:13][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r0, m0, 'zigbee2mqtt/0x00158d0002e24b7f', ... (81 bytes))
[2019-07-14 19:44:13][DEBUG] : Payload {"illuminance":25,"linkquality":52,"occupancy":true,"battery":100,"voltage":3045} for topic zigbee2mqtt/0x00158d0002e24b7f
[2019-07-14 19:44:13][INFO] : -> zigbee2mqtt|Mouvement Entree {"illuminance":25,"linkquality":52,"occupancy":true,"battery":100,"voltage":3045}
[2019-07-14 19:44:13][INFO] : -> zigbee2mqtt|Mouvement Entree{illuminance} 25
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{linkquality} 52
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{occupancy} true
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{battery} 100
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{voltage} 3045
[2019-07-14 19:44:14][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r0, m0, 'zigbee2mqtt/0x00158d0002e24b7f', ... (81 bytes))
[2019-07-14 19:44:14][DEBUG] : Payload {"illuminance":25,"linkquality":52,"occupancy":true,"battery":100,"voltage":3045} for topic zigbee2mqtt/0x00158d0002e24b7f
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree {"illuminance":25,"linkquality":52,"occupancy":true,"battery":100,"voltage":3045}
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{illuminance} 25
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{linkquality} 52
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{occupancy} true
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{battery} 100
[2019-07-14 19:44:14][INFO] : -> zigbee2mqtt|Mouvement Entree{voltage} 3045
[2019-07-14 19:44:16][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r0, m0, 'zigbee2mqtt/0x00124b001bc7480a', ... (48 bytes))
[2019-07-14 19:44:16][DEBUG] : Payload {"state":true,"linkquality":55,"led_state":true} for topic zigbee2mqtt/0x00124b001bc7480a
[2019-07-14 19:44:16][INFO] : -> zigbee2mqtt|Repeater Zigbee {"state":true,"linkquality":55,"led_state":true}
[2019-07-14 19:44:16][INFO] : -> zigbee2mqtt|Repeater Zigbee{state} true
[2019-07-14 19:44:16][INFO] : -> zigbee2mqtt|Repeater Zigbee{linkquality} 55
[2019-07-14 19:44:16][INFO] : -> zigbee2mqtt|0x00124b001bc7480a{led_state} true
[2019-07-14 19:44:34][DEBUG] : broker msg: Client jeedom sending PINGREQ
[2019-07-14 19:44:34][DEBUG] : broker msg: Client jeedom received PINGRESP
[2019-07-14 19:45:16][DEBUG] : broker msg: Client jeedom received PUBLISH (d0, q0, r0, m0, 'zigbee2mqtt/0x00124b001bc7480a', ... (48 bytes))
[2019-07-14 19:45:16][DEBUG] : Payload {"state":true,"linkquality":57,"led_state":true} for topic zigbee2mqtt/0x00124b001bc7480a
[2019-07-14 19:45:16][INFO] : -> zigbee2mqtt|Repeater Zigbee {"state":true,"linkquality":57,"led_state":true}
[2019-07-14 19:45:16][INFO] : -> zigbee2mqtt|Repeater Zigbee{state} true
[2019-07-14 19:45:16][INFO] : -> zigbee2mqtt|Repeater Zigbee{linkquality} 57
[2019-07-14 19:45:16][INFO] : -> zigbee2mqtt|0x00124b001bc7480a{led_state} true

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

Re: Plugin jMQTT

Message par domotruc » 15 juil. 2019, 07:02

Bonjour arnox,
Vérifies que sur ton installation tu n'as bien qu'un seul client connecté à ton broker avec un Identifiant de Connexion donné (côté jmqtt, ça veut dire un seul équipement broker avec un même Identifiant de Connexion et la même adresse ip). Sinon, ils vont se déconnecter l'un l'autre.
Si ce n'est pas ça, il me faudrait le log juste après avoir redémarrer le démon.
Merci.
domotruc
Plugins jMQTT, jElocky
domotruc.com

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

Re: Plugin jMQTT

Message par Loic74 » 15 juil. 2019, 10:59

domotruc a écrit :
14 juil. 2019, 09:59
Bonjour,
J'ai publié une correction du problème de broker restant offline.
Pour ceux que cela intéresse, le détail est sur GitHub.
Bonjour Domotruc, tout semble fonctionner à présent, merci!
---------------------------------------
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

arnox
Timide
Messages : 58
Inscription : 09 sept. 2018, 00:10

Re: Plugin jMQTT

Message par arnox » 15 juil. 2019, 14:09

@Domotruc
Bon, j'ai vérifiémon install, le seul broker que j'ai est sur mon Rpi (bon, j'ai quand meme revérifié que je n'avais rien sur mon Syno vu que j'avais des tests au tout début avec lui, mais bon c'etait il y a un an...)
Par contre, en tripatouillant dans les parametres du plugin, je me suis apercu que j'avais un identifiant de connexion renseigné par défaut (Jeedom) alors que je ne l'avais jamais fait... Bref, je l'ai supprimé, relancé le démon et tout fonctionne a présent... Merci pour ton support!

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

Re: Plugin jMQTT

Message par Loic74 » 15 juil. 2019, 14:16

arnox a écrit :
15 juil. 2019, 14:09
Par contre, en tripatouillant dans les parametres du plugin, je me suis apercu que j'avais un identifiant de connexion renseigné par défaut (Jeedom) alors que je ne l'avais jamais fait... Bref, je l'ai supprimé, relancé le démon et tout fonctionne a présent... Merci pour ton support!
Il me semble qu'il est normal que le plugin renseigne un identifiant par défaut et cela ne devrait pas affecter le fonctionnement sauf si tu as un autre client qui se connecte au broker avec le même identifiant
---------------------------------------
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

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

Re: Plugin jMQTT

Message par domotruc » 15 juil. 2019, 20:25

Loic74 a écrit :
15 juil. 2019, 14:16
arnox a écrit :
15 juil. 2019, 14:09
Par contre, en tripatouillant dans les parametres du plugin, je me suis apercu que j'avais un identifiant de connexion renseigné par défaut (Jeedom) alors que je ne l'avais jamais fait... Bref, je l'ai supprimé, relancé le démon et tout fonctionne a présent... Merci pour ton support!
Il me semble qu'il est normal que le plugin renseigne un identifiant par défaut et cela ne devrait pas affecter le fonctionnement sauf si tu as un autre client qui se connecte au broker avec le même identifiant

Bonsoir,
Je confirme l'analyse de Loïc, tu as fort certainement un module dans ton installation qui se connecte avec l'identifiant que tu avais précédemment, à savoir Jeedom.
Cool que ça marche.
domotruc
Plugins jMQTT, jElocky
domotruc.com

Mamourette1913
Timide
Messages : 1
Inscription : Hier, 00:12

Re: Plugin jMQTT

Message par Mamourette1913 » Hier, 00:20

Bonjour,
Je viens de me rendre compte que mes équipements MQTT (Victron Multiplus et Moniteur CCGX) n'étaient plus mis à jour depuis début juin suite à qq mises à jour.
Les equipements sont toujours présents sur les dashboard et les design, mais les valeurs ne sont pas mise à jour et les équipement n'apparaissent pas sur la page de configuration du plugins. Idem, quand je clique sur l'objet, je vais sur la page de configuration du plugin, mais les équipements ne sont pas là.
Par contre, lorsque je vais dans Outils/Résumé Domotique, ils sont bien présents et je peux accéder aux commandes et à la page de configuration.
Quand j'essaie de les recréer à l'identique, j'ai un message d'erreur m'indiquant les équipements du même nom existent déjà.
Avez vous une idée du problème?
Sinon le broker fonctionne, car je peux récupérer, en les recréant, les équipements.
Y a t'il un moyen de réactiver ces équipements et leurs configurations?
Merci d'avance pour votre aide,
Philippe.

Répondre

Revenir vers « [Plugin Tiers] MQTT »

Qui est en ligne ?

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