Announcement

Collapse
No announcement yet.

Version 3.3.x.x

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

  • #31
    Something else is going on right now with current showing V.3.3.3.1 and updated V.3.3.40.

    Guessing that it is running V.3.3.40

    The plugin started to show disconnect errors and then brought the HS3 interface to a crawl. I've seen this happen with one prior version.

    But never seen the following occurring.

    Then while working on one touchscreen then a second one restarting HSTouch; HSTouch started to hang while starting never connecting to Homeseer 3.

    Looking at the HS3 logs the errors while the touchscreen was connected related to a media plugin. I do not have any media plugins configured or enabled.

    HS3 GUI froze for a bit then I was able to disable the mcsMQTT plugin.

    Restarted the two Homeseer touch screen applications on two touchscreens and the two started fine and fast as usual.

    Not sure how the mcsMQTT plugin relates to Homeseer Touch. I just know that while running the mcsMQTT plugin my Homeseer Touch screens do not connect to HS3.

    So for time bean have the mcsMQTT plugin disabled.

    Looking at the logs before disabling the plugin see this sort of stuff:

    May-12 12:55:12 PM Error Calling HSEvent in plugin mcsMQTT, Instance :Object reference not set to an instance of an object
    May-12 12:55:14 PM Warning Dropping event callbacks due to full queue (Type: 2) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
    May-12 12:55:14 PM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.


    Seen the above with one version but do not recall which one.

    May-12 12:55:59 PM HSTouch Server Opening connection from:192.168.244.205/1030
    May-12 12:56:00 PM HSTouch Server Client ICS-Jog-XPE-05 (192.168.244.205/1030) named ICS-Jog-XPE-05 has CONNECTED.
    May-12 12:56:00 PM HSTouch Server Connecting speaker client to HomeSeer IP 192.168.244.171
    May-12 12:56:00 PM ASR Speaker Client speech recognition stopped
    May-12 12:56:00 PM Speaker Speaker host added, Name: ICS-HS3Pro Instance: ICS-Jog-XPE-05 IP address: 192.168.244.205
    May-12 12:56:00 PM HSTouch Server This client was already connected, removing old connection.
    May-12 12:57:32 PM HSTouch ServerWarning HSTouch had an Error retrieving the capabilities for a media plugin with Error = Object reference not set to an instance of an object
    May-12 12:57:32 PM HSTouch Server Client ICS-Jog-XPE-05:ICS-Jog-XPE-05 (255.255.255.255/0) has raised LineDisconnected or was forced closed.
    May-12 12:57:32 PM HSTouch Server Client ICS-Jog-XPE-05 named ICS-Jog-XPE-05 has DISCONNECTED.
    May-12 12:57:47 PM HSTouch ServerWarning HSTouch had an Error retrieving the capabilities for a media plugin with Error = Object reference not set to an instance of an object
    May-12 12:58:04 PM HSTouch ServerWarning HSTouch had an Error retrieving the capabilities for a media plugin with Error = Object reference not set to an instance of an object
    May-12 12:58:18 PM HSTouch ServerWarning HSTouch had an Error retrieving the capabilities for a media plugin with Error = Object reference not set to an instance of an object

    I have not seen the above errors.

    All 15 Homeseer touch clients kept doing this. I had to kill the clients as they were frozen. Then the clients (2 that I tested) wouldn't start. Rather they froze on starting.
    Last edited by Pete; May 12th, 2018, 04:35 PM.
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
    Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

    Comment


    • #32
      mcsMQTT debug has HSevent info captured. Perhaps we can correlate the HS log and your experience to understand what is happening. It seems that HS thinks mcsMQTT is not responding to event callback and this may be due to the object error that is showing.

      The actual code in HSEvent is below. It does have a synclock for thread protection, but otherwise not much that would cause timeout. Your HS log message does not seem to come from mcsMQTT which means there are no exceptions being generated in mcsMQTT that are trapped and message sent to HS log.

      Code:
          Public Sub HSEvent(ByVal EventType As Enums.HSEvent, ByVal parms() As Object) Implements HomeSeerAPI.IPlugInAPI.HSEvent
              Try
                  'Console.Writeline("HSEvent")
                  Dim iRef As Integer
                  Dim bDo As Boolean = False
                  Dim bStatus As Boolean = False
                  If EventType = Enums.HSEvent.VALUE_CHANGE Then
                      iRef = CType(parms(4), Integer)
                      If MQTTSendDictionary.ContainsKey(iRef) Then
                          With MQTTSendDictionary(iRef)
                              If .Accept Then 'AndAlso .ValueChange Then
                                  bDo = True
                                  'bStatus = .StatusChange
                              End If
                          End With
                      End If
                  ElseIf EventType = Enums.HSEvent.STRING_CHANGE Then
                      iRef = CType(parms(3), Integer)
                      If MQTTSendDictionary.ContainsKey(iRef) Then
                          With MQTTSendDictionary(iRef)
                              If .Accept Then 'AndAlso .StringChange Then
                                  bDo = True
                              End If
                          End With
                      End If
                  End If
                  If gDebugLog Then
                      Dim s As String = "HSEvent Do= " & bDo.ToString & " " & EventType.ToString & " for Device " & iRef.ToString
                      hsWritelog(PLUGIN_DEBUG, s)
                  End If
      
                  If bDo Then
                      Dim sStatus As String = hs.DeviceVSP_GetStatus(iRef, CType(parms(2), Double), ePairStatusControl.Status)
                      Dim oKVP As KeyValuePair(Of Integer, String) = New KeyValuePair(Of Integer, String)(iRef, parms(2).ToString)
                      If gDebugLog Then
                          Dim s As String = "HSEvent Add " & EventType.ToString & " | " & iRef.ToString
                          hsWritelog(PLUGIN_DEBUG, s)
                      End If
                      SyncLock oHSEventCollection.SyncRoot
                          oHSEventCollection.Enqueue(oKVP)
                          oEventQueueWaiting.Set()
                      End SyncLock
                  End If
                  If bStatus Then
                      Dim sStatus As String = hs.DeviceVSP_GetStatus(iRef, CType(parms(2), Double), ePairStatusControl.Status)
                      Dim oKVP As KeyValuePair(Of Integer, String) = New KeyValuePair(Of Integer, String)(iRef, sStatus)
                      SyncLock oHSEventCollection.SyncRoot
                          oHSEventCollection.Enqueue(oKVP)
                          oEventQueueWaiting.Set()
                      End SyncLock
                  End If
      
              Catch ex As Exception
                  hsWritelogEx(PLUGIN_NAME, "HSEvent", ex.Message)
              End Try
          End Sub

      Comment


      • #33
        Thank you Michael. Enabled Debug under the general tab.

        Looking for post when this happened before and have not been able to find it.

        May-12 12:55:14 PM Warning Dropping event callbacks due to full queue (Type: 2) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
        May-12 12:55:14 PM Warning Plugin mcsMQTT is not responding but it is still running, not restarting yet.

        Over time it did cause Homeseer 3 to become unresponsive.
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
        Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

        Comment


        • #34
          I can see why HS could become non responsive if it is managing and waiting on a large queue of events that need a response.

          While my first reaction is that it is a return from HSEvent, it could also be more directly related to HSTouch where it is making some reference to a mcsMQTT device and not getting a response. All just guesses at this point.

          Comment


          • #35
            Thank you Michael.

            Thinking what happened last time HS3 became unresponsive then the touchscreens started to disconnect. I ended up sshing to the Homeseer box and just killing the mono process then shutting down Homeseer and rebooting the box and disabling the plugin to wait for an update.

            I am still tinkering with the plugin at this time.

            I have not made any changes to any of the touchscreens. Well no designer to HSTouch client updates in close to a year now.

            I am mostly using HS3 Pro / 2-3 plugins to test where I am using the HS3 Lite machine to run events (not running mcsMQTT on HS3 Lite right now; just HS3 Pro).

            That said looking at a number of around 10 events running on the HS3 Pro machine such that not much activity. There are no events or triggers based on any mcsMQTT variables at this time.

            It will most likely happen in the next 2-3 hours. Will save debug text file at that point.
            - Pete

            Auto mator
            Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
            Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

            Comment


            • #36
              Well it happened a bit sooner...

              May-12 7:46:37 PM Warning Dropping event callbacks due to full queue (Type: 2048) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates
              May-12 7:55:17 PM Error Posting back to plugin web page MQTT Setup: Object reference not set to an instance of an object-> at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_remoting_wrapper(intptr,i ntptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI.PostBackProc(string,string,string,int ) at Scheduler.proxyPage.postBackProc (Scheduler.StateObject& state, System.String Data) [0x00036] in <03c63de3f1dc4fe5b4c97ebd223f29dc>:0
              May-12 7:55:17 PM Error Posting back to plugin web page MQTT Setup: Object reference not set to an instance of an object-> at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_remoting_wrapper(intptr,i ntptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI.PostBackProc(string,string,string,int ) at Scheduler.proxyPage.postBackProc (Scheduler.StateObject& state, System.String Data) [0x00036] in <03c63de3f1dc4fe5b4c97ebd223f29dc>:0
              May-12 7:55:17 PM Error Calling HSEvent in plugin mcsMQTT, Instance :Object reference not set to an instance of an object
              May-12 7:55:19 PM Warning Dropping event callbacks due to full queue (Type: 2) (500 entries), system may be too busy, plugins and HSTouch may not receive all device updates

              Nothing odd in debug logs...

              5/12/2018 8:05:42 PM 5722910 | Update Accepted 2196 to 71.3 StatusType=2
              5/12/2018 8:05:42 PM 5722915 | Updating Device from 71.1 PayloadNumeric=True
              5/12/2018 8:05:42 PM 5722926 | ActoOnMessageFor Trigger Topic 26.061575000000/temperature,Payload=71.3
              5/12/2018 8:05:43 PM 5724029 | Update Accepted 2195 to 76.3 StatusType=2
              5/12/2018 8:05:43 PM 5724034 | Updating Device from 76.3 PayloadNumeric=True
              5/12/2018 8:05:43 PM 5724047 | ActoOnMessageFor Trigger Topic 10.F197E1010800/temperature,Payload=76.3
              5/12/2018 8:05:43 PM 5724747 | Update Accepted 2194 to 71.7 StatusType=2
              5/12/2018 8:05:43 PM 5724751 | Updating Device from 71.6 PayloadNumeric=True
              5/12/2018 8:05:43 PM 5724764 | ActoOnMessageFor Trigger Topic 10.A147E9000800/temperature,Payload=71.7
              5/12/2018 8:05:44 PM 5725069 | Update Accepted 2198 to 55 StatusType=2
              5/12/2018 8:05:44 PM 5725074 | Updating Device from 54.9 PayloadNumeric=True
              5/12/2018 8:05:44 PM 5725087 | ActoOnMessageFor Trigger Topic 26.F372E7000000/temperature,Payload=55
              5/12/2018 8:05:45 PM 5726206 | ActoOnMessageFor Trigger Topic 10.AE5613000800/temperature,Payload=69.7
              5/12/2018 8:05:46 PM 5727289 | Update Accepted 2193 to 53.3 StatusType=2
              5/12/2018 8:05:46 PM 5727295 | Updating Device from 53.3 PayloadNumeric=True
              5/12/2018 8:05:46 PM 5727307 | ActoOnMessageFor Trigger Topic 10.8A23CB010800/temperature,Payload=53.3

              Trying to disable plugin and GUI is unresponsive.

              Got to the manager page and see this for the plugin:

              CRITICAL: Failed to get InterfaceStatus from mcsMQTT: Object reference not set to an instance of an object

              Disabled the plugin.

              Debug logs look the same as above.

              Still very unresponsive. Cannot shut down HS3. Will SSH and kill the mono processes and reboot.
              Last edited by Pete; May 12th, 2018, 08:39 PM.
              - Pete

              Auto mator
              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

              Comment


              • #37
                Hi michael,

                when i deploy my flows on node-red, mcsmqtt disconect each time. I have mannually restart the plugin.


                edit: the plugin reconnect itself after 15-20 seconds
                Last edited by MattL0; May 12th, 2018, 08:50 PM.

                Comment


                • #38
                  Pete, three items of interest. The first is that the object managing the browser interface in mcsMQTT is not present. The second is that there were no callback to HSEvent by HS to mcsMQTT.

                  May-12 7:55:17 PM Error Posting back to plugin web page MQTT Setup: Object reference not set to an instance of an object-> at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_remoting_wrapper(intptr,i ntptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI.PostBackProc(string,string,string,int ) at Scheduler.proxyPage.postBackProc (Scheduler.StateObject& state, System.String Data) [0x00036] in <03c63de3f1dc4fe5b4c97ebd223f29dc>:0
                  May-12 7:55:17 PM Error Calling HSEvent in plugin mcsMQTT, Instance :Object reference not set to an instance of an object
                  If gDebugLog Then
                  Dim s As String = "HSEvent Do= " & bDo.ToString & " " & EventType.ToString & " for Device " & iRef.ToString
                  hsWritelog(PLUGIN_DEBUG, s)
                  End If
                  mcsMQTT is designed to support multiple browser pages independently and if the 2 second postback timer from the browser page, via HS, has not been received for 5 minutes then mcsMQTT destroys the object managing that browser page.

                  To minimize the variables during investigation assure that only one browser window is open and connected to mcsMQTT page. in 3.3.4.2 I restored some prior debug that existed in earlier versions in the postback routine that is called by HS. It should be called every 2 seconds or when a user input is make on the browser's mcsMQTT page.

                  The other is related to HSEvent. There were no HSEvent callbacks in the snippet of debug you posted. This means that HS never called mcsMQTT with an event change. The other item in the HS log indicates that when it was going to do the callback there was no mcsMQTT present. This looks more like a startup error that is preventing normal completion of mcsMQTT initialization. The start of the debug is of interest in this case.

                  Comment


                  • #39
                    when i deploy my flows on node-red, mcsmqtt disconect each time. I have mannually restart the plugin.
                    This seems to me more related to the broker than to mcsMQTT. If for whatever reason the connection to the broker is dropped then mcsMQTT will try to reconnect automatically. I think this is typical of IOT in general. mcsMQTT monitors the connection on 10 second intervals.

                    Comment


                    • #40
                      Thank you Michael.

                      One more thing. When I started it last time I let it accumulate some history but was never able to get any charting working.

                      Updated to V.3.3.4.2. Plugin manager now shows the plugin updated at V.3.3.4.2

                      Logs show updated and started. Skipped a few of the repetitive lines below when copying and pasting.

                      May-12 9:45:29 PM Plug-In Finished initializing plug-in mcsMQTT
                      May-12 9:45:29 PM Info Plugin mcsMQTT has connected. IP:127.0.0.1:33220
                      May-12 9:45:29 PM Starting Plug-In Initializing plugin mcsMQTT ...
                      May-12 9:45:29 PM mcsMQTT Version 3.3.4.2 Registered with Homeseer
                      May-12 9:45:29 PM Starting Plug-In Plugin mcsMQTT started successfully in 206 milliseconds

                      Went to look at history and see history. I saw history with previous version. Note that I tested the charting previously a few minutes after starting the plugin.

                      Configured a chart and saved it. This did not work with previous version.

                      Charting working fine now.

                      Debug currently shows...

                      5/12/2018 9:45:29 PM 0 | mcsMQTT Version 3.3.4.2 running at /HomeSeer, HS is at /HomeSeer
                      5/12/2018 9:45:29 PM 5 | mcsMQTT InitHW ComputerName= ICS-HS3Pro, IOEnabled=False
                      5/12/2018 9:45:29 PM 108 | mcsMQTT Debug InitHW Database Ready
                      5/12/2018 9:45:29 PM 111 | PopulateReceiveDict 26.061575000000/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 115 | PopulateReceiveDict 26.061575000000/humidity, PluginDevice=True
                      5/12/2018 9:45:29 PM 116 | PopulateReceiveDict 26.5CD3F1000000/humidity, PluginDevice=True
                      5/12/2018 9:45:29 PM 117 | PopulateReceiveDict 26.5CD3F1000000/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 118 | PopulateReceiveDict 10.F197E1010800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 118 | PopulateReceiveDict 10.A147E9000800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 119 | PopulateReceiveDict 26.F372E7000000/humidity, PluginDevice=True
                      5/12/2018 9:45:29 PM 121 | PopulateReceiveDict 26.F372E7000000/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 122 | PopulateReceiveDict 10.8A23CB010800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 122 | mcsMQTT Debug Receive Ready
                      5/12/2018 9:45:29 PM 123 | mcsMQTT Debug Trigger Ready
                      5/12/2018 9:45:29 PM 152 | Spawning MQTT Threads
                      5/12/2018 9:45:29 PM 152 | mcsMQTT Debug MQTT Ready
                      5/12/2018 9:45:29 PM 152 | HW Init Complete
                      5/12/2018 9:45:29 PM 153 | Background Init Started
                      5/12/2018 9:45:29 PM 153 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 156 | MQTT Thread Started with broker 192.168.244.175, Shutdown=False, Disconnect=False, Client=False, Connected=False
                      5/12/2018 9:45:29 PM 156 | MQTT Thread Not Connected Yet
                      5/12/2018 9:45:29 PM 156 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 157 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 157 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 157 | MQTT Thread Client Created
                      5/12/2018 9:45:29 PM 157 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 158 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 158 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 158 | MQTT Thread Client ID=b949aa13-baab-45fd-abf4-e82711c9b712
                      5/12/2018 9:45:29 PM 158 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 161 | PopulateReceiveDict 10.67C6697351FF8D/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 162 | PopulateReceiveDict 26.061575000000/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 162 | PopulateReceiveDict 26.061575000000/humidity, PluginDevice=True
                      5/12/2018 9:45:29 PM 162 | PopulateReceiveDict 10.67C6697351FF/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 163 | PopulateReceiveDict 10.A04713000800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 164 | PopulateReceiveDict 10.A04713000800/latesttemp, PluginDevice=True
                      5/12/2018 9:45:29 PM 164 | PopulateReceiveDict Temp800D9, PluginDevice=True
                      5/12/2018 9:45:29 PM 165 | PopulateReceiveDict 26.5CD3F1000000/humidity, PluginDevice=True
                      5/12/2018 9:45:29 PM 165 | PopulateReceiveDict 26.5CD3F1000000/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 165 | PopulateReceiveDict 10.AE5613000800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 165 | PopulateReceiveDict 10.4B5613000800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 166 | PopulateReceiveDict 10.F197E1010800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 166 | PopulateReceiveDict ICS-HS3Pro/mcsMQTT/LWT, PluginDevice=True
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict 10.A147E9000800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict 26.F372E7000000/humidity, PluginDevice=True
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict 26.F372E7000000/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict 10.8A23CB010800/temperature, PluginDevice=True
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict , PluginDevice=False
                      5/12/2018 9:45:29 PM 167 | PopulateReceiveDict ICS-Pine64/mcsMQTT/LWT, PluginDevice=True
                      5/12/2018 9:45:29 PM 167 | MQTT Thread Broker 192.168.244.175 Connect Response=0
                      5/12/2018 9:45:29 PM 167 | MQTT Broker Connection Accepted, Connected=True
                      5/12/2018 9:45:29 PM 168 | Background Init Received
                      5/12/2018 9:45:29 PM 169 | MQTT Thread Subscribing
                      5/12/2018 9:45:29 PM 170 | MQTT Subscription Start
                      5/12/2018 9:45:29 PM 170 | MQTT Subscription Topics being selected
                      5/12/2018 9:45:29 PM 170 | MQTT Subscription Topics selected
                      5/12/2018 9:45:29 PM 171 | MQTTSubscribe List / NoDiscovery=False to
                      5/12/2018 9:45:29 PM 171 | #
                      5/12/2018 9:45:29 PM 376 | PopulateSendDict 1778, PluginDevice=False
                      5/12/2018 9:45:29 PM 383 | PopulateSendDict 1779, PluginDevice=False
                      5/12/2018 9:45:29 PM 398 | ActoOnMessageFor Trigger Topic 10.67C6697351FF8D/temperature,Payload=70.0834
                      5/12/2018 9:45:29 PM 451 | Update Accepted 2196 to 71.2 StatusType=2
                      5/12/2018 9:45:29 PM 456 | Updating Device from 71.1 PayloadNumeric=True
                      5/12/2018 9:45:29 PM 468 | ActoOnMessageFor Trigger Topic 26.061575000000/temperature,Payload=71.2
                      5/12/2018 9:45:29 PM 477 | PopulateSendDict 1780, PluginDevice=False
                      5/12/2018 9:45:29 PM 483 | PopulateSendDict 1781, PluginDevice=False
                      5/12/2018 9:45:30 PM 519 | Update Accepted 2199 to 40.9 StatusType=2
                      5/12/2018 9:45:30 PM 519 | PopulateSendDict 1789, PluginDevice=False
                      5/12/2018 9:45:30 PM 523 | PopulateSendDict 1790, PluginDevice=False
                      5/12/2018 9:45:30 PM 524 | Updating Device from 41.2 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 525 | PopulateSendDict 1791, PluginDevice=False
                      5/12/2018 9:45:30 PM 531 | PopulateSendDict 1792, PluginDevice=False
                      5/12/2018 9:45:30 PM 540 | ActoOnMessageFor Trigger Topic 26.061575000000/humidity,Payload=40.9
                      5/12/2018 9:45:30 PM 597 | ActoOnMessageFor Trigger Topic 10.67C6697351FF/temperature,Payload=61.5
                      5/12/2018 9:45:30 PM 658 | ActoOnMessageFor Trigger Topic 10.A04713000800/temperature,Payload=69.8
                      5/12/2018 9:45:30 PM 803 | Background Send
                      5/12/2018 9:45:30 PM 808 | Background Init Filters - Background Complete
                      5/12/2018 9:45:30 PM 828 | Update Accepted 2200 to 41.5 StatusType=2
                      5/12/2018 9:45:30 PM 833 | Updating Device from 40.6 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 844 | ActoOnMessageFor Trigger Topic 26.5CD3F1000000/humidity,Payload=41.5
                      5/12/2018 9:45:30 PM 894 | Update Accepted 2197 to 75.6 StatusType=2
                      5/12/2018 9:45:30 PM 899 | Updating Device from 77.6 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 911 | ActoOnMessageFor Trigger Topic 26.5CD3F1000000/temperature,Payload=75.6
                      5/12/2018 9:45:30 PM 980 | ActoOnMessageFor Trigger Topic 10.AE5613000800/temperature,Payload=69.6
                      5/12/2018 9:45:30 PM 1038 | ActoOnMessageFor Trigger Topic 10.4B5613000800/temperature,Payload=69.6
                      5/12/2018 9:45:30 PM 1088 | Update Accepted 2195 to 74.1 StatusType=2
                      5/12/2018 9:45:30 PM 1095 | Updating Device from 76.4 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 1110 | ActoOnMessageFor Trigger Topic 10.F197E1010800/temperature,Payload=74.1
                      5/12/2018 9:45:30 PM 1119 | ActoOnMessageFor Trigger Topic ICS-HS3Pro/mcsMQTT/LWT,Payload=Offline
                      5/12/2018 9:45:30 PM 1119 | Update Accepted 2194 to 71.7 StatusType=2
                      5/12/2018 9:45:30 PM 1124 | Updating Device from 71.6 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 1136 | ActoOnMessageFor Trigger Topic 10.A147E9000800/temperature,Payload=71.7
                      5/12/2018 9:45:30 PM 1136 | Update Accepted 2201 to 63 StatusType=2
                      5/12/2018 9:45:30 PM 1141 | Updating Device from 57.1 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 1160 | ActoOnMessageFor Trigger Topic 26.F372E7000000/humidity,Payload=63
                      5/12/2018 9:45:30 PM 1160 | Update Accepted 2198 to 53.8 StatusType=2
                      5/12/2018 9:45:30 PM 1164 | Updating Device from 54.8 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 1177 | ActoOnMessageFor Trigger Topic 26.F372E7000000/temperature,Payload=53.8
                      5/12/2018 9:45:30 PM 1186 | Update Accepted 2193 to 52.3 StatusType=2
                      5/12/2018 9:45:30 PM 1191 | Updating Device from 53.3 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 1203 | ActoOnMessageFor Trigger Topic 10.8A23CB010800/temperature,Payload=52.3
                      5/12/2018 9:45:30 PM 1230 | Update Accepted 2193 to 52.3 StatusType=2
                      5/12/2018 9:45:30 PM 1235 | Updating Device from 52.3 PayloadNumeric=True
                      5/12/2018 9:45:30 PM 1248 | ActoOnMessageFor Trigger Topic 10.8A23CB010800/temperature,Payload=52.3
                      5/12/2018 9:45:31 PM 2350 | Update Accepted 2195 to 74.1 StatusType=2
                      5/12/2018 9:45:31 PM 2355 | Updating Device from 74.1 PayloadNumeric=True
                      5/12/2018 9:45:31 PM 2368 | ActoOnMessageFor Trigger Topic 10.F197E1010800/temperature,Payload=74.1
                      5/12/2018 9:45:31 PM 2439 | Update Accepted 2198 to 53.7 StatusType=2
                      5/12/2018 9:45:31 PM 2444 | Updating Device from 53.8 PayloadNumeric=True
                      5/12/2018 9:45:31 PM 2455 | ActoOnMessageFor Trigger Topic 26.F372E7000000/temperature,Payload=53.7
                      5/12/2018 9:45:33 PM 3543 | ActoOnMessageFor Trigger Topic 10.A04713000800/temperature,Payload=69.8
                      5/12/2018 9:45:33 PM 3621 | Update Accepted 2196 to 71.1 StatusType=2
                      5/12/2018 9:45:33 PM 3626 | Updating Device from 71.2 PayloadNumeric=True
                      5/12/2018 9:45:33 PM 3638 | ActoOnMessageFor Trigger Topic 26.061575000000/temperature,Payload=71.1
                      5/12/2018 9:45:33 PM 4260 | Update Accepted 2201 to 64.3 StatusType=2
                      5/12/2018 9:45:33 PM 4266 | Updating Device from 63 PayloadNumeric=True
                      5/12/2018 9:45:39 PM 9597 | ActoOnMessageFor Trigger Topic 26.F372E7000000/temperature,Payload=53.7
                      WebPageCount=0
                      Register Events 1, bValueCallbackRegistered=False, bStringCallbackRegistered=False

                      To minimize the variables during investigation assure that only one browser window is open and connected to mcsMQTT page.

                      OK
                      Last edited by Pete; May 12th, 2018, 10:03 PM.
                      - Pete

                      Auto mator
                      Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                      Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                      Comment


                      • #41
                        Thank for this info

                        Comment


                        • #42
                          Pete,
                          Your total initialization was about two seconds and things look pretty typical. The last thing you showed is where the HSEvent callback was registered, but subsequently HS never did a callback to report a device status change. It actually looks as if things hung at this point as other data normally shown in the debug also stopped. The actual statement is below

                          Code:
                          callback.RegisterEventCB(HomeSeerAPI.Enums.HSEvent.VALUE_CHANGE, PLUGIN_NAME, "")
                          What is odd is that you seem to be the only one having this issue. I don't know exactly what our next step should be. In the future it would be better to just attach the debug file rather than picking info from it as sometime data relationships have significance too.

                          If you get in a situation where history or charts do not show then try toggling one of the checkboxes on the tab that includes/excludes classes of topics from the selector. This will cause the selector to be rebuilt. It is likely the database still has the data, but the page was being constructed at a time when the select filter was not being properly constructed.

                          Comment


                          • #43
                            Thank you Michael.

                            I have left the start up of plugins in Homeseer default mode in the set up / tools lab / checkbox Load plug-ins in the background on startup.

                            I have had one or two other plugins which did not shut off or took a long time to shut down when shutting down the mothership.

                            Never pay attention these days.

                            IE: then to see the plugins run in a terminal window (very chatty kathy) I would run the plugins manually in a linux terminal window using the remote command (locally) mono plugin.exe in Linux. Way long time ago with first versions of Homeseer 3 in windows you could do this but I read today you cannot.

                            Testing the first Omni Plugin did the console thing to watch and did notice when shutting down the main mothership HS3 the plugin would error out and fill up the console as it was shutting down. Starting though worked fine.

                            Yes the debug file was Mb's large and I should just compress and attach it to the post.

                            Yeah don't know why this happened to me only as all I am doing here is using a Red Node OWFS broker with the mcsMQTT plugin.

                            I am not doing anything with the data on the Homeseer 3 side other than watching it and looking at the charts.

                            I have configured more Node Red OWFS sensors and have these disabled at this time. Each of the Node Red OWFS to MQTT sensors is set up to check OWFS readings every 10 seconds which is probably too much? Am I the only one here using the Node Red / OWFS broker with multiple 1-wire sensors?
                            Is one Node Red broker / OWFS / every 10 seconds per sensor X 16 or so sensors too much? Should I go to maybe a 120 or 360 seconds Mosquitto send per device?

                            None the less the issue did crop up on the repeated start ups of Homeseer and the plugin version 3.3.4.0 within a few hours of it running as it has happened similarly only once before with a different version of the plugin. Never really was paying attention to the HS3 logs or gui but caught it mostly with the 15 Homeseer touchscreens losing connectivity of the mothership.

                            Feel asleep early last night / morning and quit watching.

                            This morning version 3.3.4.2 of the plugin is running fine. HS3 response times are great and I see no errors in the Homeseer 3 logs. I have not looked at debug and was going to shut it off.

                            I will attach the debug logs here with this message zipped up.

                            Zipped the 13Mb plus debug file and it is less than 1Mb compressed and attached.

                            If you get in a situation where history or charts do not show then try toggling one of the checkboxes on the tab that includes/excludes classes of topics from the selector. This will cause the selector to be rebuilt. It is likely the database still has the data, but the page was being constructed at a time when the select filter was not being properly constructed.

                            Thank you and will do. Going baby steps here and mostly watching then trying the new functions of the mcsMQTT plugin one step at a time.

                            I sincerely appreciate what you are doing with Mosquitto / plugin.
                            Attached Files
                            Last edited by Pete; May 13th, 2018, 11:23 AM.
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                            Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                            Comment


                            • #44
                              V.3.3.4.2 at 15.15 C time is doing fine.

                              No errors in logs and Homeseer 3 GUI is fast, touchscreens are all connected and logs are error free.
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                              Comment


                              • #45
                                Day #2 of V.3.3.4.2 at 10.02 C time

                                Playing with 1-wire OWFS counter values from the Hobby Boards dual counter in the Lightning sensor.

                                This morning added second broker RPi / Node Red in attic with Hobby Boards Lightning dual counter. It is working. I configured the rate and accum device adds.

                                [ATTACH]68805[/ATTACH]

                                In the Homeseer 3 GUI I see the current value, accum and rate numbers increasing fine.

                                Curious what the rate is?

                                Is it a count per minute / per hour?

                                How do I set the rate?

                                Guessing that the accum number adding the current value number?

                                [ATTACH]68806[/ATTACH]

                                Is it possible to graph the rate?
                                - Pete

                                Auto mator
                                Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.4X
                                Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.4X

                                X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                                Comment

                                Working...
                                X