More Lock Fun

I got this out of the blue this morning:

I can’t swear to it but I really thought I was on the stock Edge drivers (although I have Philh30’ installed). Checking after getting these messages and my locks have changed to Philh30s driver. I could be wrong on that though.

Phil’s original Z-Wave lock driver had the issue that the stock driver has where it periodically resets all the codes to 'Code XX". He provided a fix for that in the beta driver.

The odd thing here though is it appears nothing actually reset or changed. Codes and names are intact.

I also saw that behavior on both the stock and Phil’s original driver. Plus the beta has the unlockCodeName exposed which can be used as a trigger in Routines.

1 Like

Grrr, it just happened again.