Announcement

Collapse
No announcement yet.

Plugin to monitor Z-Wave battery device Health - CLOSED

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

  • Originally posted by ralnet View Post
    Sparkman

    I just installed the new plug-in but it does not show up in my manage plug-in files. Just prior to this I did an HS3 upgrade (HS3 Standard Edition 3.0.0.312 (Windows). Any thoughts?
    Bob
    Hi Bob,

    Have you tried restarting HS after?

    Cheers
    Al
    HS 3.0.0.548: 1990 Devices 1172 Events
    Z-Wave 3.0.1.262: 126 Nodes on one Z-Net

    Comment


    • I've updated to 3.0.4.0 but when I try to access the config I get the error message and log entrys below.

      ERROR in GetPagePlugin: Item has already been added. Key in dictionary: 'Livingroom Z-Wave Fibaro On/Off Sensor(Z-Wave)' Key being added: 'Livingroom Z-Wave Fibaro On/Off Sensor(Z-Wave)'

      Mar-07 15:49:54 SDJ-Health Failed to find battery child.
      Mar-07 15:49:54 SDJ-Health Failed to find battery child.
      Mar-07 15:49:54 SDJ-Health Activity Checking stopped.
      Mar-07 15:49:54 SDJ-Health Polling devices stopped.
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #989
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #988
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #987
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #986
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #985
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1048
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1047
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1038
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1030
      Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1028
      Mar-07 15:49:42 Plug-In Finished initializing plug-in SDJ-Health
      Mar-07 15:49:42 SDJ-Health Version 3.0.4.0 Initialized.

      I stopped HS3, copied in the .exe and the images folder, restarted HS3. I've even stopped the plugin and deleted the .ini and .ini backup file and restarted but still the same error.

      Any ideas what might be causing this?

      Thanks
      Simon

      Comment


      • Originally posted by Simonk View Post
        I've updated to 3.0.4.0 but when I try to access the config I get the error message and log entrys below.

        ERROR in GetPagePlugin: Item has already been added. Key in dictionary: 'Livingroom Z-Wave Fibaro On/Off Sensor(Z-Wave)' Key being added: 'Livingroom Z-Wave Fibaro On/Off Sensor(Z-Wave)'

        Mar-07 15:49:54 SDJ-Health Failed to find battery child.
        Mar-07 15:49:54 SDJ-Health Failed to find battery child.
        Mar-07 15:49:54 SDJ-Health Activity Checking stopped.
        Mar-07 15:49:54 SDJ-Health Polling devices stopped.
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #989
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #988
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #987
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #986
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #985
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1048
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1047
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1038
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1030
        Mar-07 15:49:54 SDJ-Health PEData read sucessfully from child device #1028
        Mar-07 15:49:42 Plug-In Finished initializing plug-in SDJ-Health
        Mar-07 15:49:42 SDJ-Health Version 3.0.4.0 Initialized.

        I stopped HS3, copied in the .exe and the images folder, restarted HS3. I've even stopped the plugin and deleted the .ini and .ini backup file and restarted but still the same error.

        Any ideas what might be causing this?

        Thanks
        Simon
        It looks like something might be a bit messed up with the monitoring devices. If this was upgraded from the earlier version then perhaps something didn't convert correctly. The error in GetPagePlugin is because it is trying to add two devices with the same name to the list. It is probably due to the same issue but it's not impossible to have 2 devices named the same so I have corrected that bug and uploaded 3.0.4.1 to the earlier post. This will hopefully allow you to open the Config page. Change to LogLevel 2 and restart the plugin which should give me a bit more information to track down which devices it is having problems with.

        Steve

        Comment


        • Sparkman, Yes I rebooted the system but it got originally hung up because I just dumped the HTML into the image file. The plug-in did not like that.

          Comment


          • Originally posted by SteveMSJ View Post
            It looks like something might be a bit messed up with the monitoring devices. If this was upgraded from the earlier version then perhaps something didn't convert correctly. The error in GetPagePlugin is because it is trying to add two devices with the same name to the list. It is probably due to the same issue but it's not impossible to have 2 devices named the same so I have corrected that bug and uploaded 3.0.4.1 to the earlier post. This will hopefully allow you to open the Config page. Change to LogLevel 2 and restart the plugin which should give me a bit more information to track down which devices it is having problems with.

            Steve
            I left it running for 10 minutes, filtered log below.

            Code:
            Mar-07 21:58:47	 	SDJ-Health	Device #508 added to message queue for processing.
            Mar-07 21:58:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:58:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:58:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:58:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:58:38	 	SDJ-Health	Checking status...
            Mar-07 21:56:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:56:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:56:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:56:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:56:38	 	SDJ-Health	Checking status...
            Mar-07 21:54:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:54:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:54:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:54:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:54:38	 	SDJ-Health	Checking status...
            Mar-07 21:52:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:52:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:52:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:52:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:52:38	 	SDJ-Health	Checking status...
            Mar-07 21:52:38	 	SDJ-Health	PEData written sucessfully to child device #987
            Mar-07 21:52:38	 	SDJ-Health	Device #674 found in database
            Mar-07 21:51:24	 	SDJ-Health	Device #674 added to message queue for processing.
            Mar-07 21:50:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:50:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:50:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:50:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:50:38	 	SDJ-Health	Checking status...
            Mar-07 21:50:38	 	SDJ-Health	PEData written sucessfully to child device #988
            Mar-07 21:50:37	 	SDJ-Health	Device #684 found in database
            Mar-07 21:50:17	 	SDJ-Health	Device #684 added to message queue for processing.
            Mar-07 21:48:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:48:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:48:38	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:48:38	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:48:38	 	SDJ-Health	Checking status...
            Mar-07 21:48:38	 	SDJ-Health	PEData written sucessfully to child device #985
            Mar-07 21:48:38	 	SDJ-Health	Device #678 found in database
            Mar-07 21:47:18	 	SDJ-Health	Device #678 added to message queue for processing.
            Mar-07 21:46:40	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:46:40	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:46:40	 	SDJ-Health	Warnig - Battery devices #0 not found!
            Mar-07 21:46:40	 	SDJ-Health	Failed to find battery child.
            Mar-07 21:46:40	 	SDJ-Health	Checking status...
            Mar-07 21:46:40	 	SDJ-Health	Activity Checking stopped.
            Mar-07 21:46:40	 	SDJ-Health	Debug - Starting Update Activity Checking...
            Mar-07 21:46:40	 	SDJ-Health	0 devices in Checking Activity list
            Mar-07 21:46:40	 	SDJ-Health	Debug - Checking Activity Devices....
            Mar-07 21:46:40	 	SDJ-Health	Polling devices stopped.
            Mar-07 21:46:40	 	SDJ-Health	Debug - Starting Update Polling...
            Mar-07 21:46:40	 	SDJ-Health	0 devices in polling list
            Mar-07 21:46:40	 	SDJ-Health	Debug - Checking Poll Devices....
            Mar-07 21:46:40	 	SDJ-Health	Debug - Finished registering callbacks.
            Mar-07 21:46:40	 	SDJ-Health	Debug - Registering Enums.HSEvent.LOG
            Mar-07 21:46:40	 	SDJ-Health	Debug - Registering Enums.HSEvent.CONFIG_CHANGE
            Mar-07 21:46:40	 	SDJ-Health	Debug - CheckAndCreateDevices completed
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #989
            Mar-07 21:46:40	 	SDJ-Health	Child device #989 found in database.
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #988
            Mar-07 21:46:40	 	SDJ-Health	Child device #988 found in database.
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #987
            Mar-07 21:46:40	 	SDJ-Health	Child device #987 found in database.
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #986
            Mar-07 21:46:40	 	SDJ-Health	Child device #986 found in database.
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #985
            Mar-07 21:46:40	 	SDJ-Health	Child device #985 found in database.
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #1048
            Mar-07 21:46:40	 	SDJ-Health	Child device #1048 found in database.
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #1047
            Mar-07 21:46:40	 	SDJ-Health	Child device #1047 found in database.
            Mar-07 21:46:40	 	SDJ-Health	PEData read sucessfully from child device #1038
            Mar-07 21:46:40	 	SDJ-Health	Child device #1038 found in database.
            Mar-07 21:46:39	 	SDJ-Health	PEData read sucessfully from child device #1030
            Mar-07 21:46:39	 	SDJ-Health	Child device #1030 found in database.
            Mar-07 21:46:39	 	SDJ-Health	PEData read sucessfully from child device #1028
            Mar-07 21:46:39	 	SDJ-Health	Child device #1028 found in database.
            Mar-07 21:46:39	 	SDJ-Health	10 child devices found.
            Mar-07 21:46:39	 	SDJ-Health	Child device associations cleaned up.
            Mar-07 21:46:39	 	SDJ-Health	PEData read sucessfully from root device.
            Mar-07 21:46:39	 	SDJ-Health	Root device identified.
            Mar-07 21:46:38	 	SDJ-Health	Debug - CheckAndCreateDevices started
            Mar-07 21:46:38	 	SDJ-Health	Debug - BuildInterfaceList completed
            Mar-07 21:46:38	 	SDJ-Health	HomeID D7894C18 : Interface Name Z-Wave.me UZB
            Mar-07 21:46:37	 	SDJ-Health	Debug - BuildInterfaceList started
            Mar-07 21:46:27	 	SDJ-Health	Version 3.0.4.1 Initialized.

            Comment


            • Originally posted by Simonk View Post
              I left it running for 10 minutes, filtered log below.
              One of the monitoring devices appears to be referencing a device which doesn't have a battery child, or at least the plugin can't find the battery child. This maybe due to a mix up when the plugin has updated the devices to the latest version.
              Have a look through your monitoring devices and see if the devices they are monitoring make sense, i.e. they are battery powered devices and have a proper root and battery child. Also check the reported battery levels match the levels of the actual battery devices. If you find one that isn't correct then the easiest thing to do is delete the monitoring child. If it is a valid device it will create a new child when it next wakes up. If you can't find anything odd I would suggest deleting all the monitoring children, just leaving the root device, and let the plugin recreate them all. Do this whilst the plugin is running so it knows they are deleted and removes them from the information stored in the root device. If you delete them when the plugin isn't running it will recreate them from the stored information when you restart it, which you don't want it to do in this particular case.

              Steve

              Comment


              • Hi Steve, installed new version. First uninstalled the previous one. Now it is started creating the devices. It is nice you can also monitor using the last successful communication of the device or it child's but it would be nice if you could also display the last time stamp of last communication in the devices that are monitored using wake up message detection


                Sent from my iPhone using Tapatalk

                Comment


                • Originally posted by olof View Post
                  Hi Steve, installed new version. First uninstalled the previous one. Now it is started creating the devices. It is nice you can also monitor using the last successful communication of the device or it child's but it would be nice if you could also display the last time stamp of last communication in the devices that are monitored using wake up message detection
                  Ho olof, I'm glad it is working for you.

                  I'm trying to keep the footprint of the plug-in as small as possible so you would need to convince me that adding the additional information, which needs to be detected, displayed and stored, is of benefit. It wouldn't be difficult to do, but for me the time of the last detected wake-up call and the sleep period (together with the battery information) is all I want to know. That tells me the device is alive and working which is the purpose of the plug-in.

                  However, perhaps you have a purpose in mind, so I'd welcome your views.

                  Incidentally, for devices that the plug-in monitors by 'Activity Checking', it doesn't actually display the date/time of the last activity but it uses it as an indication that the device is alive. So if the 'Activity Monitoring' period is set to 6 hours it will check every 6 hours that there has been a device change within the last 6 hours. If there has then it considers the device is alive and displays the check date/time as the 'Last Good Check'.

                  Steve

                  Comment


                  • First off, I want to say that this is a great addition to our system. My goal is to have my wife be able to replace batteries if I am unable to. HS3 battery reporting is not quite there and this has been a negative for me.

                    I'm getting this error when I change the root device report:

                    SDJ-Health ERROR - Setting Root String: Argument 'Index' is not a valid value.

                    Any help on this would be appreciated.

                    Michael
                    Michael

                    HS3 Pro 3.0.0.470 | 849 devices | 349 events | OpenSprinkler | BLShutdown | EasyTrigger | NetCAM | Harmony Hub | Sonos | SDJ-Health | BLUPS | PHLocation | BLBackup | BLLock | Z-Wave 3.0.1.243 | weatherXML | Pushover 3P | Blue-Iris | AirPlaySpeak

                    Comment


                    • Originally posted by Rvtravlr View Post
                      First off, I want to say that this is a great addition to our system. My goal is to have my wife be able to replace batteries if I am unable to. HS3 battery reporting is not quite there and this has been a negative for me.

                      I'm getting this error when I change the root device report:

                      SDJ-Health ERROR - Setting Root String: Argument 'Index' is not a valid value.

                      Any help on this would be appreciated.

                      Michael
                      I can't reproduce this so I've updated the version in message #192 to 3.0.4.2. with some additional error checking to help pin down your issue. Please can you update and then post what errors it logs when you change the root device reports.

                      Thanks,
                      Steve

                      Comment


                      • Originally posted by SteveMSJ View Post
                        I can't reproduce this so I've updated the version in message #192 to 3.0.4.2. with some additional error checking to help pin down your issue. Please can you update and then post what errors it logs when you change the root device reports?
                        Just dropped it in and no errors when changing root reports. Nice job!

                        Michael
                        Michael

                        HS3 Pro 3.0.0.470 | 849 devices | 349 events | OpenSprinkler | BLShutdown | EasyTrigger | NetCAM | Harmony Hub | Sonos | SDJ-Health | BLUPS | PHLocation | BLBackup | BLLock | Z-Wave 3.0.1.243 | weatherXML | Pushover 3P | Blue-Iris | AirPlaySpeak

                        Comment


                        • Originally posted by Rvtravlr View Post
                          Just dropped it in and no errors when changing root reports. Nice job!



                          Michael


                          Good. Thanks for the feedback.

                          Steve

                          Comment


                          • Just loaded in 3.0.4.2 on Linux, it's detecting things as they come up in the log.

                            However I'm seeing a number of these errors since it was installed:
                            Mar-17 9:20:53 PM SDJ-Health Error - whilst checking latest status of all monitored devices! Number overflow.
                            Mar-17 9:20:35 PM
                            SDJ-Health Error - whilst checking latest status of all monitored devices! Number overflow.

                            Comment


                            • Originally posted by karib View Post
                              Just loaded in 3.0.4.2 on Linux, it's detecting things as they come up in the log.

                              However I'm seeing a number of these errors since it was installed:
                              Mar-17 9:20:53 PM SDJ-Health Error - whilst checking latest status of all monitored devices! Number overflow.
                              Mar-17 9:20:35 PM
                              SDJ-Health Error - whilst checking latest status of all monitored devices! Number overflow.
                              Please could you set LogLevel to 2 for a period and post what other messages SDJ-Health logs around the time of these error messages.

                              Thanks,
                              Steve

                              Comment


                              • Battery Discharge Rate

                                Hi Steve,

                                Been running the new version and overall it is running well. I do have an Everspring luminance sensor that dropped from 100% battery to 90% battery a few days after I installed the new version, so it flagged it as a high discharge rate (> 15.5%), but it's been sitting like that over the last week. Will it eventually clear? Everspring devices will only report battery values in steps of 10%, so I expect this will be a continual issue with these devices.

                                Thanks
                                Al
                                HS 3.0.0.548: 1990 Devices 1172 Events
                                Z-Wave 3.0.1.262: 126 Nodes on one Z-Net

                                Comment

                                Working...
                                X