Announcement

Collapse
No announcement yet.

Jon00 Homeseer Log Monitor for Homeseer 3 and Homeseer 4

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

    #76
    Here my start log. Last version doesn't solve the problem.

    apr-12 17:44:145 Error Exception in GetLogDetail_Real: Formato della stringa di input non corretto.
    apr-12 17:44:14 Error Exception in GetLogDetail_Real: Formato della stringa di input non corretto.
    apr-12 17:44:14 Error Exception in GetLogDetail_Real: Formato della stringa di input non corretto.
    apr-12 17:44:14 Jon00_HSLogMon Version 1.0.4.2
    apr-12 17:44:14 Jon00_HSLogMon Connected to Homeseer
    apr-12 17:44:13 Web Server Web Server authorized local login successful from: ********** User: ******
    apr-12 17:43:41 mcsMQTT Event Action Publishing HS3/cmnd/richiesta_invio_stato_devices with Payload of ON
    apr-12 17:43:41 Event Deleting event after run: "Delayed Actions richiesta_stato_devices_microprocessore (Delayed Event)"
    apr-12 17:43:41 Event Event Trigger "SERVICE richiesta_stato_devices_microprocessore"
    apr-12 17:43:41 Event Event Trigger "Delayed Actions richiesta_stato_devices_microprocessore (Delayed Event)"
    apr-12 17:43:38 email Email successfully sent to *********
    apr-12 17:43:35 mcsMQTT MQTTClient is Connected to broker at ********
    apr-12 17:43:33 Speaker Speaker host added, Name: DOMOTICO-RKM Instance: Default IP address: 127.0.0.1
    apr-12 17:43:30 Info System connected to MyHS Service successfully with license ID ****.
    apr-12 17:43:30 Info System connected to MyHS Service, waiting for acknowledge...
    apr-12 17:43:29 Startup Start up complete.
    apr-12 17:43:29 Info No device issues found
    apr-12 17:43:29 Info Checking device parent child relationships...
    apr-12 17:43:29 Startup HSSentry is disabled in Setup, sentry will not be started.
    apr-12 17:43:29 Startup (Startup.vb script) No speaker clients detected, waiting up to 30 seconds for any to connect...
    apr-12 17:43:29 Startup (Startup.vb script) Scripting is OK and is now running Startup.vb
    apr-12 17:43:29 Startup Starting Event Scheduler...
    apr-12 17:43:27 Startup Running the startup script Startup.vb
    apr-12 17:43:26 Info Starting speaker client...
    apr-12 17:43:26 Startup Starting Find service...
    apr-12 17:43:26 Startup Updater services starting...
    apr-12 17:43:26 Speech Listening for remote speaker connections on port 10401
    apr-12 17:43:26 Startup Initializing Speaker Client Interface
    apr-12 17:43:26 Startup Start automation engine...
    apr-12 17:43:26 Startup HStouch server started, waiting for clients to connect.
    apr-12 17:43:26 HSTouch Server Server started on port 10200
    apr-12 17:43:26 Plug-In Finished initializing plug-in mcsMQTT
    apr-12 17:43:26 Starting Plug-In mcsMQTT loaded in 4941 milliseconds
    apr-12 17:43:26 Starting Plug-In Plugin mcsMQTT started successfully in 3666 milliseconds
    apr-12 17:43:22 mcsMQTT Version 5.2.1.5 Registered with Homeseer
    apr-12 17:43:22 Starting Plug-In Initializing plugin mcsMQTT ...
    apr-12 17:43:22 Info Plugin mcsMQTT has connected. IP:127.0.0.1:49753
    apr-12 17:43:17 RFXCOM 41 (RecRxChar) receiver #1 successfully initialized to Variable Length Mode
    apr-12 17:43:17 Plug-In Finished initializing plug-in RFXCOM
    apr-12 17:43:17 Starting Plug-In RFXCOM loaded in 1713 milliseconds
    apr-12 17:43:17 Starting Plug-In Plugin RFXCOM started successfully in 1028 milliseconds
    apr-12 17:43:17 RFXCOM 41 (InitVariables) No correct Telegram Token available
    apr-12 17:43:17 RFXCOM 41 (InitIO) RFXCOM version is:30.0.0.41
    apr-12 17:43:16 Starting Plug-In Initializing plugin RFXCOM ...
    apr-12 17:43:16 Info Plugin RFXCOM has connected. IP:127.0.0.1:49749
    apr-12 17:43:15 Startup Initializing Plug-Ins
    apr-12 17:43:15 Plug-In Found plug-in: RFXCOM, version: 30.0.0.41
    apr-12 17:43:13 Plug-In Found plug-in: mcsMQTT, version: 5.2.1.5
    apr-12 17:43:10 Startup Checking for available plug-ins
    apr-12 17:43:10 Info Remote plug-in API interface started on port 10400
    apr-12 17:43:07 Startup Creating ASP.NET application host...
    apr-12 17:43:06 Web Server UPNP Discovery started
    apr-12 17:43:06 Web Server Web Server started on port 81
    apr-12 17:43:06 Web Server Local IP address (subnet) is: 1*********(255.255.255.0)
    apr-12 17:43:06 Startup This version of HomeSeer is registered as a HS3STANDARD version.
    apr-12 17:43:06 Startup Creating Speaker Client Interface Object...
    apr-12 17:43:06 Startup HomeSeer version is: 3.0.0.548
    apr-12 17:43:06 Load Config Loading TIMERS...
    apr-12 17:43:05 Load Config Loading COUNTERS...
    apr-12 17:43:05 Load Config 150 total events loaded.
    apr-12 17:43:05 Load Config Loading Events...
    apr-12 17:43:05 Load Config Loading Event Groups...
    apr-12 17:43:05 Load Config 155 total devices loaded.
    apr-12 17:43:05 Database Loading Devices...
    apr-12 17:43:05 Database Opening (Mode=Read Only) up HomeSeer database C:\Program Files\HomeSeer HS3\Data\CRIS.hsd
    apr-12 17:43:05 Startup Loading configuration file ...
    apr-12 17:43:05 Startup Database SAVE process started.
    apr-12 17:43:04 Startup Local voice recognition class started.

    Comment


      #77
      There is nothing more I can do then. I put trapping code everywhere and if that is not triggering, it must be internal to Homeseer's function. All I can suggest you do is change your regional format to USA.
      Jon

      Comment


        #78
        Ok, Jon, I'll try with US regional setting.
        Thanks a lot for your support!

        Comment


          #79
          Jon,

          Is there any way to add a trigger based on the color of the log entry? I notice that color is one of the variables in the log structure: Public LogStyleColor As String.

          This would be very useful for some of the errors I get that are colored red but otherwise aren't easily searched for with regex or other means.

          Comment


            #80
            Yes, I expect that can be added. Colors would have to be matched on their hex code i.e. #FF0000 so you would need to know exactly what the log message originator was using to get a trigger.
            Jon

            Comment


              #81
              Both HS3 & HS4 versions have now been updated to support optional log color trigger criteria. Any problems, please let me know.
              Jon

              Comment


                #82
                Originally posted by prsmith777 View Post
                Jon,

                Is there any way to add a trigger based on the color of the log entry? I notice that color is one of the variables in the log structure: Public LogStyleColor As String.

                This would be very useful for some of the errors I get that are colored red but otherwise aren't easily searched for with regex or other means.
                Originally posted by jon00 View Post
                Both HS3 & HS4 versions have now been updated to support optional log color trigger criteria. Any problems, please let me know.

                prsmith777 Did you try this?
                Jon

                Comment


                  #83
                  I totally missed that update. I will let you know later today. Thanks for the quick response.

                  Comment


                    #84
                    Works like a charm.

                    Instead of enabling logging to get the color code in the log, I highlight the red log entry in Chrome browser and then right click and "inspect"... the font color is shown in hex code. So far all the reds in the log that I want to monitor seem to be #FF0000

                    Comment


                      #85
                      Looks like I spoke too soon. Tests messages work when applying "#FF0000" color, but actual red error messages don't trigger. I suspect the color hex codes aren't matching. I tried to save the colors into the log using Logging=2, but there is no HsLogMonitor folder in Data/Jon00. Does it matter which Trigger I put Logging=2?

                      Upon further testing, I can get everything to work properly using writelogex including monitoring of the correct color code, but when Homeseer writes to the log in a color other than black, it's not picking it up. I think maybe the color code is not exposed when Homeseer writes to the log. I haven't tried plugin errors yet

                      Comment


                        #86
                        Maybe incorrect documentation. Try HSlogging=1

                        Will only show on the trigger to which this setting is applied.
                        Jon

                        Comment


                          #87
                          Tried HSLogging=1 with no change. Im fairly certain the red color in the log from Homeseer is #FF0000 based on html analysis. Yet its not picking it up. My suspicion is that the color code is not exposed when Homeseer writes to the log directly. It is exposed when a test message is sent with the color code.

                          Comment


                            #88
                            Yes, that may well be the case. It only reports to the log when there is color information. I could only test using hs.writelogex and normal black text shows nothing.
                            Jon

                            Comment


                              #89
                              Originally posted by jon00 View Post
                              Yes, that may well be the case. It only reports to the log when there is color information. I could only test using hs.writelogex and normal black text shows nothing.
                              Welp thanks for the effort. Now I have to dig deeper into Regex to get what I want....

                              Comment


                                #90
                                I use LogMonitor to check the log for Z-Net errors. If one of my Z-Nets loses connectivity, then I run a script that power cycles them and they restart nicely. Works very well....

                                However, it seems I am often having to unplug the Z-Net for adding new devices, etc. and the LogMon triggers go off. I was wanting a way to easily disable the triggers. I tried disabling the script that is called by LogMon, but it runs regardless of it being enabled or disabled.

                                Is there a quick and easy way to disable/enable specific triggers?

                                Comment

                                Working...
                                X