Announcement

Collapse
No announcement yet.

Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423

Collapse
X
Collapse
 
  • Page of 98
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 3 8 9 10 11 12 13 14 15 16 17 18 23 63 98 template Next
    #181
    Have you had a crash? Let it run and report if it crashes. Memory will go up and down but to me its not an issue until it crashes. And if it has crashed, please post the crash dialog.

    Originally posted by Furious View Post
    Ah good, glad to see I'm being completely ignored - I'll just tell my server that the slowly creeping memory with .383 will go away on its own.
    💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

    Comment

      #182
      Originally posted by concordseer View Post
      Ran .379 for 15 days without a crash. Stopped it to update to .383 today to help with testing. Memory usage rising at its usual rate on startup, I'm going to leave this one running until memory usage settles or it crashes.

      I think these updates are aimed at Linux users. Has it now been established that Windows users memory issues have been resolved. Still puzzled as to why memory usage steadily rises from startup. Should memory be rising and falling as processes are swapped in and out of memory as and when they are utilised. Maybe this is a too simplistic way of looking at things.
      On Day 6 and HS3Pro .383 reporting in Tools-About Homeseer memory used 89mb and Htop reporting 236mb/927mb memory used. I'm expecting this to stabilise soon as it did in .379 but still rising at the moment.

      Comment

        #183
        Here at 7 days on V.383....on Homeseer 3 Lite (Zee2 HS3)

        Enabled HSTouch from day #1 next adding 2-3 clients. Currently using ~15 Homeseer touch clients with HS3Pro V.383 on Box #1.

        Currently running a couple of scripts.

        One script is reading a 1-Wire network (using Digitemp & OWFS), ZWave GPIO and Domoticz running on the ZNet POE RPi2 Wheezy device.

        Next adding an SDR radio to the RPi2 in the attic for reception of satellite images. (found a DIY) such that will be pushing a bit on the RPi2.

        Attic RPi2 is at 80Mb / 973Mb.

        [ATTACH]64439[/ATTACH]

        Added WeatherXML. Note that total memory is at 712Mb / 1.94Gb

        [ATTACH]64445[/ATTACH]
        Last edited by Pete; November 15, 2017, 07:18 AM.
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
        HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
        HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
        HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11
        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

        Comment

          #184
          I have been testing today again with the beta HS3, now version .383.
          Same result as I mentioned before, disabling HSTouch and after a while re-enabling HSTouch without restarting results in loads of repeating errors!

          Am I the only one seeing this? My log is overloading within seconds here?

          Code:
          nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:30	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:27	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
          Wim
          -- Wim

          Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

          1210 devices/features ---- 392 events ----- 40 scripts

          Comment

            #185
            Current up time is just under 4 days, again running with one processor locked up on .383. I'm going to let it run for awhile and see if another locks up.

            Current Date/Time: 11/15/2017 7:49:05 AM
            HomeSeer Version: HS3 Pro Edition 3.0.0.383
            Linux version: Linux HS3 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 3 Days 15 Hours 17 Minutes 31 Seconds
            Number of Devices: 353
            Number of Events: 90
            Available Threads: 800
            HSTouch Enabled: True
            Event Threads: 0
            Event Trigger Eval Queue: 0
            Event Trigger Priority Eval Queue: 0
            Device Exec Queue: 0
            HSTouch Event Queue: 0
            Email Send Queue: 0
            Anti Virus Installed:

            Enabled Plug-Ins
            2.0.35.0: BLLAN
            3.0.0.56: DSC Security
            3.0.1.9: Kodi
            1.2.0.0: Monoprice Amp
            3.0.6510.21140: Ultra1Wire3
            3.0.0.76: weatherXML
            3.0.0.36: X10
            0.0.0.6: YAMAHA-RECEIVER
            3.0.1.154: Z-Wave
            https://forums.homeseer.com/forum/de...plifier-plugin

            Comment

              #186
              @Rich,
              Had a v.383 HS3 Crash this morning at ~8:25 am 11/15 (last log entry) again there is no indication in the log to show errors that would lead up to a Crash, and was not doing anything with HS3 related. So based on last re-boot at 12:29 pm 11/14 I've been up 20 hours. Looking at my CPU 1-2% and HS3 Memory 144,160 (KB) nothing of interest. I've included my Windows Event Messages around and slightly past the Crash event for your consideration and reading of the "tea leaves" This obviously is a repeatable event. Please advise what other data point(s) I you need to diagnose.

              As @Pete suggested I will use the .NET refresh link to update my .Net files and disable the PHlocation plugin to remove any outside problems. Mike

              Current Date/Time: 11/15/2017 10:33:02 AM
              HomeSeer Version: HS3 Pro Edition 3.0.0.383
              Operating System: Microsoft Windows 10 Pro - Work Station
              System Uptime: 0 Days 1 Hour 44 Minutes 3 Seconds
              IP Address: 192.168.0.XXX
              Number of Devices: 547
              Number of Events: 207
              Available Threads: 400
              HSTouch Enabled: False
              Event Threads: 1
              Event Trigger Eval Queue: 0
              Event Trigger Priority Eval Queue: 0
              Device Exec Queue: 0
              HSTouch Event Queue: 0
              Email Send Queue: 0
              Anti Virus Installed: Windows Defender
              License: Registered
              License: XXXX
              User Name and Access Level: XXXX
              WAN IP Address: XXXX
              Web Server Port: XXXX
              Location: (Latitude) 42.10 (Longitude) 75.92 City/State-US-New York,Binghamton,75.92,42.10

              Enabled Plug-Ins
              2.0.48.0: BLBackup
              2.0.40.0: BLGData
              2.0.12.0: BLRoombaWifi
              3.1.1.24385: Blue-Iris
              3.0.0.40: EasyTrigger
              3.0.0.25: ImperiHome
              3.0.0.28: Nest
              3.0.1.109: PHLocation
              0.0.0.34: Pushover 3P
              3.0.0.1: Random
              3.1.0.22: Sonos
              3.0.6331.36036: UltraCID3
              3.0.6524.19944: UltraWeatherWU3
              3.0.1.156: Z-Wave
              Attached Files
              Computer: CUK Intel NUC7i7BNH
              Op System: Windows10 Pro - Work Station
              HS Version: HS4 Pro Edition 4.2.19.0

              Plug-Ins: AK Weather 4.0.5.25,APCUPSD 3.3.2.3,BLBackup 2.0.63.0,BLEditor 2.0.11.0,BLGData 3.0.55.0,BLOccupied 2.0.28.0,BLShutdown 1.0.6.0,Blue-Iris 3.1.3.33206,Device History 3.2.0.2,EasyTrigger 3.0.0.76,Harmony Hub 4.0.14.0,iRobot 5.22.41.1,JowiHue 4.0.8.7,Nest 3.0.0.34,NetCam Plugin 1.0.0.5,PHLocation2 3.0.0.64,Pushover 4.0.10.0,Random 3.0.0.2,Restart 1.0.0.7,Ring 1.0.0.9,SDJ-Health 3.1.1.3,Sonos 3.1.0.59,Sonos4 4.0.1.12,UltraCID3 3.0.6681.34300,UltraMon3 3.0.6554.33094,UltraNetCam3 3.0.6413.20219,Unifi 4.0.32.0,Zigbee 4.0.11.0,Z-Wave 4.0.3.0, and Jon00 scripts.

              Comment

                #187
                Yes, please try and refresh .NET. The logs don't show enough information to see what happened. But clearly it was a .NET dll that crash happened it which is different from other reported crashes.

                There is a reference to the location plugin but it looks like that crashed because HS went away, so I don't see that as the cause.

                Originally posted by MNB View Post
                @Rich,
                Had a v.383 HS3 Crash this morning at ~8:25 am 11/15 (last log entry) again there is no indication in the log to show errors that would lead up to a Crash, and was not doing anything with HS3 related. So based on last re-boot at 12:29 pm 11/14 I've been up 20 hours. Looking at my CPU 1-2% and HS3 Memory 144,160 (KB) nothing of interest. I've included my Windows Event Messages around and slightly past the Crash event for your consideration and reading of the "tea leaves" This obviously is a repeatable event. Please advise what other data point(s) I you need to diagnose.

                As @Pete suggested I will use the .NET refresh link to update my .Net files and disable the PHlocation plugin to remove any outside problems. Mike

                Current Date/Time: 11/15/2017 10:33:02 AM
                HomeSeer Version: HS3 Pro Edition 3.0.0.383
                Operating System: Microsoft Windows 10 Pro - Work Station
                System Uptime: 0 Days 1 Hour 44 Minutes 3 Seconds
                IP Address: 192.168.0.XXX
                Number of Devices: 547
                Number of Events: 207
                Available Threads: 400
                HSTouch Enabled: False
                Event Threads: 1
                Event Trigger Eval Queue: 0
                Event Trigger Priority Eval Queue: 0
                Device Exec Queue: 0
                HSTouch Event Queue: 0
                Email Send Queue: 0
                Anti Virus Installed: Windows Defender
                License: Registered
                License: XXXX
                User Name and Access Level: XXXX
                WAN IP Address: XXXX
                Web Server Port: XXXX
                Location: (Latitude) 42.10 (Longitude) 75.92 City/State-US-New York,Binghamton,75.92,42.10

                Enabled Plug-Ins
                2.0.48.0: BLBackup
                2.0.40.0: BLGData
                2.0.12.0: BLRoombaWifi
                3.1.1.24385: Blue-Iris
                3.0.0.40: EasyTrigger
                3.0.0.25: ImperiHome
                3.0.0.28: Nest
                3.0.1.109: PHLocation
                0.0.0.34: Pushover 3P
                3.0.0.1: Random
                3.1.0.22: Sonos
                3.0.6331.36036: UltraCID3
                3.0.6524.19944: UltraWeatherWU3
                3.0.1.156: Z-Wave
                💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                Comment

                  #188
                  Total cpu usage was up to 32% when I got home tonight. Looks like Kodi plugin is having some issue along with a worker thread.



                  Originally posted by happnatious1 View Post
                  Current up time is just under 4 days, again running with one processor locked up on .383. I'm going to let it run for awhile and see if another locks up.

                  Current Date/Time: 11/15/2017 7:49:05 AM
                  HomeSeer Version: HS3 Pro Edition 3.0.0.383
                  Linux version: Linux HS3 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 3 Days 15 Hours 17 Minutes 31 Seconds
                  Number of Devices: 353
                  Number of Events: 90
                  Available Threads: 800
                  HSTouch Enabled: True
                  Event Threads: 0
                  Event Trigger Eval Queue: 0
                  Event Trigger Priority Eval Queue: 0
                  Device Exec Queue: 0
                  HSTouch Event Queue: 0
                  Email Send Queue: 0
                  Anti Virus Installed:

                  Enabled Plug-Ins
                  2.0.35.0: BLLAN
                  3.0.0.56: DSC Security
                  3.0.1.9: Kodi
                  1.2.0.0: Monoprice Amp
                  3.0.6510.21140: Ultra1Wire3
                  3.0.0.76: weatherXML
                  3.0.0.36: X10
                  0.0.0.6: YAMAHA-RECEIVER
                  3.0.1.154: Z-Wave
                  Attached Files
                  https://forums.homeseer.com/forum/de...plifier-plugin

                  Comment

                    #189
                    Originally posted by rjh View Post
                    Have you had a crash? Let it run and report if it crashes. Memory will go up and down but to me its not an issue until it crashes. And if it has crashed, please post the crash dialog.
                    I had a crash this week (weekend). . .ZWave crashed first. . .restarted and looked okay for a bit, then crashed again. . .my cpu load seems to be 70% for HS3 and 55% for ZWave most often (running on fresh built Pi2).

                    Comment

                      #190
                      Originally posted by w.vuyk View Post
                      I have been testing today again with the beta HS3, now version .383.
                      Same result as I mentioned before, disabling HSTouch and after a while re-enabling HSTouch without restarting results in loads of repeating errors!

                      Am I the only one seeing this? My log is overloading within seconds here?

                      Code:
                      nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:31	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:30	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:29	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:28	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
