Announcement

Collapse
No announcement yet.

Fails to install?

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

  • #16
    Take a look at the debug file that we started with to help understand.

    Comment


    • #17
      Originally posted by Michael McSharry View Post
      Take a look at the debug file that we started with to help understand.
      Sorry - there's nothing here that looks like an error to me. I've deleted some of the lines about database updates for brevity, but I can post the entire thing if it will help. You can see where it says "Thread Started with broker 172.16.1.2, ..." but that's it.

      BTW, the "garbage" chronologically out of order extra lines at the end are real. It's not an artifact of something I did (or at least I don't think so!).
      5/19/2019 8:06:07 PM 18 | mcsMQTT Version 3.6.1.3 running at /usr/local/HomeSeer, HS is at /usr/local/HomeSeer
      5/19/2019 8:06:07 PM 36 | mcsMQTT InitHW ComputerName= ziti, IOEnabled=False
      5/19/2019 8:06:08 PM 475 | mcsMQTT Debug InitHW Database Ready
      5/19/2019 8:06:08 PM 494 | PopulateReceiveDict environment/temperature/outside_1, PluginDevice=1, Ref=137
      5/19/2019 8:06:08 PM 544 | PopulateReceiveDict environment/barometer, PluginDevice=1, Ref=138
      5/19/2019 8:06:08 PM 549 | PopulateReceiveDict environment/solar, PluginDevice=1, Ref=139
      5/19/2019 8:06:08 PM 554 | mcsMQTT Debug Receive Ready
      5/19/2019 8:06:08 PM 560 | mcsMQTT Debug Trigger Ready
      5/19/2019 8:06:08 PM 750 | HW Init Complete
      5/19/2019 8:06:08 PM 754 | Background Init Started
      5/19/2019 8:06:08 PM 755 | PopulateReceiveDict , PluginDevice=0, Ref=10
      5/19/2019 8:06:08 PM 756 | PopulateReceiveDict , PluginDevice=0, Ref=100
      5/19/2019 8:06:08 PM 756 | PopulateReceiveDict , PluginDevice=0, Ref=101
      ......
      5/19/2019 8:06:08 PM 791 | PopulateReceiveDict , PluginDevice=0, Ref=98
      5/19/2019 8:06:08 PM 792 | PopulateReceiveDict , PluginDevice=0, Ref=99
      5/19/2019 8:06:08 PM 793 | PopulateReceiveDict environment/temperature/outside_1, PluginDevice=1, Ref=137
      5/19/2019 8:06:08 PM 795 | PopulateReceiveDict environment/barometer, PluginDevice=1, Ref=138
      5/19/2019 8:06:08 PM 795 | PopulateReceiveDict environment/solar, PluginDevice=1, Ref=139
      5/19/2019 8:06:08 PM 795 | Background Init Received
      5/19/2019 8:06:09 PM 1426 | AddToMQTTSend1 10, PayloadTemplate=
      5/19/2019 8:06:09 PM 1429 | AddToMQTTSend1 100, PayloadTemplate=
      5/19/2019 8:06:09 PM 1433 | AddToMQTTSend1 101, PayloadTemplate=
      ......
      5/19/2019 8:06:09 PM 1733 | AddToMQTTSend1 98, PayloadTemplate=
      5/19/2019 8:06:09 PM 1735 | AddToMQTTSend1 99, PayloadTemplate=
      5/19/2019 8:06:09 PM 1737 | Background Send
      5/19/2019 8:06:10 PM 2432 | Background Init Filters - Background Complete
      5/19/2019 8:06:10 PM 2434 | Spawning MQTT Threads
      5/19/2019 8:06:10 PM 2448 | mcsMQTT Debug MQTT Ready
      5/19/2019 8:06:10 PM 2465 | MQTT Thread Started with broker 172.16.1.2, Shutdown=False, Disconnect=False, Client=False, Connected=False
      5/19/2019 8:06:10 PM 2471 | MQTT Thread Not Connected Yet
      5/19/2019 8:06:10 PM 2471 | Calling MQTTclient
      5/19/2019 8:06:10 PM 2474 | MQTT Thread Client Created
      5/19/2019 8:06:10 PM 2474 | MQTT Thread Client ID=HS3MQTT
      5/19/2019 8:06:10 PM 2475 | Calling MQTT Connect
      5/19/2019 8:06:20 PM 12818 | Page Timing Start
      5/19/2019 8:06:20 PM 12940 | Sort > 0
      5/19/2019 8:06:21 PM 13496 | Page Timing End
      5/19/2019 8:16:18 PM 610986 | HSEvent VALUE_CHANGE| 1024| F2| 100| 0| 58
      5/19/2019 8:17:03 PM 655380 | HSEvent VALUE_CHANGE| 1024| 0184F557-014-Q26| 255| 0| 111
      5/19/2019 8:17:03 PM 655689 | HSEvent VALUE_CHANGE| 1024| 0184F557-014-Q25| 8| 0| 110
      5/19/2019 8:17:08 PM 660453 | HSEvent VALUE_CHANGE| 1024| 0184F557-009-Q12| 22| 21| 36
      ......
      5/20/2019 6:04:19 AM 35891301 | HSEvent VALUE_CHANGE| 1024| S6| 1| 2| 7
      5/20/2019 6:04:19 AM 35891348 | HSEvent VALUE_CHANGE| 1024| F15| 100| 0| 18
      5/20/2019 6:04:54 AM 35926677 | HSEvent VALUE_CHANGE| 1024| S6| 2| 1| 7
      5/20/2019 6:04:54 AM 35926729 | HSEvent VALUE_CHANGE| 1024| F15| 0| 100| 18
      39 PM 615268 | MessageRefExists SELECT count(Ref) as extant FROM MQTT_MESSAGE WHERE (Ref=119)=15/19/2019 8:05:39 PM 615291 | UpdateRecord UPDATE MQTT_MESSAGE SET Source='',Topic='',Payload='',Template='',Pattern='',Replace ='',Match='0',LastDate='2019-05-14 08:44:09',Reject=0,Express=0,Accept=0,RetainFlag=0,PluginDev ice=0,Subscribe=0,Chart=0,History=0,Ref=119,ChangeType=1,Mis c=262160,QOS=0,StatusType=0 WHERE (Ref=119), result=1, Key=Ref
      5/19/2019 8:05:39 PM 615291 | MessageRefExists SELECT count(Ref) as extant FROM MQTT_MESSAGE WHERE (Ref=12)=1
      5/19/2019 8:05:39 PM 615317 | UpdateRecord UPDATE MQTT_MESSAGE SET Source='',Topic='',Payload='',Template='',Pattern='',Replace ='',Match='0',LastDate='2019-05-14 08:44:09',Reject=0,Express=0,Accept=0,RetainFlag=0,PluginDev ice=0,Subscribe=0,Chart=0,History=0,Ref=12,ChangeType=1,Misc =262160,QOS=0,StatusType=0 WHERE (Ref=12), result=1, Key=Ref
      5/19/2019 8:05:39 PM 615318 | MessageRefExists SELECT count(Ref) as extant FROM MQTT_MESSAGE WHERE (Ref=120)=1
      5/19/2019 8:05:39 PM 615343 | UpdateRecord UPDATE MQTT_MESSAGE SET Source='',Topic='',Payload='',Template='',Pattern='',Replace ='',Match='0'

      Comment


      • #18
        The applicable code sequence is below. Your debug shows it gets to this point, but does not return normally from creating the client object since "MQTT Thread Client Created" was not in your debug log. The exception trap looks to send the message to the HS log with "StartMQTTThread" as part of the message. Do you see anything in the HS log?

        The client is established with M2MMqtt.Net.dll which should be in HS subfolder /bin/mcsMQTT. The one I have has a file date of May 27, 2018. The pointer to get to this file is contained in HSPI_MCSMQTT.exe.config which will be in the same folder as HS. The pointer in the file will contain <probing privatePath="bin\mcsMQTT;bin/mcsMQTT;html\bin;html/bin;bin"/>
        Code:
                               hsWriteLog(PLUGIN_DEBUG, "Calling MQTTclient")
                                Try
                                    oMQTTClient = New MqttClient(gMQTTBroker,
                                    gMQTTBrokerPort,
                                    bSecure,
                                    caCert,
                                    clientCert,
                                    sslProtocol,
                                    New Security.RemoteCertificateValidationCallback(AddressOf ValidateBrokerCertificate))
                                    'New Security.LocalCertificateSelectionCallback(AddressOf SelectClientCertificate))
                                Catch ex As Exception
                                    hsWriteLog(PLUGIN_NAME, "StartMQTT Client attempt Failed to Broker" & gMQTTBroker & ex.Message & ":" & ex.InnerException.Message)
                                End Try
        
                                bSubscribed = False
                                If bFirstPass Then
                                    hsWriteLog(PLUGIN_DEBUG, "MQTT Thread Client Created")
                                End If
        :
        :
        
                Catch ex As Exception
                    hsWritelogEx(PLUGIN_NAME, "StartMQTTThread", ex.Message)
                End Try

        Comment


        • #19
          Originally posted by Michael McSharry View Post
          since "MQTT Thread Client Created" was not in your debug log
          Actually it is -

          5/19/2019 8:06:10 PM 2471 | Calling MQTTclient
          5/19/2019 8:06:10 PM 2474 | MQTT Thread Client Created
          5/19/2019 8:06:10 PM 2474 | MQTT Thread Client ID=HS3MQTT
          5/19/2019 8:06:10 PM 2475 | Calling MQTT Connect


          What happens after "Calling MQTT Connect" ?

          Comment


          • #20
            With success "MQTT Thread Client Created" is in the mcsMQTT debug log. If an error is thrown then a line with "StartMQTTThread" and the actual error message will be in the HS log. If neither of the two then it is stuck in the bowels of M2MQTT.Net.dll.

            Comment

            Working...
            X