Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Contenu supprimé à la demande de son auteur
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
c'est pas un problème matériel mais juste que quelquechose envoie trop d'infos au port série (cf https://github.com/OpenZWave/open-zwave/issues/673)
regarde le logs des messages envoyés, peut-être un scénario qui s'exite un peu trop ?
regarde le logs des messages envoyés, peut-être un scénario qui s'exite un peu trop ?
Coin!
Thermostat lowcost MaxCube DataTransfert (upload vers cloud)
Développeur embarqué (rtos/drivers linux/c/xilinx/atmel/pic/arm/mips), système (linux,docker,qnx), scientifique (c++/python/mongodb), web (php/mysql), webservices (java/nodejs)
Thermostat lowcost MaxCube DataTransfert (upload vers cloud)
Développeur embarqué (rtos/drivers linux/c/xilinx/atmel/pic/arm/mips), système (linux,docker,qnx), scientifique (c++/python/mongodb), web (php/mysql), webservices (java/nodejs)
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Salut fensoft,fensoft a écrit :c'est pas un problème matériel mais juste que quelquechose envoie trop d'infos au port série (cf https://github.com/OpenZWave/open-zwave/issues/673)
regarde le logs des messages envoyés, peut-être un scénario qui s'exite un peu trop ?
Tu fais comment pour regarder ces logs ?
Envoyé de mon SM-G935F en utilisant Tapatalk
Ma config : RPI 3 / AEON LABS Z-Stick Gen5 / JPI / ~30 modules ZWAVE
Le tout tourne sous les dernières versions de jeedom et plugins
Le tout tourne sous les dernières versions de jeedom et plugins
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Bonjour à tous,
je tombe pas hasard sur ce post : si cela peut aider, j'ai le soucis également lorsque je passe en mode inclusion après plusieurs jours sans redémarrage de mon Raspberry.
Seule solution pour que le plugin reprenne ses esprits : redémarrer le Raspberry (redémarrage du démon insuffisant).
Chronologiquement :
- démarrage du Raspberry
- x jours se passent
- j'ai besoin d'ajouter un nouveau module donc passage en mode inclusion
- message "Error, ERROR: Not enough space in stream buffer" en boucle dans les logs du plugin. Plus rien ne répond coté Zwave.
- redémarrage du Raspberry
- une fois le réseau Zwave OK, passage en mode inclusion
- inclusion du module
et c'est tout bon.
J'ai le soucis à chaque nouvelle inclusion.
je tombe pas hasard sur ce post : si cela peut aider, j'ai le soucis également lorsque je passe en mode inclusion après plusieurs jours sans redémarrage de mon Raspberry.
Seule solution pour que le plugin reprenne ses esprits : redémarrer le Raspberry (redémarrage du démon insuffisant).
Chronologiquement :
- démarrage du Raspberry
- x jours se passent
- j'ai besoin d'ajouter un nouveau module donc passage en mode inclusion
- message "Error, ERROR: Not enough space in stream buffer" en boucle dans les logs du plugin. Plus rien ne répond coté Zwave.
- redémarrage du Raspberry
- une fois le réseau Zwave OK, passage en mode inclusion
- inclusion du module
et c'est tout bon.
J'ai le soucis à chaque nouvelle inclusion.
Ma config : RPI 2 / AEON LABS Z-Stick Gen5 / 40 modules ZWAVE / 15 modules RFXCom / Bluetooth
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Bonjour à tous,
j'ai eu ce problème il y a un mois, il n'y avait pas trop de solutions, du coup j'ai fais une réinstalle ça a fonctionné.
Aujourd'hui je passe en v3.0.11, (j'étais en V3.0.10), je fais également la mise à jour du plugin open ZWAVE et rebelotte, plantage Zwave.
Je suis sur RPI3 avec clé Z-stick gen 5.
je viens de tenter la manip de débrancher la clé, j'espère que ça va rentrer dans l'ordre, mais ça devient pénible....
Je vous tiens au jus et pour info j'ai aucun scénario qui tourne....
Si c'est un problème matériel, ça sous entend que ça serait la clé qui déconne ????
En tout cas merci pour les infos de tous....
j'ai eu ce problème il y a un mois, il n'y avait pas trop de solutions, du coup j'ai fais une réinstalle ça a fonctionné.
Aujourd'hui je passe en v3.0.11, (j'étais en V3.0.10), je fais également la mise à jour du plugin open ZWAVE et rebelotte, plantage Zwave.
Je suis sur RPI3 avec clé Z-stick gen 5.
je viens de tenter la manip de débrancher la clé, j'espère que ça va rentrer dans l'ordre, mais ça devient pénible....
Je vous tiens au jus et pour info j'ai aucun scénario qui tourne....
Si c'est un problème matériel, ça sous entend que ça serait la clé qui déconne ????
En tout cas merci pour les infos de tous....
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Hello,
de bon matin je reviens vers vous pour vous dire que ça n'a rien changé.
Je l'ai laissé débranchée toute la nuit et rien n' a changé.
Je rebranche ma clé, je lui indique le port, je redémarre le démon et là, la roue crantée se met à tourner et ne s'arrête plus......
C'est franchement usant, ça fait un peu plus d'un an que j'utilise jeedom et j’enchaîne les pannes et les réinstallations....
de bon matin je reviens vers vous pour vous dire que ça n'a rien changé.
Je l'ai laissé débranchée toute la nuit et rien n' a changé.
Je rebranche ma clé, je lui indique le port, je redémarre le démon et là, la roue crantée se met à tourner et ne s'arrête plus......
C'est franchement usant, ça fait un peu plus d'un an que j'utilise jeedom et j’enchaîne les pannes et les réinstallations....
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Idem pour moi...
Strictement aucun souci depuis plus d'1 an, et là, il y a 2 jours, je passe en 3.1.7 et ce bug est arrivé dans l'heure suivant la MAJ...
Si c'est matériel, c'est une sacrée coïncidence...
Strictement aucun souci depuis plus d'1 an, et là, il y a 2 jours, je passe en 3.1.7 et ce bug est arrivé dans l'heure suivant la MAJ...
Si c'est matériel, c'est une sacrée coïncidence...
-
- Timide
- Messages : 240
- Inscription : 18 sept. 2015, 09:00
- Localisation : Champagne - ardennes
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Perso, je n avais pas le problème avant que je passe à la version 3.0.
Depuis, je ne fais pas plus de 10j sans avoir le soucis.
J'ai tout réinstallé tout nickel et pas mieux.
Le dernière chose à faire serait de changer le dongle mais je n'y crois pas trop.
Depuis, je ne fais pas plus de 10j sans avoir le soucis.
J'ai tout réinstallé tout nickel et pas mieux.
Le dernière chose à faire serait de changer le dongle mais je n'y crois pas trop.
NUC avec VM jeedom sur Debian (maître)
jeedom mini + (esclave)
jeedom mini + (esclave)
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
idem ce soir sur une smart après plusieurs arrets relance zwave suite a suppression de noeuds fantomes.
Je fais comment pour débrancher la clef sur une smart? je tente arret et je débranche la smart 10 mins pour voir.
Je fais comment pour débrancher la clef sur une smart? je tente arret et je débranche la smart 10 mins pour voir.
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Perso, j'ai résolu mon souci (disons que ça fait plus de 10 jours que ça ne bug pas...) sans toucher à la clé, juste en supprimant un noeud qui semblait poser problème et en redémarrant le PI3...je croise les doigts...
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Suite à inclusion d'un module, le réseau z-wave ne démarre plus et se met à grimper dans le buffer jusqu'à avoir cette fameuse
"ERROR: Not enough space in stream buffer.
Le dongle a été elevé plusieurs minutes, j'ai tenté de supprimer le noeud mais il apparaît encore dans la page santé.
Log openzwave :
Log openzwaved :
J'en suis à plusieurs arrêt/relances... rien y fait, une idée ?
"ERROR: Not enough space in stream buffer.
Le dongle a été elevé plusieurs minutes, j'ai tenté de supprimer le noeud mais il apparaît encore dans la page santé.
Log openzwave :
Code : Tout sélectionner
[2017-11-03 19:52:30][ERROR] : Error in manager callback
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg/openzwave/network.py", line 948, in zwcallback
self._handle_value_added(args)
File "/usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg/openzwave/network.py", line 1473, in _handle_value_added
self.nodes[args['nodeId']].add_value(args['valueId']['id'])
KeyError: 'valueId'
[2017-11-03 19:52:30][ERROR] : Error in manager callback
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg/openzwave/network.py", line 948, in zwcallback
self._handle_value_added(args)
File "/usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg/openzwave/network.py", line 1473, in _handle_value_added
self.nodes[args['nodeId']].add_value(args['valueId']['id'])
KeyError: 'valueId'
[2017-11-03 19:54:23][ERROR] : RemoveFailedNode, RequestNetworkUpdate. (Failed)
[2017-11-03 19:54:24][ERROR] : RemoveFailedNode, RequestNetworkUpdate. (Failed)
[2017-11-03 19:54:25][ERROR] : RemoveFailedNode, RequestNetworkUpdate. (Failed)
[2017-11-03 20:12:21][ERROR] : Le noeud [Piscine][Pompe Electrolyseur] (101) est présumé mort
[2017-11-03 20:17:19][ERROR] : Le noeud [Piscine][Sondes] (107) est présumé mort
Code : Tout sélectionner
2017-11-03 19:52:30.428 Always, OpenZwave Version 1.4.0 Starting Up
2017-11-03 19:52:48.733 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:52:49.735 Error, Node102, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:52:50.512 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:52:50.514 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:52:52.643 Error, Node113, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:52:52.829 Error, Node113, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:52:54.210 Error, Node113, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:52:54.645 Error, Node113, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:53:11.917 Error, Node098, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:53:20.846 Error, Node027, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:54:07.340 Error, Node113, Cannot find endpoint map to instance for Command Class COMMAND_CLASS_METER endpoint 3
2017-11-03 19:54:07.371 Error, Node113, Cannot find endpoint map to instance for Command Class COMMAND_CLASS_METER endpoint 3
2017-11-03 19:54:07.427 Error, Node113, Cannot find endpoint map to instance for Command Class COMMAND_CLASS_METER endpoint 3
2017-11-03 19:54:23.140 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:54:24.143 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:54:25.145 Error, Node102, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:54:25.643 Error, Node100, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:54:35.638 Error, Node100, ERROR: Dropping command, expected response not received after 2 attempt(s)
2017-11-03 19:54:46.111 Error, Node075, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:54:46.168 Error, Node075, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:54:46.696 Error, Node075, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:55:05.865 Error, Node075, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:55:14.423 Error, Node099, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:55:14.945 Error, Node099, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:55:15.150 Error, Node099, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:55:31.872 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:55:36.185 Error, Node102, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:55:46.182 Error, Node102, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:55:46.185 Error, Node102, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:55:56.183 Error, Node102, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:56:19.253 Error, Node112, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:56:29.251 Error, Node112, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:57:00.479 Error, Node133, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:57:24.324 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:57:43.697 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:57:57.953 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:58:32.110 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:58:42.817 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:58:59.926 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:59:21.587 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:59:32.851 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 19:59:43.872 Error, Node078, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 19:59:53.871 Error, Node078, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:00:16.728 Error, Node018, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:00:38.041 Error, Node137, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:00:51.200 Error, Node031, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:01:16.624 Error, Node044, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:01:44.218 Error, Node067, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:02:45.504 Error, Node069, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:03:16.423 Error, Node069, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:04:08.663 Error, Node071, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:04:25.147 Error, Node075, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:04:56.309 Error, Node086, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:05:57.756 Error, Node089, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:06:09.975 Error, Node089, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:07:00.819 Error, Node090, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:07:17.035 Error, Node091, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:07:27.033 Error, Node091, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:07:53.126 Error, Node098, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:08:05.975 Error, Node099, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:08:16.431 Error, Node099, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:08:30.743 Error, Node100, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:08:40.737 Error, Node100, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:08:52.428 Error, Node100, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:09:04.299 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:09:04.812 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:09:14.301 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:09:15.060 Error, Node101, Cannot find endpoint map to instance for Command Class COMMAND_CLASS_SWITCH_BINARY endpoint 0
2017-11-03 20:09:29.483 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:09:30.485 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:09:31.422 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:09:31.426 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:09:40.487 Error, Node101, ERROR: Dropping command, expected response not received after 4 attempt(s)
2017-11-03 20:09:40.491 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:09:50.488 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:10:01.192 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:10:01.196 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:10:11.194 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:10:21.197 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:10:22.085 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:10:31.199 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:10:41.202 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:10:41.369 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:10:51.203 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:11:01.205 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:11:01.210 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:11:11.206 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:11:11.223 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:11:21.208 Error, Node101, ERROR: Dropping command, expected response not received after 3 attempt(s)
2017-11-03 20:11:31.209 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:11:31.213 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:11:41.212 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:11:51.213 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:11:52.215 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:11:52.730 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:11:52.734 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:12:02.218 Error, Node101, ERROR: Dropping command, expected response not received after 2 attempt(s)
2017-11-03 20:12:12.219 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:12:13.221 Error, Node101, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:12:14.078 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:12:14.082 Error, Node101, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:12:21.557 Error, Node101, ERROR: node presumed dead
2017-11-03 20:12:23.222 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.224 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.225 Error, Node101, ERROR: Dropping command because node is presumed dead
2017-11-03 20:12:23.227 Error, Node102, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:12:24.715 Error, Node101, WARNING: node revived
2017-11-03 20:12:33.225 Error, Node102, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:12:46.622 Error, Node102, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:12:58.161 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:13:08.162 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:13:18.163 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:13:28.163 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:13:38.163 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:13:48.164 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:13:58.164 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:14:08.165 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:14:18.166 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:14:28.167 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:14:38.168 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:14:48.169 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:14:58.169 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:08.170 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:18.171 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:28.172 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:39.235 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:40.236 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:41.236 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:42.237 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:43.237 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:15:43.320 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:15:43.323 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:15:43.324 Error, Node107, ERROR: Dropping command, expected response not received after 6 attempt(s)
2017-11-03 20:15:43.327 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:15:47.887 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:15:53.324 Error, Node107, ERROR: Dropping command, expected response not received after 6 attempt(s)
2017-11-03 20:15:53.529 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:03.325 Error, Node107, ERROR: Dropping command, expected response not received after 2 attempt(s)
2017-11-03 20:16:04.326 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:05.326 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:06.327 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:07.327 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:07.354 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:07.357 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:07.358 Error, Node107, ERROR: Dropping command, expected response not received after 6 attempt(s)
2017-11-03 20:16:07.361 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:07.363 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:07.367 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:17.358 Error, Node107, ERROR: Dropping command, expected response not received after 5 attempt(s)
2017-11-03 20:16:27.359 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:27.475 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:37.360 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:38.353 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:16:47.360 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:57.360 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:16:57.937 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:17:07.361 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:17:08.361 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:17:09.362 Error, Node107, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:17:10.042 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:17:10.048 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:17:10.051 Error, Node107, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:17:19.287 Error, Node107, ERROR: node presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.366 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:19.367 Error, Node107, ERROR: Dropping command because node is presumed dead
2017-11-03 20:17:30.666 Error, Node062, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:17:41.935 Error, Node108, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:17:52.203 Error, Node108, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:18:13.940 Error, Node128, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:18:18.841 Error, Node128, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:18:28.835 Error, Node128, ERROR: Dropping command, expected response not received after 2 attempt(s)
2017-11-03 20:18:38.836 Error, Node128, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:18:51.545 Error, Node129, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:19:01.863 Error, Node129, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:19:12.280 Error, Node131, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:19:13.973 Error, Node131, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:19:15.232 Error, Node107, WARNING: node revived
2017-11-03 20:19:23.969 Error, Node131, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:19:33.969 Error, Node131, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:19:44.036 Error, Node132, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:19:55.692 Error, Node132, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:20:06.081 Error, Node133, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:20:23.037 Error, Node135, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:20:34.571 Error, Node136, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:20:46.183 Error, Node136, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:20:57.349 Error, Node100, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:21:12.284 Error, Node137, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:21:32.381 Error, Node137, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:21:46.613 Error, Node139, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:21:56.950 Error, Node139, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:22:10.724 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:22:25.598 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:22:35.994 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:22:48.366 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:23:04.460 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:23:04.732 Error, Node141, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2017-11-03 20:23:14.730 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:23:32.673 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:23:42.833 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:24:13.857 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:24:23.856 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:24:39.873 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:25:13.880 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:25:39.441 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:25:51.282 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:26:04.553 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:26:15.104 Error, Node141, Recieved a MultiChannelEncap for endpoint 1 for Command Class 33, which we can't find
2017-11-03 20:26:37.885 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:27:11.590 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:27:21.590 Error, Node141, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-11-03 20:27:37.584 Error, Node141, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
perso ça fonctionne.
J'ai fait :
* arrêt de la relance auto plug in. Plusieurs F5 pour pour s assurer de la prise en compte du changement car roue infinie.
* arrêt de la smart
* débrancher l'alim électrique pendant 10 a 15 mins.
* rebrancher la smart
* relancer dépendances zwaves
* relancer zwave
* repasser en mode relance auto du plugin
J'ai fait :
* arrêt de la relance auto plug in. Plusieurs F5 pour pour s assurer de la prise en compte du changement car roue infinie.
* arrêt de la smart
* débrancher l'alim électrique pendant 10 a 15 mins.
* rebrancher la smart
* relancer dépendances zwaves
* relancer zwave
* repasser en mode relance auto du plugin
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
J'ai restauré ma config z-wave, le réseau refonctionne.
Mais j'ai toujours mon noeud qui a fait planter le plugin z-wave à l'inclusion, et quand je veux le supprimer j'ai cette erreur :
Mais j'ai toujours mon noeud qui a fait planter le plugin z-wave à l'inclusion, et quand je veux le supprimer j'ai cette erreur :
Code : Tout sélectionner
[2017-11-03 20:32:51][ERROR] : Error in manager callback
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg/openzwave/network.py", line 948, in zwcallback
self._handle_value_added(args)
File "/usr/local/lib/python2.7/dist-packages/openzwave-0.3.1-py2.7.egg/openzwave/network.py", line 1473, in _handle_value_added
self.nodes[args['nodeId']].add_value(args['valueId']['id'])
KeyError: 'valueId'
[2017-11-03 20:34:05][ERROR] : RemoveFailedNode, RequestNetworkUpdate. (Failed)
[2017-11-03 20:34:06][ERROR] : RemoveFailedNode, RequestNetworkUpdate. (Failed)
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Même erreur chez moi, j'ai un noeud en échec mais pas moyen d'accéder à la page de conf du plugin zwave...
je vais suivre ce post et voir ce que je peux faire
je vais suivre ce post et voir ce que je peux faire
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Hello,
Même souci que Dric ci-dessus.
Après coupure de courant, Jeedom redémarre tout à l'air nickel mais queue sortante qui augmente...
Je laisse stabiliser. Ensuite je tente d'inclure un module et la c'est parti, meme log que DRIC même symptome
Même souci que Dric ci-dessus.
Après coupure de courant, Jeedom redémarre tout à l'air nickel mais queue sortante qui augmente...
Je laisse stabiliser. Ensuite je tente d'inclure un module et la c'est parti, meme log que DRIC même symptome
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Personnellement c'est tout le z-wave qui est paralysé et je commence à regretter de gérer mon chauffage via ce moyen soit ça bug chauffage éteint et du coup je m'en rends compte quand il fait froid, soit ça bug quand les chauffages sont en route et du coup c'est sauna dans la maison ...
Pour l'instant j'ai désactivé tous les scénarios mais c'est toujours pareil, ça tiens une dizaine de jours et ça fini par bugger. Le problème c'est que je n'arrive pas à cerner le moment ou ça dérape puisque quand je m'en aperçois le log est saturé par le message "Error, ERROR: Not enough space in stream buffer". Débrancher le dongle et attendre 30min pour le remettre n'est pas une solution !
Alors du coup le problème est matériel ou logiciel ? comment en être sur ?
Pour l'instant mon installation n'est pas très WAF xd
Pour l'instant j'ai désactivé tous les scénarios mais c'est toujours pareil, ça tiens une dizaine de jours et ça fini par bugger. Le problème c'est que je n'arrive pas à cerner le moment ou ça dérape puisque quand je m'en aperçois le log est saturé par le message "Error, ERROR: Not enough space in stream buffer". Débrancher le dongle et attendre 30min pour le remettre n'est pas une solution !
Alors du coup le problème est matériel ou logiciel ? comment en être sur ?
Pour l'instant mon installation n'est pas très WAF xd
- JEEDOM sous VM DEBIAN Jessie
- AEON Labs Z-Wave Gen5
- 1x Qubino ZMNHAD1
- 1x Qubino ZMNHLA2
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
il faudrait te faire un script de surveillance afin de voir si ton log contient le fameux message "Error, ERROR: Not enough space in stream buffer" et il faudrait qu'il stop le demon du plugin en cas de détection puis vide le log. avec le plugin en mode automatique jeedom va le relancer.
c'est évidement une solution de contournement et non une résolution de problème.
c'est évidement une solution de contournement et non une résolution de problème.
As-tu consulté la documentation avant de poser ta question?
Les demandes de support en MP ne seront pas traité mais j'accepte les dons paypal.me/nechry
Visiter mon blog http://nechry-automation.ch/
Les demandes de support en MP ne seront pas traité mais j'accepte les dons paypal.me/nechry
Visiter mon blog http://nechry-automation.ch/
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
Le problème c'est qu'un redémarrage manuel du démon ne fonctionne pas (roue crantée éternelle), je ne pense pas qu'un script ne changeras pas grand chose à moins de me prévenir au plus vite mais sachant que pour l'instant ça ne tiens que 2 ou 3 jours, j'ai pas le temps d'oublier que ça déconne ^^
- JEEDOM sous VM DEBIAN Jessie
- AEON Labs Z-Wave Gen5
- 1x Qubino ZMNHAD1
- 1x Qubino ZMNHLA2
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
il ne sera justement pas démarré manuellement mais par le Watchdog de jeedom
As-tu consulté la documentation avant de poser ta question?
Les demandes de support en MP ne seront pas traité mais j'accepte les dons paypal.me/nechry
Visiter mon blog http://nechry-automation.ch/
Les demandes de support en MP ne seront pas traité mais j'accepte les dons paypal.me/nechry
Visiter mon blog http://nechry-automation.ch/
Re: Plugins Z-wave bloqué: Error, ERROR: Not enough space in stream buffer
dans ce cas tu m’intéresse mais je ne sais pas comment faire le script xD
- JEEDOM sous VM DEBIAN Jessie
- AEON Labs Z-Wave Gen5
- 1x Qubino ZMNHAD1
- 1x Qubino ZMNHLA2
Qui est en ligne ?
Utilisateurs parcourant ce forum : Aucun utilisateur inscrit et 17 invités