Announcement

Collapse
No announcement yet.

Not seeing devices properly all of a sudden?

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

    Not seeing devices properly all of a sudden?

    Hi,
    so I added two z-wave motion detectors 5 days apart and the first one was integrated to the PI no problem, but the second is not,
    They both show up here, in monitoring, which I am not using.
    Click image for larger version  Name:	Capture-sdjhealth1.PNG Views:	0 Size:	48.0 KB ID:	1468136

    But only the first one from 5 days ago shows up under devices being polled
    Click image for larger version  Name:	Capture-sdjhealth2.PNG Views:	0 Size:	39.1 KB ID:	1468137

    Now the weird thing is after a few hours I did get a device listing for the new one...but it doesn't look quite right... it says "unknown type" even though it did say it measured the battery.
    Meanwhile the first one from 5 days ago keeps missing polls.

    Click image for larger version  Name:	Capture-sdjhealth3.PNG Views:	0 Size:	93.6 KB ID:	1468138

    any idea where it went sideways on me? The setup for both were pretty identical in process, they are the same ecolink motions,

    Thanks in advance.
    Last edited by RogerL; April 11, 2021, 05:32 AM. Reason: edit cuz i kant spel

    #2
    Originally posted by RogerL View Post
    Hi,
    so I added two z-wave motion detectors 5 days apart and the first one was integrated to the PI no problem, but the second is not,
    They both show up here, in monitoring, which I am not using.


    But only the first one from 5 days ago shows up under devices being polled

    Now the weird thing is after a few hours I did get a device listing for the new one...but it doesn't look quite right... it says "unknown type" even though it did say it measured the battery.
    Meanwhile the first one from 5 days ago keeps missing polls.



    any idea where it went sideways on me? The setup for both were pretty identical in process, they are the same ecolink motions,

    Thanks in advance.
    Hi RogerL,

    Something certainly seems odd.

    I would have thought these were non-listening devices so should be automatically monitored by wake-ups and shouldn't appear as available for polling.

    Please could you post a screenshot of the Z-Wave node information for the two devices? That is from the 'PLUG-INS>Z-Wave>Node Information' page.

    Steve

    Comment


      #3
      Originally posted by SteveMSJ View Post

      Hi RogerL,

      Something certainly seems odd.

      I would have thought these were non-listening devices so should be automatically monitored by wake-ups and shouldn't appear as available for polling.

      Please could you post a screenshot of the Z-Wave node information for the two devices? That is from the 'PLUG-INS>Z-Wave>Node Information' page.

      Steve
      here you go.... 5 days apart but they ended up being sequential.

      Click image for larger version

Name:	Capture-sdjhealth4.PNG
Views:	154
Size:	130.3 KB
ID:	1468141

      Comment


        #4
        Originally posted by RogerL View Post

        here you go.... 5 days apart but they ended up being sequential.
        Thanks for that.
        Sorry to keep asking for more information, but there is something wrong and I just want to track down what might have caused it.

        Can you post screenshots of the 'Advanced' Tab for the two battery child devices. Gate Motion Battery and Yard Motion Battery?

        Thanks,
        Steve

        Comment


          #5
          Originally posted by SteveMSJ View Post

          Thanks for that.
          Sorry to keep asking for more information, but there is something wrong and I just want to track down what might have caused it.

          Can you post screenshots of the 'Advanced' Tab for the two battery child devices. Gate Motion Battery and Yard Motion Battery?

          Thanks,
          Steve
          In addition to the above could you also do the following:
          • Go to the 'PLUG-INS>SDJ-Health>Config' page and set the LogLevel to 2
          • Go back to devices
          • Go to 'PLUG-INS'>SDJ-Health>Battery Devices'
          • Click on the 'Select Devices that Require Polling' list, then close it.
          • Go Back to devices
          • Go to the 'PLUG-INS>SDJ-Health>Config' page and set the LogLevel to 0 or 1.
          • Post a snapshot of the log between the changes in log level which should look something like this:
          Click image for larger version  Name:	Log.png Views:	0 Size:	306.0 KB ID:	1468171

          I'll also need to know the device RefID's of the Gate Motion Battery and Yard Motion Battery devices.

          Thanks,

          Steve

          Comment


            #6
            Originally posted by SteveMSJ View Post

            Thanks for that.
            Sorry to keep asking for more information, but there is something wrong and I just want to track down what might have caused it.

            Can you post screenshots of the 'Advanced' Tab for the two battery child devices. Gate Motion Battery and Yard Motion Battery?

            Thanks,
            Steve
            Sure, anything you need I can do it.

            Here is the Yard Motion
            Click image for larger version

