Announcement

Collapse
No announcement yet.

Device reporting fine in SDJ-Health but not in actual device?

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

  • Device reporting fine in SDJ-Health but not in actual device?

    In my quest to have 100% battery monitoring (thanks Steve!) I have an odd situation. I have a water sensor that is not updating in the device yet SDJ-Health is showing it reported fine each day. What am I missing here? Thanks.

    Click image for larger version

Name:	Screen Shot 2019-10-12 at 8.05.16 AM.png
Views:	43
Size:	77.5 KB
ID:	1332422Click image for larger version

Name:	Screen Shot 2019-10-12 at 8.17.11 AM.png
Views:	34
Size:	120.7 KB
ID:	1332423
    Click image for larger version

Name:	Screen Shot 2019-10-12 at 8.18.51 AM.png
Views:	33
Size:	178.2 KB
ID:	1332425
    Attached Files

  • #2
    Originally posted by simonmason View Post
    In my quest to have 100% battery monitoring (thanks Steve!) I have an odd situation. I have a water sensor that is not updating in the device yet SDJ-Health is showing it reported fine each day. What am I missing here? Thanks.
    Simon,

    The device is a non-listening ZWave device and I can see that its wake-up period must be set to 12 hours. The device is waking up on schedule every 12 hours and SDJ-health detects this as shown by Last Wake Time and Last Sleep Period on the monitoring child. If the device died for any reason you would get an alert when it missed its regular wake-up. The fact that none of the actual device children in HS3 have updated just means that the device hasn't sent any information to HS3. You probably won't get anything until the battery level drops and it sends a new reading or of course if the water sensor itself trips.

    Some devices send battery updates even when the level hasn't changed but most don't to conserve power. No updates of the devices in HS3 doesn't mean the device isn't working. If it dies for any reason you will get an alert in SDJ-Health.

    Hope that helps, Steve

    Comment


    • #3
      Do your HomeSeer logs give any additional information about perhaps too many queued messages?

      Comment


      • #4
        Originally posted by RoChess View Post
        Do your HomeSeer logs give any additional information about perhaps too many queued messages?
        I don't think there is any problem with the device, HS3 or SDJ-Health, it is all working as it should. Some devices just sit there quietly, appearing to do nothing, but actually waking up at regular intervals to say "I'm here is there anything you want to send me". As there is nothing you want it to do it goes back to sleep and continues. If it had anything to report like a leak detected or a new battery reading you would get an update of the devices. This is the main reason for SDJ-Health as it will alert you if the device has actually died so you don't think it is just quietly biding its time.

        You can tell it is waking up because SDJ-Health is reporting the wake-up times and intervals in the monitoring device. If Simon looks back through his HS3 log he will see ZWave wake-up messages for the particular node at the times SDJ-Health is reporting them. I think he was just wondering why none of the HS3 Last Change times for the leak detector's devices were updating but that is normal behaviour for these devices.

        Steve

        Comment


        • #5
          There are times a device wakes up, but HS fails in sending/retrieving info from it, likely due to other z-wave traffic. The SDJ-Health plugin will see the wake-up and correctly mark it as still being alive, but none of the devices would update. The log entries would look like this:

          Code:
           
          Oct-12 8:51:25 AM Z-Wave Main ZNet: Z-Wave Wake-Up 'No More Info' Notification error sending to Node 110(Kitchen Misc Sensors Multisensor - Kitchen - Pantry - Node 110).
          Oct-12 8:51:21 AM Z-Wave Main ZNet: Wake-Up Notification Processing for Node 110 (Kitchen Misc Sensors Multisensor - Kitchen - Pantry - Node 110)
          Oct-12 8:51:21 AM Z-Wave Main ZNet: Z-Wave Wake-Up Notification Received for Node 110
          HS 3.0.0.548: 1976 Devices 1156 Events
          Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

          Comment


          • #6
            Originally posted by sparkman View Post
            There are times a device wakes up, but HS fails in sending/retrieving info from it, likely due to other z-wave traffic. The SDJ-Health plugin will see the wake-up and correctly mark it as still being alive, but none of the devices would update. The log entries would look like this:
            Thank you sparkman, that is what I was meant to say, but had no example to pull from as everything has been working fine for me since last restart a few weeks ago

            I used to get the occasional queued up warning on some battery devices, but I would just ignore those and fixed the bad event/script; they tend to be non-listening battery devices, versus those in FLiRS mode.

            Comment


            • #7
              Thanks everyone. I have now reached nirvana - all of my battery devices are now being monitored!

              Comment


              • #8
                Originally posted by sparkman View Post
                There are times a device wakes up, but HS fails in sending/retrieving info from it, likely due to other z-wave traffic. The SDJ-Health plugin will see the wake-up and correctly mark it as still being alive, but none of the devices would update. The log entries would look like this:

                Code:
                 
                Oct-12 8:51:25 AM Z-Wave Main ZNet: Z-Wave Wake-Up 'No More Info' Notification error sending to Node 110(Kitchen Misc Sensors Multisensor - Kitchen - Pantry - Node 110).
                Oct-12 8:51:21 AM Z-Wave Main ZNet: Wake-Up Notification Processing for Node 110 (Kitchen Misc Sensors Multisensor - Kitchen - Pantry - Node 110)
                Oct-12 8:51:21 AM Z-Wave Main ZNet: Z-Wave Wake-Up Notification Received for Node 110
                Valid point, well made.
                Some devices, particularly StellaZ radiator valves, often go back to sleep before HS3 finishes communicating with them. As they are old devices they require poling to retrieve anything, e.g. temperature, setpoints, operating modes and it is generally impossible to retrieve more than two of those parameters at one wake-up.

                However, in Simon's case the only information likely to be requested from the leak sensor by HS3 at a wake-up is the battery level. I don't know the actual model he has but most modern ZWave battery devices don't require polling for anything, they send the information when it is relevant. The wake-ups are mainly for sending queued parameter settings which you generally only do when you are first setting them up. However, they are a convenient way of knowing that they are still alive,

                Steve

                Comment

                Working...
                X