Announcement

Collapse
No announcement yet.

SDJ-Health reporting 0% battery on all my locks

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • SDJ-Health reporting 0% battery on all my locks

    Hi, I recently installed SDJ-Health and it is monitoring most of my battery devices automatically. However, all 3 of my locks (Yale locks) showing 0% battery even though their actual battery levels are 90-100%. For example, here are 2 of them:



    Click image for larger version

Name:	Screen Shot 2018-12-11 at 1.15.05 PM.png
Views:	9
Size:	109.7 KB
ID:	1265923

    I have tried it for the last week with polling and also with device monitoring both on off (it did pickup all 3 locks automatically but has never shown battery level > 0 on any of the locks).


    I have Log Poll and Wakeup messages enabled
    Click image for larger version

Name:	Screen Shot 2018-12-11 at 11.44.47 AM.png
Views:	35
Size:	23.9 KB
ID:	1265922

    I have tried checking and unchecking the "Do not update device last change time if device value does not change" box on both the Root and Battery devices, but that has no effect.

    In my HS3 log (this is from when I opened the PI config page with debugging = 2), I can see all 3 locks being referenced (root/battery devices 573/574, 590/591, 1698/1699)

    Code:
     
    Dec-11 11:46:18 AM SDJ-Health Checking status...
    Dec-11 11:45:04 AM SDJ-Health Activity Checking stopped.
    Dec-11 11:45:04 AM SDJ-Health Debug - Starting Update Activity Checking...
    Dec-11 11:45:04 AM SDJ-Health Debug - Checking Activity Devices....
    Dec-11 11:45:04 AM SDJ-Health 0 devices in Checking Activity list
    Dec-11 11:45:04 AM SDJ-Health PEData written sucessfully to root device.
    Dec-11 11:44:57 AM SDJ-Health Battery Device List finished 12 devices.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #940 RDRef #939 Not Pollable Z-Wave Exclude device Type 0
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #792 RDRef #791 Not Pollable Z-Wave Exclude device Type 0
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #840 RDRef #828 Pollable PHLocation Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #603 RDRef #599 Not Pollable Z-Wave Exclude device Type 0
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #574 RDRef #573 Pollable Z-Wave Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #591 RDRef #590 Pollable Z-Wave Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #513 RDRef #482 Not Pollable Z-Wave Exclude device Type 0
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1807 RDRef #1808 Not Pollable UltraNetatmo3 Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1789 RDRef #1790 Not Pollable UltraNetatmo3 Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1798 RDRef #1799 Not Pollable UltraNetatmo3 Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1444 RDRef #1429 Pollable PHLocation Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1699 RDRef #1698 Pollable Z-Wave Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1305 RDRef #1290 Pollable PHLocation Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1361 RDRef #1360 Not Pollable Z-Wave Exclude device Type 0
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1275 RDRef #1260 Pollable PHLocation Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1028 RDRef #1013 Pollable PHLocation Added.
    Dec-11 11:44:57 AM SDJ-Health Debug - BDRef #1051 RDRef #1036 Pollable PHLocation Added.
    Dec-11 11:44:56 AM SDJ-Health Building Battery Device List...
    Dec-11 11:44:18 AM SDJ-Health 1 queued messages processed
    Dec-11 11:44:18 AM SDJ-Health Checking status...
    Dec-11 11:44:18 AM SDJ-Health PEData written sucessfully to child device #1882
    Dec-11 11:44:18 AM SDJ-Health Device #791 found in database
    Dec-11 11:42:24 AM SDJ-Health Wake-Up Device #791 added to message queue for processing.
    Dec-11 11:42:18 AM SDJ-Health Checking status...

    And I can see Back Door lock updated its battery level this morning:

    Code:
     
    Dec-11 6:33:40 AM Z-Wave Device: Entry Back Door Lock Battery Set to 95
    Dec-11 5:44:14 AM SDJ-Health Battery device #591 polled succesfully. <-- this is "Entry Back Door Lock"
    Dec-11 1:44:14 AM SDJ-Health Battery device #574 polled succesfully. <- this is "Entry Front Door Lock", there is no battery set for this one after the poll

    But Front Door lock and my other lock polled but did not update:

    Code:
    ec-11 9:44:14 AM         SDJ-Health    Battery device #1699 polled succesfully. -- this is my 3rd lock, there was no battery set after this
    I am stumped. Can you think of anything I am doing wrong here? Is there any more info I could provide to help get to the bottom of this?

    Thanks!


    System Info:

    Current Date/Time: 12/11/2018 11:48:39 AM
    HomeSeer Version: HS3 Pro Edition 3.0.0.478
    Operating System: Microsoft Windows 10 Pro - Work Station
    System Uptime: 20 Days 17 Hours 16 Minutes 28 Seconds
    IP Address: 192.168.1.141
    Number of Devices: 757
    Number of Events: 541
    Available Threads: 399
    HSTouch Enabled: True
    Event Threads: 8
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed: Windows Defender

    Enabled Plug-Ins
    3.0.0.22: Autelis
    2.0.59.0: BLBackup
    3.0.29.0: BLGData
    1.3.4.3: Device History
    3.0.0.54: EasyTrigger
    3.0.0.32: Ecobee
    5.0.0.58: Global Cache Pro
    3.6.5.0: Harmony Hub
    3.9.610.5: HSBuddy
    1.2018.717.1011: MyQ
    3.0.0.14: NetCAM
    3.0.1.125: PHLocation
    0.0.0.44: Pushover 3P
    1.0.0.7: Restart
    30.0.0.36: RFXCOM
    3.0.6.6: SDJ-Health
    3.0.8.6: SDJ-VStat
    3.1.0.26: Sonos
    3.0.6647.37642: UltraLighting3
    3.0.0.38: Vista Alarm
    3.0.0.13: WeatherFlow
    3.0.0.88: weatherXML
    3.0.1.250: Z-Wave

  • #2
    Originally posted by mda View Post
    Hi, I recently installed SDJ-Health and it is monitoring most of my battery devices automatically. However, all 3 of my locks (Yale locks) showing 0% battery even though their actual battery levels are 90-100%.
    I'm sorry you are experiencing problems. This is not an issue I have seen before and from your log snippets I can't see what might be causing this.

    Please could you post a screenshot of the SDJ-Health child devices for these locks from the Device Management page.
    Also could you post a screenshot of the SDJ-Health tab of one of the monitoring children for one of the locks with problems.

    Where you see a 'polled successfully' message, as you have posted, it should be followed immediately by a message saying 'Polled Device #???? added to the message queue for processing'. Are they present in your log?

    Are there any error messages for SDJ-Health in your log?

    If you set the LogLevel to 2 you will get some debug messages which might help pinpoint the issue.

    If all else fails I would suggest deselecting the problematic devices from the lists of devices requiring polling or monitoring. Then delete the SDJ-Health monitoring children for those devices only. Then select the devices in the 'Select devices that require polling' list and wait for SDJ-Health to create new monitoring devices. That might clear the issue.

    Steve

    Comment


    • #3
      Originally posted by SteveMSJ View Post

      I'm sorry you are experiencing problems. This is not an issue I have seen before and from your log snippets I can't see what might be causing this.

      ...
      Thanks SteveMSJ -- PM sent with all the files. I already deleted the child monitoring devices for all 3 locks once (8 days ago) and it recreated them but only shows 0% battery. Should I do that again? Thanks!

      Comment


      • #4
        Originally posted by mda View Post

        Thanks SteveMSJ -- PM sent with all the files. I already deleted the child monitoring devices for all 3 locks once (8 days ago) and it recreated them but only shows 0% battery. Should I do that again? Thanks!
        Thanks for the comprehensive information.

        I have only had a quick look through, so far, but I think I have spotted what is probably the issue. The Battery Level Factor parameter is set globally to 1.0 but on your screenshot of the SDJ-Health tab for a lock it appears to be set locally to 0. The Battery Level Factor is a scaling parameter for adjusting ranges for devices that don't use the conventional 0-100%. The battery reading is scaled by this factor so if set to 0 it will give a reading of 0 whatever the actual battery level.

        Local parameters override the global factor but by default these should be 1.0. If you didn't change these to 0 then there is a bug in the plug-in I need to track down that is setting those on your locks. It isn't helped by the fact that your screenshots show that on your system the input boxes are being truncated to only show the first character, which is something else I need to look into. What browser are you using? I have tested on Chrome and Edge and on my system all the input text boxes on the SDJ-Health tab are at least as wide as the number of characters they contain.

        Can you change these local Battery Level Factors to 1, remember to click the Save button at the bottom right after changing the value. It might be worth then closing and reopening the SDJ-Health tab to make sure the values are sticking. See if this resolves the problem.

        Steve

        Comment


        • #5
          That was it, thanks! Changing them to 1 solved the problem. I never manually set them so I suspect there is a bug in there somewhere.

          I am using Safari on a Mac (latest version).

          Thanks again,

          -Michael

          Comment


          • #6
            Originally posted by mda View Post
            That was it, thanks! Changing them to 1 solved the problem. I never manually set them so I suspect there is a bug in there somewhere.

            I am using Safari on a Mac (latest version).

            Thanks again,

            -Michael
            Ok that’s good. I’ll try and track down why the local factor was getting set to zero to correct for a future release.

            Steve

            Comment


            • #7
              Originally posted by mda View Post
              I am using Safari on a Mac (latest version).
              Michael, I've corrected the truncated of characters in the text input boxes when using Safari. I had tested in Chrome and Edge where it displayed fine. Now tested using Safari on my iPhone and adjusted the code so they look better. They are a bit wide in Chrome and Edge now but better this way. Next update will have these changes.

              Steve

              Comment


              • #8
                Originally posted by SteveMSJ View Post

                Ok that’s good. I’ll try and track down why the local factor was getting set to zero to correct for a future release.

                Steve
                Michael,

                I have tried all ways I can to duplicate your issue where the local BatteryLevel factor for your locks had been set to zero. I can't replicate it on my system. Whilst you have corrected them successfully I would still like to track down the bug that caused it so it doesn't happen again.

                If you don't mind can you go through the procedure of setting up monitoring of one of your locks again to see if you can repeat the issue. If it does then can you document the exact steps you went through so I can try and replicate it.

                You would need to delete one of the SDJ-Health monitoring devices first.
                To do this make sure that you first remove it from the list of 'Devices requiring Polling' on the SDJ-Health tab, then delete the SDJ-Health monitoring child.

                Let me know what happens.

                Thanks,
                Steve

                Comment


                • #9
                  Originally posted by SteveMSJ View Post
                  Let me know what happens.
                  I ran the test but unfortunately I could not replicate the problem either. Sorry.

                  Here is what I did and what happened (I don't know if it was supposed to find the locks without polling enabled or not, so forgive me if most of my testing was wasted):
                  1. Confirmed global battery factor setting is still 1
                  2. Unchecked all Lock Root devices on the PI config page Polling setting
                  3. Deleted all 3 lock SDJ Health devices
                  4. Turned PI off
                  5. Waited 15 sec
                  6. Turned PI on
                  7. Polled the room with the lock devices in it
                  8. PI did not create new SDJ Health devices for the locks
                  9. Set poll rate on all 3 lock roots to 10 min (slightly staggered by a few seconds)
                  10. Opened PI cofing page, went back to devices list
                  11. Still no new SDJ Health devices
                  12. Waited 13 min
                  13. Still no new SDJ Health devices
                  14. Polled room with locks in it again
                  15. Still no new SDJ Health devices
                  16. Selected all 3 lock root devices to enable polling in the PI Config page and set polling to 10 min
                  17. Within about a minute the PI created the 3 new SDJ Health child devices
                  18. Battery level factor was correct (1) on all 3 child devices and the battery % also showing correctly

                  Is there a reason the locks need polling enabled in the PI? It seems that adding the extra polling will drain my lock batteries more quickly? Thanks,

                  Comment


                  • #10
                    Originally posted by mda View Post

                    I ran the test but unfortunately I could not replicate the problem either. Sorry.

                    Here is what I did and what happened (I don't know if it was supposed to find the locks without polling enabled or not, so forgive me if most of my testing was wasted):
                    1. Confirmed global battery factor setting is still 1
                    2. Unchecked all Lock Root devices on the PI config page Polling setting
                    3. Deleted all 3 lock SDJ Health devices
                    4. Turned PI off
                    5. Waited 15 sec
                    6. Turned PI on
                    7. Polled the room with the lock devices in it
                    8. PI did not create new SDJ Health devices for the locks
                    9. Set poll rate on all 3 lock roots to 10 min (slightly staggered by a few seconds)
                    10. Opened PI cofing page, went back to devices list
                    11. Still no new SDJ Health devices
                    12. Waited 13 min
                    13. Still no new SDJ Health devices
                    14. Polled room with locks in it again
                    15. Still no new SDJ Health devices
                    16. Selected all 3 lock root devices to enable polling in the PI Config page and set polling to 10 min
                    17. Within about a minute the PI created the 3 new SDJ Health child devices
                    18. Battery level factor was correct (1) on all 3 child devices and the battery % also showing correctly

                    Is there a reason the locks need polling enabled in the PI? It seems that adding the extra polling will drain my lock batteries more quickly? Thanks,
                    Ok, The 0 battery level factor must have been some corruption then and hopefully won't reoccur. Nobody else has reported it happening.

                    The plugin detects and automatically monitors non-listening ZWave battery devices. Listening devices, like your locks, aren't detected automatically you need to select them from the Polling list or the Activity list depending on the method you want to use. The thing is that many powered devices like multisensors have battery child devices and the pi doesn't know whether or not they are running on battery power so I decided it was best to let the user select which ones they want to monitor.

                    You don't want to set any polling on the lock devices themselves it will only drain the batteries, turn off all automatic polling that you have set on the root or any children of the lock. Once selected the pi will poll the battery device of the lock at the polling interval you set on the config page. I would recommend leaving it at the default 360 mins, but that is up to you. This will have little impact on ZWave communications and negligible battery drain.

                    Steve

                    Comment


                    • #11
                      Thanks!

                      Comment

                      Working...
                      X