Name:	Capture-sdjhealth5.PNG
Views:	140
Size:	39.6 KB
ID:	1468236
            Here is the gate motion
            Click image for larger version

Name:	Capture-sdjhealth6.PNG
Views:	138
Size:	39.8 KB
ID:	1468237

            Comment


              #7
              Originally posted by SteveMSJ View Post

              In addition to the above could you also do the following:
              • Go to the 'PLUG-INS>SDJ-Health>Config' page and set the LogLevel to 2
              • Go back to devices
              • Go to 'PLUG-INS'>SDJ-Health>Battery Devices'
              • Click on the 'Select Devices that Require Polling' list, then close it.
              • Go Back to devices
              • Go to the 'PLUG-INS>SDJ-Health>Config' page and set the LogLevel to 0 or 1.
              • Post a snapshot of the log between the changes in log level which should look something like this:
              Click image for larger version Name:	Log.png Views:	0 Size:	306.0 KB ID:	1468171

              I'll also need to know the device RefID's of the Gate Motion Battery and Yard Motion Battery devices.

              Thanks,

              Steve
              and here's the debug log
              Click image for larger version

Name:	Capture-sdjhealth7.PNG
Views:	154
Size:	69.9 KB
ID:	1468240

              Yard motion battery is device 915 and Gate motion battery is device 1023

              Comment


                #8
                Originally posted by RogerL View Post

                and here's the debug log

                Yard motion battery is device 915 and Gate motion battery is device 1023
                Thanks for the info which should help me troubleshoot what has caused the issue. I can’t immediately see how one of these devices has managed to get into the list available to be polled. I’ll investigate that further tomorrow.

                To cure the issue just delete the monitoring child’s for these two devices. Don’t select them from any lists, just leave things and the plug-in should detect them automatically the next time they wake up and create new monitoring child’s. This could take 12 hours or so depending on what the devices wake up interval is.

                Steve

                Comment


                  #9
                  Originally posted by SteveMSJ View Post

                  Thanks for the info which should help me troubleshoot what has caused the issue. I can’t immediately see how one of these devices has managed to get into the list available to be polled. I’ll investigate that further tomorrow.

                  To cure the issue just delete the monitoring child’s for these two devices. Don’t select them from any lists, just leave things and the plug-in should detect them automatically the next time they wake up and create new monitoring child’s. This could take 12 hours or so depending on what the devices wake up interval is.

                  Steve
                  so, delete these two devices from the PI right? not the actual devices themselves.

                  Click image for larger version

Name:	Capture-sdjhealth3.PNG
Views:	138
Size:	93.6 KB
ID:	1468249

                  Comment


                    #10
                    Originally posted by RogerL View Post

                    so, delete these two devices from the PI right? not the actual devices themselves.

                    Click image for larger version

Name:	Capture-sdjhealth3.PNG
Views:	138
Size:	93.6 KB
ID:	1468249
                    Yes, the monitoring child devices created by SDJ-Health. Don’t mess with the actual devices.

                    Steve

                    Comment


                      #11
                      Originally posted by RogerL View Post

                      and here's the debug log
                      Click image for larger version

