I have a new issue that just popped up. I have five Monoprice 4-in-1 motion sensors that have been running fine for about two years. Recent two of them have not stopped showing motion, but still updating temp, battery, humidity, etc. I replaced the batteries, pushed the little pin hole to force update and nothing. So I unpaired the two devices and repaired them. Now they are showing up as * networkSecurityLevel: ZWAVE_S0_LEGACY. The other two are still running fine. I tried generic zwave device handler, monoprice device handler, zooz device hander. It still shows up as legacy. No clue why these two are having issues but the other two are not.
Well, I don’t know why it’s only showing up for some of the devices, but they are getting ready for their S2 certification so that’s why it would start showing up for older devices.
I noticed that new tag in the IDE a while back when trying (unsuccessfully - see all the zeros in the raw description) to add some existing Aeon Recessed Door Sensors after my v3 migration. As shown below, they no longer get included with their proper Raw Description and while one successfully completed S0 negotiation, the other failed it. My guess was that these are pre-S2 Zwave Plus devices so when they manage to include Securely (see first couple characters in Raw Description) but not using S2, they get the ZWAVE_S0_LEGACY tag, and when it fails… well they get the FAILED tag shown below.