larryllix Posted January 7, 2016 Posted January 7, 2016 Larry, A 3:00 AM Query will not in fact reset a low battery node state . . . Are you saying that a general Query will not reset the Lowbatt status to off? LeeG stated "The Motion Sensor Low Bat node does not go back to Off state on its own. Once the battery has been replaced right click on Low Bat node and select Query. This will cause the ISY to reset the Low Bat node to Off. Below are two examples where I right clicked and selected Query on two Motion Sensors. Note that no actual Query command was sent to the Motion Sensor. The Query request simply directs the ISY to reset the Low Bat node to Off." I tend to believe that, as an explanation why I have had almost a dozen LowBatts recorded, or MS units went nuts, and yet have never seen a LowBatt status as On yet. I don't get that many power failures to buy the blank status on those but I am just trying to understand why I never see this status as On, yet, with 10 MS units. Does this means that a single device query does different things in ISY than a general Query??
Teken Posted January 7, 2016 Posted January 7, 2016 Are you saying that a general Query will not reset the Lowbatt status to off? LeeG stated "The Motion Sensor Low Bat node does not go back to Off state on its own. Once the battery has been replaced right click on Low Bat node and select Query. This will cause the ISY to reset the Low Bat node to Off. Below are two examples where I right clicked and selected Query on two Motion Sensors. Note that no actual Query command was sent to the Motion Sensor. The Query request simply directs the ISY to reset the Low Bat node to Off." I tend to believe that, as an explanation why I have had almost a dozen LowBatts recorded, or MS units went nuts, and yet have never seen a LowBatt status as On yet. I don't get that many power failures to buy the blank status on those but I am just trying to understand why I never see this status as On, yet, with 10 MS units. Does this means that a single device query does different things in ISY than a general Query?? I posed this exact same question in one of the beta firmware releases and going off memory it was in 4.4.1. Essentially there are two types of queries which I never knew existed until I had this problem. The 3:00 AM Query (I am generalizing here) say for example checks for three things. Where as a manual query initiated by the user checks for say five things. Again, I am offering an example of what I was told and the value I indicated should not be used as a reference. But, simply as an example that there are two distinct queries in the system. So that goes back to your question a 3:00 AM Query will not in fact reset a low battery node from on to off. I know this because I've watched and documented this for more than four years. The only time the low battery node will go away completely is from a reboot or loss of power etc. This is why there are so many people asking *How do I reset the low battery node* in this forum. Clear as mud?
LeeG Posted January 7, 2016 Posted January 7, 2016 I'll run the Event Viewer for the 3AM Query. I don't think any battery powered device is queried at 3AM because they are asleep.
larryllix Posted January 8, 2016 Posted January 8, 2016 (edited) Interesting! This means that the device query, not being able to query a battery device, instead of changing the status to blank, 'cause ISY doesn't know, sets the status to Off without any confirmation of status. Edited January 8, 2016 by larryllix
LeeG Posted January 8, 2016 Posted January 8, 2016 The manual Query of Motion Sensor Low Bat node does reset the node to Off. That is the expected process to reset Low Bat node after battery replaced. If the manual Query is done without replacing battery the Low Bat=On is lost. The 3AM Query Program has no affect on Motion Sensor Low Bat node.
larryllix Posted January 9, 2016 Posted January 9, 2016 The manual Query of Motion Sensor Low Bat node does reset the node to Off. That is the expected process to reset Low Bat node after battery replaced. If the manual Query is done without replacing battery the Low Bat=On is lost. The 3AM Query Program has no affect on Motion Sensor Low Bat node. Thank you LeeG! I wonder what ever happened to my maybe 8 or 9 LowBatts though? This is why I wrote a recording program because I have never got a valid notification but have recorded a few after installing code for it. hmmm... I'll be watching closer next time.
LeeG Posted January 9, 2016 Posted January 9, 2016 larryllix Sorry but a little confused. You have received/triggered a Program that is looking for Low Bat but got no notification?
Teken Posted January 9, 2016 Posted January 9, 2016 larryllix Sorry but a little confused. You have received/triggered a Program that is looking for Low Bat but got no notification? He is not seeing the low battery node show a on status. Ideals are peaceful - History is violent
larryllix Posted January 9, 2016 Posted January 9, 2016 larryllix Sorry but a little confused. You have received/triggered a Program that is looking for Low Bat but got no notification? Just as Teken reported above. I have received LowBatt notifications from triggered programs. I have recorded LowBatt triggers in my Lowbatt list program several times, I have had MS units go berserk or stop detecting from dying batteries and no notifications, but I have never seen a LowBatt status = On in my ISY device pages, yet. Just very strange and I was accepting various reasons for this. Now I am back to wondering why again.
Teken Posted January 9, 2016 Posted January 9, 2016 What are the hardware production date, revision, and ISY firmware of these MS units? Ideals are peaceful - History is violent
larryllix Posted January 9, 2016 Posted January 9, 2016 What are the hardware production date, revision, and ISY firmware of these MS units? Ideals are peaceful - History is violent 7 units are v.41 3 units are v.44 all purchased from two years ago to a few months ago. Oldest IP address 28.40.XX to newest 36.94.XX Not sure which ones did what now but most have had their batteries replaced from new and maybe 5 have ever reported LowBatt. I have to assume the rest acted strangely, with flashing LED, intermittent operation or just quit working. I currently have two that reported LowBatt about a month ago and they still work fine. I haven't bothered yet as both those units had new batteries about two months ago. One has to be factory reset and relinked every time I replace the battery.
Teken Posted January 9, 2016 Posted January 9, 2016 Those MS are too new to have a firmware issue. Ideals are peaceful - History is violent
Techman Posted January 9, 2016 Posted January 9, 2016 I had several MS that I believe were firmware version .41. When the batteries were low they started sending continuous on commands, but no low battery signal. I've since replaced them with firmware version .44. I'm using lithium batteries which seem to last about 2 years (in mild climate) so it's too early to tell if the current firmware fixed the low battery problem.
Recommended Posts