Name:	Capture-sdjhealth7.PNG
Views:	154
Size:	69.9 KB
ID:	1468240

                      Yard motion battery is device 915 and Gate motion battery is device 1023
                      Hopefully by now if you have deleted the original monitoring children and the devices have woken-up, new monitoring children will have been created and everything should be hunky dory. Let me know if this is the case.

                      There is a bug somewhere that somehow allowed one of those devices to get itself into the list of devices available for polling when it shouldn't have because 'Supports Status' = False. Once in the list if you select it then it stays in the list for the future. This is because I have had a case in the past where HS has returned False for the 'Supports Status' call even when it should be true and somebodies lock dropped out of the list. The clue here is the debug entry at the top of your log extract which says '...#915 is False but was originally True...'.
                      The work around for somebodies lock dropping out, means that if it goes the other way a non-pollable device can slip into the list. As long as you don't select it then once it wakes-up it will be detected as a wake-up device and no longer appear in the list. But if you select it before it wakes-up it sticks in the list!

                      I seem to remember this happening to somebody before so you are not alone in it causing an issue. I might need to revisit the code and see if I can implement a double workround. However, the cure is always to delete the monitoring child and wait for the device to wake-up so a monitoring child is automatically created. Once the correct monitoring child exists the problem can no longer occur.

                      I hope this makes some sense.

                      Steve

                      Comment


                        #12
                        SteveMSJ

                        Deleted the monitoring children last night, yes.... no new ones have been detected/created yet.

                        Comment


                          #13
                          Originally posted by RogerL View Post
                          SteveMSJ

                          Deleted the monitoring children last night, yes.... no new ones have been detected/created yet.
                          Do you have any other non-listening devices that are being monitored ok?

                          Do you have 'Log poll and wake-up messages' selected?

                          Steve

                          Comment


                            #14
                            Originally posted by SteveMSJ View Post

                            Do you have any other non-listening devices that are being monitored ok?

                            Do you have 'Log poll and wake-up messages' selected?

                            Steve
                            As far as I can tell, yes... there are 8 other devices are being monitored.... although not all seem to be reporting/updating.
                            Click image for larger version

Name:	Capture-sdjhealth8.PNG
Views:	137
Size:	64.6 KB
ID:	1468370
                            Click image for larger version

Name:	Capture-sdjhealth9.PNG
Views:	127
Size:	79.2 KB
ID:	1468371
                            Click image for larger version

Name:	Capture-sdjhealth10.PNG
Views:	126
Size:	16.9 KB
ID:	1468369


                            and the selections are good, did not change those.

                            Click image for larger version

Name:	Capture-sdjhealth11.PNG
Views:	136
Size:	67.2 KB
ID:	1468372

                            They should have polled by now.... I know it's been over 12 hours.

                            Comment


                              #15
                              Originally posted by RogerL View Post

                              As far as I can tell, yes... there are 8 other devices are being monitored.... although not all seem to be reporting/updating.


                              They should have polled by now.... I know it's been over 12 hours.
                              The 'Log Poll and Wake-Up Messages' option, I was referring to, is in the Z-Wave plug-in. Make sure you have that checked.

                              Click image for larger version

Name:	Log Poll and Wake-up.png
Views:	185
Size:	33.9 KB
ID:	1468449

                              As detailed in the guide, that option is essential to being able to monitor wake-ups of non-listening Z-Wave devices as the Z-Wave pi doesn't provide any other indication that a device has woken up. I suspect you do have this checked as you have 4 No devices being monitored that have recorded a wake-up, although some time ago.

                              The most recent wake-up, shown on your screen shot, was on the 5th April so there is definitely something wrong! If you haven't inadvertently deselected the 'Log Poll and Wake-Up Messages' option, and all 4 devices aren't dead, then there would seem to be a problem with your Z-Wave.
                              There is a well reported, and acknowledged by HS though unresolved, bug in the Z-Wave pi that occurs quite often after including devices, usually but not exclusively, with Z-Tools. The symptoms are usually high CPU, slow down of the Z-Wave network, missed commands AND missing wake-up messages. If I see more than one battery device alert for missed wake-ups I know the bug has likely struck. The solution is just to stop and restart the Z-Wave plug-in or restart HS. Good practice is always to restart the Z-Wave plug-in after including any new devices, which prevents this bug occurring.

                              Have you restarted HS since you last included a device?

                              If this isn't the problem try searching your log for 'Wake-Up Notification', the messages look like this:

                              13/04/2021 13:05:48
                              Legacy-Plugin
                              Z-Wave
                              UZB-Dominion: Z-Wave Wake-Up Notification Received for Node 6

                              Let me know what you find.

                              Steve

                              Comment

                              Working...
                              X