heardc Posted August 10, 2016 Posted August 10, 2016 I have numerous Z-wave Eco-Link door sensors and Motion Sensors that are all no longer reporting battery level. After installation, battery level was getting updated. Now I get no entry for Battery Level on the java based UI. I wrote many programs to update me when battery levels get low, now I just get no status at all. Has anyone else seen this?
sn0cr4sh Posted August 11, 2016 Posted August 11, 2016 Actually. Yeah, same thing here. Same devices, same issue. That's really odd. -Edit - I have 5 of the EcoLink PIRs. They all work properly with my programs, but only ONE of them displays battery status. I wonder if that is significant, is there some kind of bug where multiiple of the same kind of device will only show one of their battery status? Sent from my iPhone using Tapatalk
Chris Jahn Posted August 11, 2016 Posted August 11, 2016 Are these devices communicating any events to the ISY?
sn0cr4sh Posted August 12, 2016 Posted August 12, 2016 Are these devices communicating any events to the ISY? Mine are set to work with programs to trigger lights (other Zwave devices). They all work like they should - no issues. Is that what you mean? Sent from my iPhone using Tapatalk
Chris Jahn Posted August 12, 2016 Posted August 12, 2016 Mine are set to work with programs to trigger lights (other Zwave devices). They all work like they should - no issues. Is that what you mean? Sent from my iPhone using Tapatalk Yes, I was just wondering if ISY was getting any events from the devices. For those devices not reporting battery status, I'm wondering if the default associations were not set when you added the device (because of comm errors), or possibly if there is some configuration parameters specifically for that device that can be set to turn on/off battery status reports.
sn0cr4sh Posted August 12, 2016 Posted August 12, 2016 Yes, I was just wondering if ISY was getting any events from the devices. For those devices not reporting battery status, I'm wondering if the default associations were not set when you added the device (because of comm errors), or possibly if there is some configuration parameters specifically for that device that can be set to turn on/off battery status reports. I'm not actually sure. I have several folders in my setup - one for each room. Each folder has a motion sensor and a light - all Zwave. So I don't have any scenes, and I don't know how to set associations. How does that work with Zwave devices?
heardc Posted August 12, 2016 Author Posted August 12, 2016 Are these devices communicating any events to the ISY?
heardc Posted August 12, 2016 Author Posted August 12, 2016 Yes the ISY is getting binary status updates reliably. Maybe there is a config parameter out there. It's weird that all of my battery powered sensor stopped updating the ISY at the same time.
Chris Jahn Posted August 13, 2016 Posted August 13, 2016 I'm not actually sure. I have several folders in my setup - one for each room. Each folder has a motion sensor and a light - all Zwave. So I don't have any scenes, and I don't know how to set associations. How does that work with Zwave devices? When a device is added to the ISY, we add some default associations so the ISY will be updated whenever the Z-Wave device has something to report (this is independent of actual scene support). Yes the ISY is getting binary status updates reliably. Maybe there is a config parameter out there. It's weird that all of my battery powered sensor stopped updating the ISY at the same time. This is strange because the ISY wouldn't all of sudden start ignoring these messages. One way to test would be to put the Admin Console event viewer on level 3 and just leave it running for awhile to see if we are getting some unexpected messages/message content that we are ignoring.
heardc Posted September 2, 2016 Author Posted September 2, 2016 I just made some progress on this. You can get the ISY to report battery level by doing the following: 1) Remove cover on door or motion sensor. This enables the Tamper Alarm. 2) Remove battery, wait a few seconds. 3) Replace battery, then as quick as you can, click on the query button. 4) Battery status comes back up. After doing this I found out that I had a battery level at 24%, but the ISY never knew about it. I wrote a program to query the device when the state changes, but this doesn't work either.
Chris Jahn Posted September 3, 2016 Posted September 3, 2016 I just made some progress on this. You can get the ISY to report battery level by doing the following: 1) Remove cover on door or motion sensor. This enables the Tamper Alarm. 2) Remove battery, wait a few seconds. 3) Replace battery, then as quick as you can, click on the query button. 4) Battery status comes back up. After doing this I found out that I had a battery level at 24%, but the ISY never knew about it. I wrote a program to query the device when the state changes, but this doesn't work either. The query in your program may be failing because the device is no longer awake. It would be interesting to see if the problems go away if you put in a fresh battery.
sn0cr4sh Posted September 7, 2016 Posted September 7, 2016 I don't think the re-query solution above is helpful because the battery status just eventually disappears. I had one of my sensors showing its status, but now even that one stopped doing it. I would like to figure this out, if possible. My motion sensors get used every day to trigger lights, and those still work, btw. I grabbed some logs: Node Information, Query, and a Program being run. I do see an error "Unexpected Null Database..." Is that significant? Here is the node information for one sensor: Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] ---------------------------------------------- Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] ZW021_1 uid=21 type=4.32.1 mid=330 tid=1 pid=1 model=0 Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x30 V0 SENSOR_BINARY Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x71 V2 NOTIFICATION Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x86 V0 VERSION Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x85 V2 ASSOCIATION Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x84 V2 WAKE_UP Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x80 V0 BATTERY Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x70 V1 CONFIGURATION Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - xEF V0 MARK Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] - x20 V0 BASIC Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] Tue 09/06/2016 07:59:48 PM : [ZW-SHOW ] ---------------------------------------------- Tue 09/06/2016 07:59:48 PM : [UZW-CMD 5 ] Show Node Details : ZW021_1 Here is logging that comes up when I force a Query on the device: Tue 09/06/2016 07:54:31 PM : [ZWAVE-TX ZW021_1] [0109001315028002]... Tue 09/06/2016 07:54:31 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:54:31 PM : [ZWAVE-RX ] [0104011301E8] Tue 09/06/2016 07:54:31 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:54:36 PM : [ZWAVE-TX ZW021_1] [0109001315028002]... Tue 09/06/2016 07:54:36 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:54:36 PM : [ZWAVE-RX ] [0104011301E8] Tue 09/06/2016 07:54:36 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:54:38 PM : [ZWAVE-RX ] [010500134701AF] Tue 09/06/2016 07:54:38 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:54:41 PM : [ZWAVE-TX ZW021_1] [0109001315028002]... Tue 09/06/2016 07:54:41 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:54:41 PM : [ZWAVE-RX ] [0104011301E8] Tue 09/06/2016 07:54:41 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:54:42 PM : [ZWAVE-RX ] [010500134701AF] Tue 09/06/2016 07:54:42 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:54:46 PM : [ZWAVE-WAKEUP 21] Query device when awake ZW021_1 Tue 09/06/2016 07:54:47 PM : [ZWAVE-RX ] [010500134701AF] Tue 09/06/2016 07:54:47 PM : [ZWAVE-TX ] ACK Here is the logging for when my Program runs (Motion detected, turn on lights, wait 45s, turn off lights) Tue 09/06/2016 07:56:05 PM : [ZWAVE-RX ZW021_1] [0109000400150330]... Tue 09/06/2016 07:56:05 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:05 PM : [D2D EVENT ] Event [ZW021_1] [ST] [100] uom=78 prec=0 Tue 09/06/2016 07:56:05 PM : [ ZW021_1] ST 100 (uom=78 prec=0) Tue 09/06/2016 07:56:05 PM : [D2D-CMP 0004] STS [ZW021_1] ST op=1 Event(val=100 uom=78 prec=0) is Condition(val=100 uom=78 prec=-1) --> true Tue 09/06/2016 07:56:05 PM : [D2D EVENT ] Event [ZW021_1] [DON] [100] uom=78 prec=0 Tue 09/06/2016 07:56:05 PM : [ ZW021_1] DON 100 (uom=78 prec=0) Tue 09/06/2016 07:56:06 PM : [ZWAVE-RX ZW021_1] [0109000400150320]... Tue 09/06/2016 07:56:06 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:06 PM : [ZWAVE-TX ZW024_1] [010A001318032601]... Tue 09/06/2016 07:56:06 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:56:06 PM : [ZWAVE-RX ] [0104011301E8] Tue 09/06/2016 07:56:06 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:06 PM : [ZWAVE-RX ] [010500134800A1] Tue 09/06/2016 07:56:06 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:06 PM : [D2D EVENT ] Event [ZW024_1] [DON] [100] uom=78 prec=0 Tue 09/06/2016 07:56:06 PM : [ ZW024_1] DON 100 (uom=78 prec=0) Tue 09/06/2016 07:56:06 PM : [D2D EVENT ] Event [ZW021_1] [DON] [100] uom=78 prec=0 Tue 09/06/2016 07:56:06 PM : [ ZW021_1] DON 100 (uom=78 prec=0) Tue 09/06/2016 07:56:09 PM : [ZWAVE-TX ZW024_1] [0109001318022602]... Tue 09/06/2016 07:56:09 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:56:09 PM : [ZWAVE-RX ] [0104011301E8] Tue 09/06/2016 07:56:09 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:09 PM : [ZWAVE-RX ] [010500134900A0] Tue 09/06/2016 07:56:09 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:09 PM : [ZWAVE-RX ZW024_1] [0109000400180326]... Tue 09/06/2016 07:56:09 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:09 PM : [D2D EVENT ] Event [ZW024_1] [ST] [17] uom=51 prec=0 Tue 09/06/2016 07:56:09 PM : [ ZW024_1] ST 17 (uom=51 prec=0) Tue 09/06/2016 07:56:13 PM : [ZWAVE-RX ZW021_1] [0109000400150330]... Tue 09/06/2016 07:56:13 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:13 PM : [D2D EVENT ] Event [ZW021_1] [ST] [0] uom=78 prec=0 Tue 09/06/2016 07:56:13 PM : [ ZW021_1] ST 0 (uom=78 prec=0) Tue 09/06/2016 07:56:13 PM : [D2D-CMP 0004] STS [ZW021_1] ST op=1 Event(val=0 uom=78 prec=0) is Condition(val=100 uom=78 prec=-1) --> false Tue 09/06/2016 07:56:13 PM : [D2D EVENT ] Event [ZW021_1] [DOF] [0] uom=78 prec=0 Tue 09/06/2016 07:56:13 PM : [ ZW021_1] DOF 0 (uom=78 prec=0) Tue 09/06/2016 07:56:20 PM : [ZWAVE-RX ZW030_1] [010C0004001E0631]... Tue 09/06/2016 07:56:20 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:20 PM : [ZWAVE-PROCESS ] Process value Sensor type=2 uomId=1 prec=2 Tue 09/06/2016 07:56:20 PM : [D2D EVENT ] Event [ZW030_118] [GPV] [284800] uom=56 prec=2 Tue 09/06/2016 07:56:20 PM : [ ZW030_118] GPV 284800 (uom=56 prec=2) Tue 09/06/2016 07:56:22 PM : [ZWAVE-RX ] [01080004000C0284]... Tue 09/06/2016 07:56:22 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:22 PM : [ZWAVE-DB ] Unexpected NULL database for uid=12 0x0C Tue 09/06/2016 07:56:23 PM : [ZWAVE-TX ] [01030002FE] Tue 09/06/2016 07:56:23 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:56:23 PM : [ZWAVE-RX ] [0125010205001D05]... Tue 09/06/2016 07:56:23 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:23 PM : [ZWAVE-NODE-SYNC] ---- Start Processing Z-Wave Node 12 (0x0C) ---- Tue 09/06/2016 07:56:23 PM : [ZWAVE-NODE-SYNC] -- Finished -- ISY/Z-Wave Node Sync -- Tue 09/06/2016 07:56:50 PM : [ZWAVE-TX ZW024_1] [010A001318032601]... Tue 09/06/2016 07:56:50 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:56:50 PM : [ZWAVE-RX ] [0104011301E8] Tue 09/06/2016 07:56:50 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:50 PM : [ZWAVE-RX ] [010500134A00A3] Tue 09/06/2016 07:56:50 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:50 PM : [D2D EVENT ] Event [ZW024_1] [DOF] [0] uom=78 prec=0 Tue 09/06/2016 07:56:50 PM : [ ZW024_1] DOF 0 (uom=78 prec=0) Tue 09/06/2016 07:56:51 PM : [ZWAVE-RX ZW030_1] [010C0004001E0631]... Tue 09/06/2016 07:56:51 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:51 PM : [ZWAVE-PROCESS ] Process value Sensor type=2 uomId=1 prec=2 Tue 09/06/2016 07:56:51 PM : [D2D EVENT ] Event [ZW030_118] [GPV] [284900] uom=56 prec=2 Tue 09/06/2016 07:56:51 PM : [ ZW030_118] GPV 284900 (uom=56 prec=2) Tue 09/06/2016 07:56:53 PM : [ZWAVE-TX ZW024_1] [0109001318022602]... Tue 09/06/2016 07:56:53 PM : [ZWAVE-RX ] ACK Tue 09/06/2016 07:56:53 PM : [ZWAVE-RX ] [0104011301E8] Tue 09/06/2016 07:56:53 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:53 PM : [ZWAVE-RX ] [010500134B00A2] Tue 09/06/2016 07:56:53 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:53 PM : [ZWAVE-RX ZW024_1] [0109000400180326]... Tue 09/06/2016 07:56:53 PM : [ZWAVE-TX ] ACK Tue 09/06/2016 07:56:53 PM : [D2D EVENT ] Event [ZW024_1] [ST] [0] uom=51 prec=0 Tue 09/06/2016 07:56:53 PM : [ ZW024_1] ST 0 (uom=51 prec=0)
Chris Jahn Posted September 7, 2016 Posted September 7, 2016 Hi sn0cr4sh, I'm not sure why the 'unexpected NULL database' message appears, but it looks like it may be a device that was removed from your network but wasn't excluded. It shouldn't cause any problems though. Looking through the trace, there is nothing I can see that is causing a problem. Have you tried (even temporarily) to replace the battery and see if it starts sending status again? I don't know, but I'm wondering if the eco-link gets to a low battery situation that it stops sending battery status.
heardc Posted September 7, 2016 Author Posted September 7, 2016 I am having this problem with battery levels all over 80%, so it's not a "low battery" situation. So far I have confirmed that the ISY never gets an updated battery level ever...without removing, replacing and running a query while the motion sensor is awake. This is the case with a Fibaro and Ecolink sensors.
GoBruins Posted September 7, 2016 Posted September 7, 2016 I am having this problem with battery levels all over 80%, so it's not a "low battery" situation. So far I have confirmed that the ISY never gets an updated battery level ever...without removing, replacing and running a query while the motion sensor is awake. This is the case with a Fibaro and Ecolink sensors. I've got the same issue with a Ecolink Z-Wave PIR motion detector and an Everspring water detector, The battery level is not viewable on my ISY, I should mention, my ISY is running 5.0.4.
Chris Jahn Posted September 8, 2016 Posted September 8, 2016 Hi guys, I'm not sure why this would be happening, we need to get one of these to test with. We've added more logging in v5.0.5 so it will be easier to determine the source of problems like these.
gduprey Posted September 13, 2016 Posted September 13, 2016 I've had similar things happen with devices that worked great and then stopped reporting battery levels. I have 6 Kwikset locks (all 914 units) that all work great, but one just stopped sending battery status updates. I repaired links, queried it,etc. I got the battery level again, but then it stopped updating. The locks have been in service for 2 years and 14 months of that has been with the ISY and worked fine. No idea what changed. Other locks are fine and this one will report being opened, closed, etc, just never includes battery state. I have about 20 Everspring temp/humidity sensors. All worked fine for 2 full years, then one stopped sending any update at all (temp,humidity or battery). If I "woke" it up, it could be queried, but once it went to sleep, it never reported again. Good, strong battery and I did a heal and repair links -- all succeeded, but no more reports. Again, was working for a long time, then just stopped. I have at least one Ecolink door sensor that stopped reporting battery status too after working for over a year. It seems that whatever is going wrong, once it "breaks", that's it. My setup depends too heavily on device identifiers to remove and re-add these things (I made a request a long time ago to be able to add aliases so that changing assigned device IDs didn't break the universe/outside world, but....), so I'm "limping" by (that said, the other 30+ ZWave devices continue to report status correctly).Just another datapoint. Gerry
mwester Posted September 13, 2016 Posted September 13, 2016 Ditto. I got battery levels for a while, but no longer. As Gerry mentioned, it's just too painful to modify all the programs and references, so I've chosen to live with the problem rather than spend a lot of time digging into it. I know I'm going to regret that as soon as one of the devices stops reporting because of a battery failure, but that's sort of the "leaky roof" problem (Can't fix the roof when it's leaking 'cause it's raining outside, and won't fix the roof when it's sunny 'cause when it's sunny outside, the roof isn't leaking...)
Chris Jahn Posted September 13, 2016 Posted September 13, 2016 Thanks Guys, What ISY versions are you running? We definitely see a need for a 'replace device' capability in ISY that will keep the old Z-Wave address (it won't be in 5.0.5, but hopefully one of the builds soon after that). And just to be clear, you are getting all your other events (such as 'door unlocked' etc.), just not battery status, correct?
mwester Posted September 13, 2016 Posted September 13, 2016 My z-wave sensors on my 5.0.2 ISY -- and yes, the other events all show up just fine.
gduprey Posted September 13, 2016 Posted September 13, 2016 I'm running 5.0.2 on one system (the one with the everspring temp sensor that stopped sending reports) and 4.3.26 on the one where the Kwickset lock & ecolink door sensor stopped reporting battery. The temp sensor stopped reporting anything unless I wake it up and query it. The other two still report normal activity (lock/unlock/door open/closed), just don't include battery (and in the admin console, you don't see a battery status on those devices, though sometimes I can query the Kwikset and get a battery status to appear, but it doesn't auto-update).
Chris Jahn Posted September 13, 2016 Posted September 13, 2016 My z-wave sensors on my 5.0.2 ISY -- and yes, the other events all show up just fine. One more question, if you wake a device up and query it, do you get all your status except battery in that case as well?
gduprey Posted September 13, 2016 Posted September 13, 2016 When I query it (Kwiksets don't need to be woken up, ecolincs and everspring units do), sometimes I'll get a battery report (I always get a response). Gerry
heardc Posted September 14, 2016 Author Posted September 14, 2016 I am running Zwave 4.55 and ISY 4.5.1. Should I upgrade? Sorry to add another issue, my "tamper alarms" associated with these devices never shuts off, always stays on forever unless I reboot the ISY. Then there is no status for Tamper Alarm.
gduprey Posted September 14, 2016 Posted September 14, 2016 I wonder if the tamper alarm is like the insteon leak sensors -- they stay tripped until you query them (for leak sensors, querying them clears a leak condition). I'd be curious if querying the tamper node clears it. Gerry
Recommended Posts
Archived
This topic is now archived and is closed to further replies.