nov-15 13:03:27	 	HSTouch Server Error	Exception in client listener: Elk socketadres (protocol/netwerkadres/poort) kan normaal slechts n keer worden gebruikt restarting...
                      Wim
                      Stood up this morning and HS3 was completely out of control, using 50% at least and more. Webpages would not load at all.
                      Discovered that the HSTouch plugin still exists on the system have removed that as I am sure this is causing the error I was seeing before. Why is not file not removed at a upgrade?

                      Now HS starts, complains about the HSTouch actions. Really?

                      HS climbed above 60% CPU immediatly after that.

                      Restored .357 here. Not a good version.

                      In my earlier post with testing .375 I explained my config, running windows 10

                      Thanks,

                      Wim
                      -- Wim

                      Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

                      1210 devices/features ---- 392 events ----- 40 scripts

                      Comment

                        #191
                        Discovered that the HSTouch plugin still exists on the system have removed that as I am sure this is causing the error I was seeing before. Why is not file not removed at a upgrade?

                        Saw issues relating to this in this thread a bit ago. It was easier to read the thread while it was happening. Not sure why the file wasn't removed during the upgrade.

                        Discussions related to HomeSeer Beta 3.0.0.332->356

                        Other issues posted relating to W10 relate to removing or tweaking current Bit Defender and or using Microsoft security essentials from the Windows 7 days.
                        - Pete

                        Auto mator
                        Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                        Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                        HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
                        HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                        HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11
                        X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                        Comment

                          #192
                          Pete,

                          Thanks, Feels to me this is only half a job done. I removed the hstouch excutable and updated the 10 to 15 events I had using hstouch actions. Solved... It would have been nice to have a simple proces in HS3 going through the events once and correct the actions, so the executable was not needed.

                          Tested with .357 with disabling and re-enabling the HSTouch and still loads of errors thrown here regarding the client listener.... I am sure I am not the only one seeing this?

                          What me really worries is the freezing after a day or two on HS3... Memory usage was still ok, but CPU wise all performance was gone... Startups of more then 10 minutes... no good

                          Thanks,

                          Wim
                          -- Wim

                          Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

                          1210 devices/features ---- 392 events ----- 40 scripts

                          Comment

                            #193
                            I am not seeing the HSTouch issues here with up to 15 Windows embedded clients.

                            It is low on the WAF as I have 3 touchscreens in the master bedroom and one in the master bathroom.

                            A glitch will generate noise from the wife for weeks.

                            Mostly what I see is that if everything is OK running a version of Homeseer 3 then why fix something that is not broken; such that most folks do not update or try beta versions. This is the same that was occurring during the Homeseer 2 days.

                            In the old days of enterprise company work with 160k employees had around 100-200 QA folks in a department whose only job was to test software. Homeseer is a smaller company and depends on us here on the forum to be testing stuff.



                            I do have external actions running on my touch clients via buttons but do not really use Homeseer HSTouch actions from the mothership.

                            Here utilize Jon00's Wintel remote control client that runs an agent on the Windows clients. I can do anything this way from the Homeseer mothership.

                            I have read on the long transition thread about folks redoing their HSTouch actions.
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                            Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                            HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram
                            HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                            HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11
                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                            Comment

                              #194
                              Originally posted by happnatious1 View Post
                              Total cpu usage was up to 32% when I got home tonight. Looks like Kodi plugin is having some issue along with a worker thread.
                              This morning it looks like I'm back down to 19% CPU (5% is normal) Kodi and the worker thread seamed to have worked things out by themselves.
                              https://forums.homeseer.com/forum/de...plifier-plugin

                              Comment

                                #195
                                The HSTouch plugin needs to stay if you have HSTouch events that were created when the plugin was active. There are references to the plugin that events were using so if you delete it, you will get event errors. The plugin is not used anymore and for sure, HS is not loading it so its harmless to leave it. If you are starting from scratch, you can safely delete it.

                                Originally posted by w.vuyk View Post
                                Stood up this morning and HS3 was completely out of control, using 50% at least and more. Webpages would not load at all.
                                Discovered that the HSTouch plugin still exists on the system have removed that as I am sure this is causing the error I was seeing before. Why is not file not removed at a upgrade?

                                Now HS starts, complains about the HSTouch actions. Really?

                                HS climbed above 60% CPU immediatly after that.

                                Restored .357 here. Not a good version.

                                In my earlier post with testing .375 I explained my config, running windows 10

                                Thanks,

                                Wim
                                💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                                Comment

                                Previous 1 3 8 9 10 11 12 13 14 15 16 17 18 23 63 98 template Next
                                Working...
                                X