Announcement

Collapse
No announcement yet.

JSON Error missing interface

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

    JSON Error missing interface

    Hi all,

    Trying to use BLLock to add user PINs. Instead, in the log, I'm getting this:

    theResponse --> { "Response":"Error, missing interface" }

    Here's the full section of the detailed log -- and I do have a non-standard port for HS3:

    Code:
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): port --> 81
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): fullLanIp --> 192.168.0.84 (KCX-HS)
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): splitArray.Length --> 2
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): lanIpAddress --> 192.168.0.84
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): url --> http://192.168.0.84:81/JSON
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: request; value: pluginfunction
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: plugin; value: Z-Wave
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: function; value: AddUserCodePin
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: p1; value: 
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: p2; value: 5
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: p3; value: 1111
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: p4; value: Test user
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parm: p5; value: 
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): parameters set
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request(): theResponse --> 
    { "Response":"Error, missing interface" }
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Send_Homeseer_JSON_Request() finished
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Request_Add_User_Code_Pin(): theResponse --> { "Response":"Error, missing interface" }
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Request_Add_User_Code_Pin(): theJsonResponse.ToString --> 
    JSONResponseZWaveAddUserCodePin:
    --------------------------------
       Response: Error, missing interface
    
    03/17/2018 01:43:41:922 PM : v3.0.11.0 - Request_Add_User_Code_Pin() finished
    Does anyone know what "Error, missing interface" means? I do have JSON enabled and when I do test posts to /JSON, I do get responses.

    HS3 3.0.0.423
    ZWave: 3.0.1.206

    Thanks!

    #2
    The plugin did not get your zwave interface id
    Do this:

    1. Disable plugin
    2. Edit hspi_BLLock.ini and change debugLevel=true
    3. Save ini file
    4. Re-enable plugin

    Wait until your locks are found and then stop debug logging
    Attach the BLLock-Detailed.log zipped
    It is in the HS3 root folder
    Cheers,
    Bob
    Web site | Help Desk | Feature Requests | Message Board

    Comment


      #3
      Blade - just to close the loop on this (and apologize for not getting back with you to troubleshoot this issue; life has been crazy) - it works! I updated to the latest available build (3.0.13.0) and I was able to convert the locks to BLLock.

      A couple of issues I had:
      1. On one lock, the HS3 log showed that all users were converted. When I went to view the lock in BLLock, only 1 user entry was shown! I re-entered the users for that lock in BLLock. I seem to remember reading that others had this issue too, but it seems fixed now.

      2. When I add users to the lock, I don't see log entries in the HS3 log showing that they were programmed. This may be by design. I am remote, so I haven't been able to test yet to see if they were actually added.

      Thank you!

      hjk
      ---

      Comment


        #4
        Originally posted by hjk View Post
        2. When I add users to the lock, I don't see log entries in the HS3 log showing that they were programmed. This may be by design. I am remote, so I haven't been able to test yet to see if they were actually added.
        I am sure this can be added
        I will have a look
        Cheers,
        Bob
        Web site | Help Desk | Feature Requests | Message Board

        Comment


          #5
          Try out 3.0.14 in the beta section
          I added HS3 log messages for adding and removing lock codes
          Cheers,
          Bob
          Web site | Help Desk | Feature Requests | Message Board

          Comment


            #6
            Originally posted by Blade View Post
            Try out 3.0.14 in the beta section
            I added HS3 log messages for adding and removing lock codes
            Blade - at first, I still didn't see any log entries. Then I tried a different lock, and I saw the messages. THEN, I noticed the difference.

            I have 3 locks, but one of them is mis-identified:
            • Garage door lock - BE369
            • Back door lock - BE469NXCAM716
            • Front door lock - BE369 <- misidentified; this is a BE469NXCAM716


            When I go to Users on the Back Door BE469NXCAM716 (and, for that matter, when I go to Users on the Garage Door BE369), I have the option to add a user or delete a user.

            When I go to Users on the Front door lock, the BE469 which is mis-identified as a BE369, I have an "Edit" button which lets me disable or enable users. This doesn't seem to have any effect, nor any HS3 log entries, when I delete/add/disable/enable users.

            When I look at the HS3 log when I did the conversion yesterday, I do see that all 3 locks were converted.

            So... I don't know if something strange is marked on this Front Door Lock, or if it is because it is mis-identified, or what... but something is different about it.

            Comment


              #7
              It is like the lock with the user edit button has not been converted
              Can you attach your hspi_BLLock.xml file zipped
              Cheers,
              Bob
              Web site | Help Desk | Feature Requests | Message Board

              Comment


                #8
                Originally posted by Blade View Post
                It is like the lock with the user edit button has not been converted
                Can you attach your hspi_BLLock.xml file zipped
                Sure -- can I PM this to you, or maybe email it?

                Comment


                  #9
                  Go ahead and email it to me
                  Also run the script in this thread and send me the output log

                  https://forums.homeseer.com/showthread.php?t=161081
                  Cheers,
                  Bob
                  Web site | Help Desk | Feature Requests | Message Board

                  Comment


                    #10
                    Originally posted by Blade View Post
                    Go ahead and email it to me
                    Also run the script in this thread and send me the output log

                    https://forums.homeseer.com/showthread.php?t=161081
                    Blade -- I think I fixed it. There was weirdness in the INI, probably due to multiple versions of BLLock over the years. That lock was defined 3 or 4 times with codes (encrypted) listed and different ID numbers.

                    I stopped BLLock, manually edited the INI, and removed all references to the lock. When I re-started BLLock, it found the lock and got the existing codes.

                    Since I've had a few codes which dropped off the lock itself, I went ahead and deleted all door codes and added them back using BLLock. They added successfully and I just tested, and they worked.

                    Thanks for your help!

                    Comment


                      #11
                      Glad you got it sorted out
                      Cheers,
                      Bob
                      Web site | Help Desk | Feature Requests | Message Board

                      Comment

                      Working...
                      X