gviliunas Posted November 24, 2018 Posted November 24, 2018 How does ISY stay in -sync with Z-Wave battery-powered devices? I have seven AEON MultiSensor 6 devices. (One is 12-inches from ISY so I doube it is a "real" communication problem) Quite often I see pop-up message complaining "Cannot Communicate With <Sensor Name>, Please check the connections." When I see these, the device nodes have "!" in the device tree. To bring these back, all I need do is walk by the sensor to trigger motion. Poof, it is communicating again. I suspect that ISY is expecting to hear from a battery device every x-minutes and something is getting out of sync. The questions here are: 1. How do ISY and the Battery Device stay in-sync" so ISY knows when to expect a check-in from the device? 2. Every Z-Wave device has one node with a Wakeup button and a field for a time entry. What do I do with these? 3. Is there any parameter that needs to be set in the battery device to make this more reliable?
Chris Jahn Posted November 25, 2018 Posted November 25, 2018 On 11/24/2018 at 5:59 AM, gviliunas said: How does ISY stay in -sync with Z-Wave battery-powered devices? I have seven AEON MultiSensor 6 devices. (One is 12-inches from ISY so I doube it is a "real" communication problem) Quite often I see pop-up message complaining "Cannot Communicate With <Sensor Name>, Please check the connections." When I see these, the device nodes have "!" in the device tree. To bring these back, all I need do is walk by the sensor to trigger motion. Poof, it is communicating again. I suspect that ISY is expecting to hear from a battery device every x-minutes and something is getting out of sync. The questions here are: 1. How do ISY and the Battery Device stay in-sync" so ISY knows when to expect a check-in from the device? 2. Every Z-Wave device has one node with a Wakeup button and a field for a time entry. What do I do with these? 3. Is there any parameter that needs to be set in the battery device to make this more reliable? 1. The ISY keeps in sync with battery devices, and more generally, any device that supports the WAKEUP command class by queuing certain commands such as query or scene link writes until the device wakes up. Its possible to get the communication error if you manually or use a program to query the device directly or as a member of a scene. 2. The wakeup command allows you to specify the interval at which the device wakes up. The shorter the interval, the quicker the battery will run down. 3. Not that I am aware of, but what you may want to do is keep the admin console event viewer running at level 3 and see what command the ISY is attempting prior to the device getting a communication error. This would help pinpoint the cause of the error.
asbril Posted November 25, 2018 Posted November 25, 2018 30 minutes ago, Chris Jahn said: 3. Not that I am aware of, but what you may want to do is keep the admin console event viewer running at level 3 and see what command the ISY is attempting prior to the device getting a communication error. This would help pinpoint the cause of the error. Chris, this is level 3 event log showing communication error with one of my battery operated sensors. I get these messages all the time. ISY-Events-Log.v5.0.14__Sun 2018.11.25 03.41.06 PM.txt
Chris Jahn Posted November 25, 2018 Posted November 25, 2018 2 hours ago, asbril said: Chris, this is level 3 event log showing communication error with one of my battery operated sensors. I get these messages all the time. ISY-Events-Log.v5.0.14__Sun 2018.11.25 03.41.06 PM.txt Sun 11/25/2018 03:36:26 PM : [ZWAVE-WAKEUP 124.000] Query device ZW124_1 Sun 11/25/2018 03:36:26 PM : [ZWAVE-TX ZW124_1] [80/02] Battery Get ACK,AUTO,EXPLORE To=0x7C It looks like the device is being queried either manually or by a program and thus being attempted immediately (whether or not the device is awake). If the query was queued, the message would look like this: Sun 11/25/2018 03:36:26 PM : [ZWAVE-WAKEUP 124.000] Query device ZW124_1 when awake
asbril Posted November 26, 2018 Posted November 26, 2018 13 hours ago, Chris Jahn said: Sun 11/25/2018 03:36:26 PM : [ZWAVE-WAKEUP 124.000] Query device ZW124_1 Sun 11/25/2018 03:36:26 PM : [ZWAVE-TX ZW124_1] [80/02] Battery Get ACK,AUTO,EXPLORE To=0x7C It looks like the device is being queried either manually or by a program and thus being attempted immediately (whether or not the device is awake). If the query was queued, the message would look like this: Sun 11/25/2018 03:36:26 PM : [ZWAVE-WAKEUP 124.000] Query device ZW124_1 when awake Thanks Chris, None of my sensors are in a query program, but they are are in programs to perform a specific action when activated. This specific sensor (ZW124) was set to be always awake, which I have changed now. I have 4 sensors and it is not just ZW124 that shows frequent communication errors. It is something that I rarely experienced before 5.0.13 and/or new Zwave board. With more than 60 Zwave devices I should not have an issue with the mesh network and the sensors are all close to non-battery operated Zwave devices.
SteveT Posted September 2, 2019 Posted September 2, 2019 Searching the forums for a similar issue as to what i am having... Using an AEON Multi-sensor generation 6, and the battery only lasts like 1 week while my Inteon Gen1 9v lasts like 1 year 2x CR123 batteries mind you - i switched to rechargable). I know there are more sensors, etc. but i am thinking something is hammering the battery on this one.. Either struggling with Zwave communication, or some fault in the sensor. Anything i need to check for? I dont query the sensor, it just sits there right outside my door, and there is even an Outdoor Zwave outlet sitting within 15 feet. Thanks, Steve
lilyoyo1 Posted September 2, 2019 Posted September 2, 2019 Run an event level 3 to see what's running in the background. That's where I would start
madcodger Posted October 5, 2019 Posted October 5, 2019 Any updates or resolutions to this? I’m having the same experience as gvililunas. The sensors appear to be working OK (i.e., status changes from off to on when, e.g., I open a door), but my ISY screen is filled with these error messages. So, how will I know when a device really HAS failed? This seems to be a big problem between Zwave battery devices and ISY, from the posts I’m reading
lilyoyo1 Posted October 5, 2019 Posted October 5, 2019 The same would apply to you. Run an event level 3. There is probably alot of unwanted communication. How many zwave devices do you have?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.