+- Logic Machine Forum (https://forum.logicmachine.net)
+-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1)
+--- Forum: Hardware (https://forum.logicmachine.net/forumdisplay.php?fid=12)
+--- Thread: zwave app issues (/showthread.php?tid=476)
zwave app issues - gjniewenhuijse - 28.11.2016
We have a lot of fibaro motion sensors connected to a LM4. Every motion detection packet is sended to the lm4 and every 15 minutes a temperature packet.
After restarting the lm4 we see the following behaviour:
- motion sensor detection packets and temperature packets did not received by the lm4 for 2 hours (the motion sensor wakeup interval is 7200), is that normal behaviour?
after two hours every motion detection packet is received and every 15 minutes a temperature packet.
- all devices parameters are reset to default in the lm4, not in the zwave device self. How can we get the current device parameters in the lm4 and not the default?
RE: zwave app issues - edgars - 05.12.2016
please send me ZWave log file from LogicMachine (change to your IP):
http://192.168.1.13/apps/data/zwaveapp/__log.lp
RE: zwave app issues - edgars - 08.12.2016
Quote:- motion sensor detection packets and temperature packets did not received by the lm4 for 2 hours (the motion sensor wakeup interval is 7200), is that normal behaviour?
after two hours every motion detection packet is received and every 15 minutes a temperature packet.
seems it is normal. After restart ZWave controller periodically is trying to send telegrams to it but unsuccessfully, marks them 'sleep'. And then during 2 hours all sensors wake up and inform about themselves. And only after this they start sending telegrams with temperature and motion.
E.g. Node 17 after initialization during first survey of USB stick:
Code:
2016-11-28 13:11:14.833 Info, Node017, NoOperation::Set - Routing=true
2016-11-28 13:11:14.845 Info, Node017, Sending (NoOp) message (Callback ID=0x18, Expected Reply=0x13) - NoOperation_Set (Node=17): 0x01, 0x09, 0x00, 0x13, 0x11, 0x02, 0x00, 0x00, 0x25, 0x18, 0xcb
2016-11-28 13:11:22.362 Info, Node017, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2016-11-28 13:11:22.363 Info, Node017, Node 17 has been marked as asleepAnd then at 15:05 a telegram is received informing about wakeup:
Code:
2016-11-28 15:05:20.047 Info, Node017, Received Wakeup Notification from node 17
2016-11-28 15:05:20.048 Info, Node017, Node 17 has been marked as awakeAfter this telegrams with sensor reading are being well received.
Here is description of wakeup interval parameter from Fibaro manual:
At each wake up the Fibaro Motion Sensor communicates with the main controller, updates parameter settings and the software if necessary. The Motion Sensor will wake up at a defined time interval and will ALWAYS try to communicate with the main controller Wake Up Interval set to 0 cancels the WAKE UP command frame, i.e. the device will have to be woke up manually, through the B button, sending NODE INFO command frame
It seems you just need to decrease this parameter.
Quote:- all devices parameters are reset to default in the lm4, not in the zwave device self. How can we get the current device parameters in the lm4 and not the default?
we will check this. We had such issue initially, then it was fixed.
RE: zwave app issues - gjniewenhuijse - 09.12.2016
Also the name of my zwave devices are gone (and location is never saved).