Hey @nayelyz,
I have some great news: I was continuing to work on this topic due to my need to participate in the solution of my problems, and I had some really good luck that I thought I would share. It is more of a work around than a fix, but it might help others with this issue.
Since Aeotec released their official edge driver channel, I started looking into all the documentation on their site. I found this troubleshooting guide for the Gen 5 Recessed sensor. At the bottom of the guide, they reference “Binary and Basic” reporting. This got me thinking about the cmd_class=“Basic” you pointed out in the logs. Here is what I did:
- I found the great edge driver created by @Mariano_Colmenarejo here and installed it to my hub.
a. This driver allows you to make configuration changes to Z-wave devices connected to the hub. - Changed this device’s driver to the “Z-Wave Device Config Mc” Driver
- Closed out the SmartThings app (Andriod) for the caching issue.
- Ro-opened the app to the device and set the parameters from the troubleshooting guide.
a. Parameter 121 [4 byte dec] = 272 - Hit the wakeup button on the Sensor.
- Waited a good 10 min for things to settle in. This may have been overkill.
- Changed the driver back to the stock Z-wave Sensor
- Closed out the SmartThings App
- Opened the app back up.
The device is now showing the correct status and updates/runs routines properly.
I do not know if this will help the everyday consumer for the big edge conversion but might be helpful for some.
Thank you again for all the support with this topic.