Jimbo.Automates Posted May 28, 2017 Posted May 28, 2017 I've was adding some new z-wave devices today, and all the sudden for one of my existing z-wave battery operated devices the log started going crazy with zwave-wakeup not putting device back to sleep messages every second. I pulled the battery from that device and it stopped, then I put the battery back in and it stopped. Now one of my new devices is doing the same thing, If I have the option set to put them back sleep, then I get this in the log every few seconds: Sun 05/28/2017 04:02:37 PM : [ZWAVE-WAKEUP 37] Put back to sleep ZW037_1 Sun 05/28/2017 04:02:37 PM : [ZWAVE-RX ] [01050013FD0014] [00/00] CC=0x00 cmd=0x00 [] ACK,AUTO,EXPLORE Sun 05/28/2017 04:02:38 PM : [ZWAVE-RX ] [01050013FD0115] [00/00] CC=0x00 cmd=0x00 [] ACK,AUTO,EXPLORE Sun 05/28/2017 04:02:42 PM : [ZW-TX-FAILED] 3.0/0x31.04 This device was configured and working fine and only waking up every once a minute for a few hours, then I added another new device and then it started going crazy. The even more strange thing is that I pull the batter from the device, and the log continued to show messages that the device was waking up! This has made the ISY almost unusable because it's so busy with this. Any ideas what could be going on? - Jim
Jimbo.Automates Posted May 29, 2017 Author Posted May 29, 2017 Have you tried power cycling ISY?Yes, power cycle did fix it. But it happened twice today so would like to understand what put it in that situation. Especially with a powered off device. Sent from my Nexus 6P using Tapatalk
Michel Kohanim Posted May 29, 2017 Posted May 29, 2017 Hi Jimbo, I am assuming you are on 5.0.10? What kind of device is this? With kind regards, Michel
Jimbo.Automates Posted May 29, 2017 Author Posted May 29, 2017 Yes Michel, 5.0.10. I was just replying to this I had left the admin console open overnight with the log, and this morning it was full of messages saying: Awake with no pending work, not putting back to sleep ZW037_1 I tried to copy the log, but admin console was not responding, I closed it, and then could not reconnect so had to restart ISY. This device is a http://www.everspring.com/ST814.aspx but yesterday it was Aeotec ZW097 dry contact sensor. I had left the setting to keep devices awake since I was adding new devices, but have now set it to put devices back to sleep.
Jimbo.Automates Posted June 6, 2017 Author Posted June 6, 2017 I had this happen again during a network heal on a different device which is a Aeotec Door/Window sensor at my lake house Mon 06/05/2017 09:16:18 PM : [ZWAVE-WAKEUP 28] Network Heal awakened device ZW028_1 Mon 06/05/2017 09:16:18 PM : [ZWAVE-HEAL 28] Updating Neighbors for 'Door Garage Notify Sensor' : Time allowed=44 seconds Mon 06/05/2017 09:16:19 PM : [ZWAVE-HEAL 28] Updating Neighbors for 'Door Garage Notify Sensor' : working ... Mon 06/05/2017 09:16:19 PM : [ ZW033_157] DON 100 (uom=78 prec=0) Mon 06/05/2017 09:16:19 PM : [ ZW033_157] DON 100 (uom=78 prec=0) Mon 06/05/2017 09:16:19 PM : [ ZW033_157] DON 100 (uom=78 prec=0) Mon 06/05/2017 09:16:19 PM : [ ZW033_157] DON 100 (uom=78 prec=0) Mon 06/05/2017 09:16:20 PM : [ ZW033_157] DON 100 (uom=78 prec=0) Mon 06/05/2017 09:16:22 PM : [ ZW033_157] DON 100 (uom=78 prec=0) Mon 06/05/2017 09:16:38 PM : [ZWAVE-HEAL 28] Updating Neighbors for 'Door Garage Notify Sensor' : Failed Mon 06/05/2017 09:16:38 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 Mon 06/05/2017 09:16:38 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 Mon 06/05/2017 09:16:38 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 Mon 06/05/2017 09:16:38 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 Mon 06/05/2017 09:16:38 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 ... Mon 06/05/2017 09:17:00 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 Mon 06/05/2017 09:17:00 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 Mon 06/05/2017 09:17:00 PM : [ZWAVE-WAKEUP 28] Not putting back to sleep ZW028_1 Mon 06/05/2017 09:17:00 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:17:16 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:17:32 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:17:48 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:18:04 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:18:20 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:18:36 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:18:52 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:19:08 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:19:24 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:19:40 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:19:56 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:20:12 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 Mon 06/05/2017 09:20:16 PM : [ZWAVE-WAKEUP 28] Awake with no pending work, putting back to sleep ZW028_1 Mon 06/05/2017 09:20:37 PM : [ZWAVE-WAKEUP 28] Put back to sleep ZW028_1 The "..." is where I removed a ton of lines. Once I told it to put devices back to sleep then it calmed down, so the device is waking up ever 15 seconds.
Chris Jahn Posted June 6, 2017 Posted June 6, 2017 Hi Jimbo, It looks like the wakeup interval is being set to a very low value somehow. Thanks for all the details, we've added it the list and we'll try to recreate it here.
Jimbo.Automates Posted June 6, 2017 Author Posted June 6, 2017 Thanks Chris. Also, I continued to get the 'Put back to sleep' messages until I rebooted the ISY.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.