Announcement

Collapse
No announcement yet.

Help with devices not reporting

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

    #16
    I have had to send one of my motion sensors back for replacement. I have excluded it in HS but it is still showing in SDJHealth. Can I just delete this or will the plug-in discover this?

    Comment


      #17
      Originally posted by pcgirl65 View Post
      I have had to send one of my motion sensors back for replacement. I have excluded it in HS but it is still showing in SDJHealth. Can I just delete this or will the plug-in discover this?
      The plug-in doesn't automatically delete a monitoring child if you remove the device it is monitoring, just in case it is a temporary error in HS3.

      You have two options really depending on how you replace your faulty device:

      1. Just delete the monitoring child. When you add your new device, at first wake-up it will be detected and a new monitoring child created.

      2. If you use the Replace Node procedure in HS3 you can replace a device with an identical device without breaking any events referencing the original device. If you do this you can keep the original monitoring child as the new device will have just replaced the old one.

      This doesn't really have anything to do with SDJ-Health. In HS3, if you are replacing a broken Z-Wave device with a replacement that is identical to the original it is always best to use the replacement method so that you don't have to reconstruct your events. It will keep the same children and reference IDs. It also means you can keep the original monitoring child in SDJ-Health but that isn't important.

      However, it sounds like you have already excluded it from HS so it is probably too late. If you exclude a Z-Wave device HS3 then deletes the root and child devices before you can blink. Ideally you don't exclude the broken device nor include the new device as such, you use the Replace Node method to include the new device which will include it whilst taking over the original root and child devices.

      I hope that helps.

      Steve

      Comment


        #18
        OK sounds good except I couldn’t use replace because I don’t know how long it is going to take to get this replacement. With slow shipping everywhere it might be awhile.

        Comment


          #19
          Originally posted by pcgirl65 View Post
          OK sounds good except I couldn’t use replace because I don’t know how long it is going to take to get this replacement. With slow shipping everywhere it might be awhile.
          It doesn’t actually matter how long it takes to get the replacement. You can remove the physical device and return it. As long as you don’t exclude it from your network the devices in HS3 will remain and you can use replace node when you receive the new device.

          Steve


          Comment


            #20
            Well that’s interesting! I didn’t know that thanks!

            Comment


              #21
              Originally posted by SteveMSJ View Post

              You select:
              > A Device's Value is..
              then select:
              > This device has its value set to...
              then select the SDJ-Health Battery Health Root device
              then in the 'is set to dropdown' select:
              > (Enter a custom value or value range)
              then you have two boxes where you can enter the start and finish of the range.

              Click image for larger version Name:	Event.JPG Views:	0 Size:	20.3 KB ID:	1381651

              By the way, to be pedantic, it's a Trigger not a Condition

              Steve
              Where did you determine the value range to put in the custom range?

              Comment


                #22
                Originally posted by pcgirl65 View Post

                Where did you determine the value range to put in the custom range?
                If you look on the Status Graphics tab of the SDJ-Health Root device you will see what the various values mean.

                Click image for larger version

Name:	Status Graphics.JPG
Views:	98
Size:	166.4 KB
ID:	1385477

                1000 and above are Control values which are used for the various control buttons but 0 to 100 are status values that the device will be set to by the pi. The Control Pairs will appear by name in the drop down selections for Actions, the Status Pairs will appear by name in the drop down selections for Triggers and Conditions.

                0,1,2 and 3 represent the various alerts, 50 indicates a new device has been detected and the pi is waiting for its next wake-up to set the wake-up period, 100 indicates there are no current alerts on any of the monitored devices. In an event Trigger or Condition you can select the various Statuses by name (e.g. Low Battery Alert) but you can also select a range to cover all or some of them by using the values. Hence the range of 0 to 3 in the example event is triggered on any of the Alerts. You could also use say less than 4, rather than the range, which would be the same thing.

                Using a value range is a shortcut to avoid a series of If and Or Ifs for each alert status, but you could do it that way if you wanted to use the names rather than the values.

                As an aside, you might also setup an event triggered by 'Healthy' to notify you when all alerts have been cleared, I do.

                Whether or not the various types of alert are Set depends on the pi Global Settings which can be overridden for specific devices if required. Note that High Discharge Alert is turned off by default as it is rarely useful.

                I hope that helps.

                Steve

                Comment


                  #23
                  Thanks for your explanation! Very helpful!

                  Comment

                  Working...
                  X