Announcement

Collapse
No announcement yet.

Lock model name not determined... disabled

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Lock model name not determined... disabled

    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
    ---


    #2
    The plugin cannot send user codes until HST allows it in the HS3 software itself. I have been asking for it but not sure it will happen.

    I will check your error. Can you do the following for me:

    1. Shutdown HS3
    2. Edit hspi_BLLock.ini and change debugLevel=true and save the INI file
    3. Restart HS3
    4. Once started then go and disable debug logging.

    Attach the BLLock-Detailed.log file zipped. It is in the HS3 root folder
    Cheers,
    Bob
    Web site | Help Desk | Feature Requests | Message Board

    Comment

    Working...
    X