Help with why device is in polling drop down.

[Rvtravlr]

As you can see, Kat Closet Door is in the drop down for polling.


It is the same device type as Michael Closet which is not in the polling drop down. Should I delete Kat Closet and let the PI rediscover it?

[SteveMSJ]

As you can see, Kat Closet Door is in the drop down for polling.

It is the same device type as Michael Closet which is not in the polling drop down. Should I delete Kat Closet and let the PI rediscover it?
]

Please can you post screenshots of the node details for the 2 devices from the 'PLUG-INS>Z-Wave>Node Information' page.
Also what are the actual devices.

Thanks,
Steve

[Rvtravlr]

They are both Aeon Labs recessed door sensors. https://aeotec.com/hidden-z-wave-door-sensor/

[SteveMSJ]

They are both Aeon Labs recessed door sensors. https://aeotec.com/hidden-z-wave-door-sensor/

Thanks but unfortunately the screenshot for Node 25 is missing the details at the top above the Command Classes. Could you redo that?
Also can you post screenshots of the Advanced Tab of the root/parent device for both devices. I'm trying to figure out why the plug-in is seeing them differently as neither should be appearing in the polling list..

There are circumstances where the plug-in will set the monitoring child to 'No Monitoring' but it shouldn't happen unless there is an issue so I'm trying to track down whether it is a bug in the plug-in that has caused this. Has the Kat Closet Door monitoring device been newly created or was it working previously.

Thanks,
Steve

[Rvtravlr]

[Rvtravlr]

[Rvtravlr]

As for if it was working before, I’m sorry, just don’t remember.

[SteveMSJ]

As for if it was working before, I’m sorry, just don’t remember.

There doesn't seem to be anything wrong with the devices themselves but there are two things going on here. One is that the monitoring child has somehow got set to a non-monitoring state and the second is that it is appearing in the list as available for polling even though it is a non-listening device. I haven't quite figured out the set of circumstances that has caused the first issue but I can see that, due a change I made at version 3.0.6.3. the second issue follows from the first.

Version : 3.0.6.3

• Work around added to retain monitoring of a device by polling even if its Supports_Status property gets changed from True to False by HS. This has been known to happen although it may have been a unique case.

The change at 3.0.6.3 was due to an error in HS that someone experienced. I think I will reverse the change because it was probably a one off error in HS.

As you originally supposed, if you delete the monitoring child for the Kat Closet Door sensor (ID 2234) the pi will rediscover it when it next wakes and create a new monitoring child.

Let me know if this cures the issue.

Steve

[Rvtravlr]

Thanks for taking the time to find the root cause. I deleted the device and will report back.

[Rvtravlr]

Update: Kat Closet is not in Device Management but is in Devices to be Polled just as described originally. No change.

[SteveMSJ]

Update: Kat Closet is not in Device Management but is in Devices to be Polled just as described originally. No change.

Strange. So you deleted the monitoring child for Kat Closet (node 25) and it hasn't yet created a new monitoring child?

Sorry your having these problems but can you try a couple of things to help me track down the issue.

Go to the Config page for SDJ-Health and set the LogLevel to 2. The go back to Device Management and then re-enter the SDJ-Health Config page and change back the LogLevel to your choice. Post your log for the period between the LogLevel changes.

Can you also check your log for any wake-up messages for Node 25 over the last 24 hours. If you have more than one Z-Wave interface you may have more than one Node 25 so it is the one that is on the interface that Kat Closet is on.

Thanks,
Steve