Announcement

Collapse
No announcement yet.

There are no locks configured in the plug-in.

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

    #16
    Also, download and install 3.0.2 in the updater
    Cheers,
    Bob
    Web site | Help Desk | Feature Requests | Message Board

    Comment


      #17
      I installed and restarted the new Z-Wave Plug-In .199, and stopped and restarted BLLock. Same issue as before. I also noticed this entry in the log while BLLock started:

      Feb-15 18:24:23 BLLock warning Lock model name cannot be determined by the plug-in so processing of the lock is disabled!
      Feb-15 18:24:23 BLLock warning Lock model name cannot be determined by the plug-in so processing of the lock is disabled!

      There were only two of these, but all five locks show up in the plug-in page. None show battery status or message, either.

      Comment


        #18
        Will do on 3.0.2.

        Comment


          #19
          OK load 3.0.2 and then do this:

          1. Delete debug log
          2. Shutdown plugin
          3. edit hspi_BLLock.ini and change debugLevel=true
          4. save INI file
          5. Restart plugin

          Once plugin has been started for a few minutes, turn off debug logging and then attach the BLLock-Detailed.log file zipped in the HS3 root folder
          Cheers,
          Bob
          Web site | Help Desk | Feature Requests | Message Board

          Comment


            #20
            Latest logs.
            Attached Files

            Comment


              #21
              I see 5 locks loaded and I see it getting the model for each lock

              I do see errors calling the JSON api calls in the ZWave plugin
              Is your HS3 web server running on port 80?

              Try 3.0.3 and see if it makes any difference
              Repeat the steps above to get a brand new debug log


              02/15/2018 06:38:55:373 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): port --> 80
              02/15/2018 06:38:55:374 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): url --> http://localhost:80/JSON
              02/15/2018 06:38:55:374 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): parm: request; value: pluginfunction
              02/15/2018 06:38:55:375 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): parm: plugin; value: Z-Wave
              02/15/2018 06:38:55:375 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): parm: function; value: ZwaveFunction
              02/15/2018 06:38:55:375 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): parm: p1; value: networks
              02/15/2018 06:38:55:375 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): parm: p2; value: null
              02/15/2018 06:38:55:375 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): parameters set
              02/15/2018 06:38:55:479 PM : v3.0.2.0 - Send_Homeseer_JSON_Request(): ERROR - Caught this web exception - Error: ConnectFailure (Connection refused)
              Cheers,
              Bob
              Web site | Help Desk | Feature Requests | Message Board

              Comment


                #22
                Server is on port 80. Could IP Hack Blocking be causing the issue? I have always had that enabled.

                I am loading 3.0.3 now. Will advise.

                Comment


                  #23
                  Possibly - I do not have that enabled
                  Cheers,
                  Bob
                  Web site | Help Desk | Feature Requests | Message Board

                  Comment


                    #24
                    I disabled IP Hack Blocking, installed 3.0.3, and am attaching the latest log. No joy yet, same issues.
                    Attached Files

                    Comment


                      #25
                      Yep same issue - something is blocking it
                      Do you have "Enable control using JSON" enabled on the network tab?
                      Cheers,
                      Bob
                      Web site | Help Desk | Feature Requests | Message Board

                      Comment


                        #26
                        Yes, that is checked.

                        Comment


                          #27
                          I wonder if it is a firewall issue
                          The calls are working fine here for me but something is definitely refusing it on your end
                          Cheers,
                          Bob
                          Web site | Help Desk | Feature Requests | Message Board

                          Comment


                            #28
                            I have had the firewall turned off since we started working on this - that was the first thing I thought of.

                            Comment


                              #29
                              Email me a screenshot of your network settings and I will compare to mine
                              blade9123 at gmail dot com
                              Cheers,
                              Bob
                              Web site | Help Desk | Feature Requests | Message Board

                              Comment


                                #30
                                E-Mail sent with screenshot.

                                Comment

                                Working...
                                X