Hi Blade, got a couple of questions.
First, did the issue ever get resolved about user codes? Does the plug-in now send the actual codes to the locks? (There was a scripted way to do this with HS2, but I haven't tested/tried in HS3).
Second, on my Schlage deadbolt lock, I see this when debug logging is turned on:
Jun-19 10:17:32 AM BLLock warning Lock model name cannot be determined by the plug-in so processing of the lock is disabled!
This is one that you helped me with a while back so that it was recognized at all, but maybe the change didn't make it all the way through. It's a BE469NX-CAM. Shows up as "IR Security Safety Entry Control Node x" (IR =
Ingersoll Rand Security & Safety, maybe parent company or "real" manufacturer?)
Thanks for your help!
hjk
---
First, did the issue ever get resolved about user codes? Does the plug-in now send the actual codes to the locks? (There was a scripted way to do this with HS2, but I haven't tested/tried in HS3).
Second, on my Schlage deadbolt lock, I see this when debug logging is turned on:
Jun-19 10:17:32 AM BLLock warning Lock model name cannot be determined by the plug-in so processing of the lock is disabled!
This is one that you helped me with a while back so that it was recognized at all, but maybe the change didn't make it all the way through. It's a BE469NX-CAM. Shows up as "IR Security Safety Entry Control Node x" (IR =
Ingersoll Rand Security & Safety, maybe parent company or "real" manufacturer?)
Thanks for your help!
hjk
---
Comment