Domotica gratuit › Forums › Report a bug › Zwave service very slow
Mots-clés : Zwave logs CPU repeater
- Ce sujet contient 6 réponses, 4 participants et a été mis à jour pour la dernière fois par
djandib, le il y a 4 années et 4 mois.
-
AuteurMessages
-
août 9, 2016 à 2:47 #3662
macgreg0r
Participantsince few day my zwave service is very slow(= 3 or five min to execute a command), and use many CPU.
I searched why and found that the log file OZW_Log.txt takes 8GB. I cleared it, but after 1 night it is already taking more thant 3GB:
-rw-r–r– 1 http http 3476822301 Aug 9 14:32 OZW_Log.txt
I put tail -f and saw that some messages are arriving in loop:
2016-08-09 14:34:23.948 Detail,
2016-08-09 14:34:23.948 Info, Node003, Sending (Send) message (Callback ID=0x4c, Expected Reply=0x13) – MultiInstanceAssociationCmd_Set (Node=3): 0x01, 0x0b, 0x00, 0x13, 0x03, 0x04, 0x8e, 0x01, 0x03, 0x01, 0x25, 0x4c, 0x04
2016-08-09 14:34:23.955 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-08-09 14:34:23.955 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2016-08-09 14:34:23.967 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0x4c, 0x00, 0xa5
2016-08-09 14:34:23.967 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x4c received (expected 0x4c)
2016-08-09 14:34:23.967 Info, Node003, Request RTT 18 Average Request RTT 18
2016-08-09 14:34:23.967 Detail, Expected callbackId was received
2016-08-09 14:34:23.967 Detail, Expected reply was received
2016-08-09 14:34:23.968 Detail, Message transaction complete
2016-08-09 14:34:23.968 Detail,
2016-08-09 14:34:23.968 Detail, Node003, Removing current message
2016-08-09 14:34:23.968 Detail,
2016-08-09 14:34:23.968 Info, Node003, Sending (Send) message (Callback ID=0x4d, Expected Reply=0x04) – MultiInstanceAssociationCmd_Get (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x8e, 0x02, 0x03, 0x25, 0x4d, 0x01
2016-08-09 14:34:23.974 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-08-09 14:34:23.974 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2016-08-09 14:34:23.987 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0x4d, 0x00, 0xa4
2016-08-09 14:34:23.987 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x4d received (expected 0x4d)
2016-08-09 14:34:23.987 Info, Node003, Request RTT 18 Average Request RTT 18
2016-08-09 14:34:23.987 Detail, Expected callbackId was received
2016-08-09 14:34:23.994 Detail, Node003, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x03, 0x05, 0x8e, 0x03, 0x03, 0x00, 0x00, 0x78
2016-08-09 14:34:23.994 Detail,
2016-08-09 14:34:23.994 Info, Node003, Response RTT 25 Average Response RTT 25
2016-08-09 14:34:23.994 Info, Node003, Max associations for node 3, group 3 is zero. Querying associations for this node is complete.
2016-08-09 14:34:23.994 Info, Node003, Adding the controller to group 3 (Send updates) of node 3
2016-08-09 14:34:23.994 Info, Node003, MultiInstanceAssociation::Set – Adding instance 0 on node 1 to group 3 of node 3
2016-08-09 14:34:23.995 Detail, Node003, Queuing (Send) MultiInstanceAssociationCmd_Set (Node=3): 0x01, 0x0b, 0x00, 0x13, 0x03, 0x04, 0x8e, 0x01, 0x03, 0x01, 0x25, 0xae, 0xe6
2016-08-09 14:34:23.995 Info, Node003, Get MultiInstanceAssociation for group 3 of node 3
2016-08-09 14:34:23.995 Detail, Node003, Queuing (Send) MultiInstanceAssociationCmd_Get (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x8e, 0x02, 0x03, 0x25, 0xaf, 0xe3
2016-08-09 14:34:23.995 Detail, Node003, Expected reply and command class was received
2016-08-09 14:34:23.995 Detail, Node003, Message transaction complete
2016-08-09 14:34:23.995 Detail,
2016-08-09 14:34:23.996 Detail, Node003, Removing current messagewhat is going on with node3(fibaro wallplug)? it is running normaly (switch on/off ok).
how to stop that.
One more thing, I think that the clear log scene template is not cleaning zwave OZW_Log.txt, TBC.août 9, 2016 à 9:49 #3664Miss Laura
ModérateurCan you check the associations of node 3?
Sounds like it’s trying to react to other devices.
Also check your scenes.Lastly you can try restarting the zwave service or disabling the debug mode on zwave, meaning it will not write logs anymore.
Have fun,
Lauraaoût 10, 2016 à 4:39 #3667macgreg0r
ParticipantI’ve restarted Zwave and event my synology an the issue was still there.
I finaly use the “clear config files” of Zwave service then cleared logs, and it seem ok now.
but I’m interested about the zwave debug mode. there is a “logging” option, is it that?
because I think this disable all zwave logs.is there a log level to configure ERROR/WARN/INFO/DEBUG somewere?
août 10, 2016 à 10:25 #3668K.Rens
Maître des clésNo, sadly it’s all or nothing in terms of logs.
Via the core you can still track a bit.
I have disabled logging for speed for instance.Kind regards,
K.Rensoctobre 7, 2016 à 10:07 #3761djandib
ParticipantHi,
my zwave now needs about 8 Minutes to turn on/off a lamp!
I ordered today a Foxx Project Range Extender, FPZWRE1EU.
May It`s going to speed up.
One question to the repeater:
actuel
shutter->Association Group 1 zwave 1 usb-stick
do I have to change it manually to:
shutter->Association Group 1 zwave 21 repeater
???octobre 10, 2016 à 11:59 #3767macgreg0r
ParticipantHi, My issue about zwave slow response was the amount of logs generated.
One device was “spaming” logs. after « clear config files » and a complete redetection, all came back to normal.
Check if your zwave logs aren’t too big, and try to clear them.
If issue is still there try to shorter the distance between your devices and zwave controler.
If still the issue, mabe a zwave extender can help.
But if my memory is good, each zwave device is a network repeater, if a node is too far from base other node will transmit commands.octobre 10, 2016 à 1:50 #3768djandib
ParticipantHi MacGregor,
I installed the Foxx-Repeater at Saturday and try to get my system run again.
(Very slow, all logs out, etc).
Do I have to associate the e.g. sensors manually?
Actuall the sensors are only associate to Group-1 Zwave 1 (my USB-Stick)What about the Button “Heal Network”?
What does it do?Andi
-
AuteurMessages
- Vous devez être connecté pour répondre à ce sujet.