Announcement

Collapse
No announcement yet.

Discussions related to HomeSeer Beta builds 3.0.0.369->3.0.0.423

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

    Is version .404 now the latest and if so what did it fix? Mike
    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


      404 is a test build not an official beta, hence I did not post it to the beta forum.

      404 was posted to see if it fixes a problem on Linux (Windows too maybe), where CPU gets stuck high. The only change is that it does run the compaction routines on the HS and Energy databases. There is suspicion that in some cases these routines are hanging. If you are seeing high CPU I would like you to try this build.

      Originally posted by MNB View Post
      Is version .404 now the latest and if so what did it fix? Mike
      💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

      Comment


        Originally posted by happnatious1 View Post
        That then begs the question of what possible use could it be for trouble shooting purposes?
        (other than 169.xxx.xxx.xxx means no Internet)
        An IPv4 address of 169.xxx.xxx.xxx does NOT imply "no internet". There is a very specific range of addresses (169.254.0.0/16) that are used for link-local addresses (and even then, the blocks 169.254.0.0/24 and 169.254.255.0/24 are reserved). "Link-Local" addresses are often assigned automatically by the OS if a 'normal' IP address isn't assigned, either statically or by DHCP. Link-local addresses are not routable and only valid within the network segment (the "link") they're connected to.

        Other than the 169.254.0.0/16 range, there are millions of valid, public IPv4 addresses that start with the '169' octet.

        -M.

        Comment


          Originally posted by mloebl View Post
          Internal IP addresses (in my opinion) if NAT'ing are pretty safe, as if a hacker breaches your firewall to make it useful, you've got bigger problems If it's a routable IPv4 or IPv6 address, I wouldn't post it publically either.
          To expand on this a little bit:

          There are three defined blocks of IP addresses that are available for anybody to use:

          10.0.0.0/8
          172.16.0.0/12
          192.168.0.0/16

          The reason anybody can assign addresses from these blocks is simply that, by long-agreement (courtesy of RFC-1918), these addresses are not routed over the Internet.

          Most of us are likely using a 192.168.x.0/24 network within our homes. By default, most residential routers, cable modem/routers, Wifi-routers (or any other combo device like that) are typically configured by the manufacturer to use 192.168.1.0/24 (or sometimes, 192.168.0.0/24). Described another way, each device on your network will have an address of 192.168.1.X (or 192.168.0.X) and will use a netmask of 255.255.255.0.

          Since these addresses are not routed over the Internet you can safely post them as part of a configuration file. As noted in the previous post, a bad guy would have to breach your firewall to be able to actually reach an IP address on your internal network.

          -M.

          Comment


            Got home this evening and my lights didn't come on when I opened the front door. Went to the log and say that the dsc plug in didn't see the door open. turned on my office light and the log didn't see the zwave light come on. Disabled and re enable the dsc plug in, it's not coming back. disabled the zwave plug in and re-enabled, it took a long time but came back. 10 minutes later voice announcements started to happen. Time to reboot.

            Jan-22 6:09:36 PM Error Initializing plug-in(2): DSC Security Instance::Object reference not set to an instance of an objectSTACK: Server stack trace: Exception rethrown at [0]: at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_remoting_wrapper (intptr,intptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI:InitIO (string) at Scheduler.clsHSPI.CheckInterfaces () [0x00098] in <8147654499854220932a398529059801>:0
            Jan-22 6:09:35 PM Plug-In Finished initializing plug-in DSC Security
            Jan-22 6:08:35 PM Info Plugin DSC Security has connected. IP:127.0.0.1:51004
            Jan-22 6:08:35 PM Error Initializing plug-in(2): DSC Security Instance::Object reference not set to an instance of an objectSTACK: Server stack trace: Exception rethrown at [0]: at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_remoting_wrapper (intptr,intptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI:InitIO (string) at Scheduler.clsHSPI.CheckInterfaces () [0x00098] in <8147654499854220932a398529059801>:0
            Jan-22 6:08:34 PM Plug-In Finished initializing plug-in DSC Security
            Jan-22 6:08:15 PM Device Control Device: Outside Outside Garage Door to Off (0)
            Jan-22 6:08:15 PM Device Control Device: Outside Outside Front Porch to Off (0)
            Jan-22 6:07:35 PM Info Plugin DSC Security has connected. IP:127.0.0.1:50954
            Jan-22 6:07:34 PM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object
            Jan-22 6:07:31 PM Info Plugin Z-Wave with instance: has disconnected
            Jan-22 6:07:31 PM Z-Wave Z-Net: Exiting Ethernet Communications Thread
            Jan-22 6:07:31 PM Z-Wave Finished: 79 Z-Wave Scenes, applying changes to the database...
            Jan-22 6:07:31 PM Z-Wave Finished processing Z-Wave Devices.
            Jan-22 6:07:30 PM Z-Wave Finished: 79 Z-Wave Devices, applying changes to database...
            Jan-22 6:07:30 PM Z-Wave Saving Z-Wave Devices Information...
            Jan-22 6:07:30 PM Z-Wave Finished processing Z-Wave Network(s).
            Jan-22 6:07:30 PM Z-Wave Finished: 1 Z-Wave Networks, applying changes to database...
            Jan-22 6:07:30 PM Z-Wave Saving Z-Wave Network Information...
            Jan-22 6:07:30 PM Plug-In Shutting down Plug-In: Z-Wave
            Jan-22 6:06:48 PM Error Initializing plug-in(2): DSC Security Instance::Object reference not set to an instance of an objectSTACK: Server stack trace: Exception rethrown at [0]: at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_remoting_wrapper (intptr,intptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI:InitIO (string) at Scheduler.clsHSPI.CheckInterfaces () [0x00098] in <8147654499854220932a398529059801>:0



            Current Date/Time: 1/22/2018 6:16:10 PM
            HomeSeer Version: HS3 Pro Edition 3.0.0.402
            Linux version: Linux HS3 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 3 Days 19 Hours 14 Minutes 7 Seconds
            Number of Devices: 368
            Number of Events: 90
            Available Threads: 799
            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.38.0: BLLAN
            3.0.0.56: DSC Security
            3.0.1.10: Kodi
            1.2.0.0: Monoprice Amp
            3.0.6510.21140: Ultra1Wire3
            3.0.0.79: weatherXML
            3.0.0.36: X10
            0.0.0.6: YAMAHA-RECEIVER
            3.0.1.173: Z-Wave
            https://forums.homeseer.com/forum/de...plifier-plugin

            Comment


              Still checking if build 404 has any affect on memory or crashes, so it would be ideal if you could run build 404.

              Originally posted by happnatious1 View Post
              Got home this evening and my lights didn't come on when I opened the front door. Went to the log and say that the dsc plug in didn't see the door open. turned on my office light and the log didn't see the zwave light come on. Disabled and re enable the dsc plug in, it's not coming back. disabled the zwave plug in and re-enabled, it took a long time but came back. 10 minutes later voice announcements started to happen. Time to reboot.

              Jan-22 6:09:36 PM Error Initializing plug-in(2): DSC Security Instance::Object reference not set to an instance of an objectSTACK: Server stack trace: Exception rethrown at [0]: at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_remoting_wrapper (intptr,intptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI:InitIO (string) at Scheduler.clsHSPI.CheckInterfaces () [0x00098] in <8147654499854220932a398529059801>:0
              Jan-22 6:09:35 PM Plug-In Finished initializing plug-in DSC Security
              Jan-22 6:08:35 PM Info Plugin DSC Security has connected. IP:127.0.0.1:51004
              Jan-22 6:08:35 PM Error Initializing plug-in(2): DSC Security Instance::Object reference not set to an instance of an objectSTACK: Server stack trace: Exception rethrown at [0]: at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_remoting_wrapper (intptr,intptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI:InitIO (string) at Scheduler.clsHSPI.CheckInterfaces () [0x00098] in <8147654499854220932a398529059801>:0
              Jan-22 6:08:34 PM Plug-In Finished initializing plug-in DSC Security
              Jan-22 6:08:15 PM Device Control Device: Outside Outside Garage Door to Off (0)
              Jan-22 6:08:15 PM Device Control Device: Outside Outside Front Porch to Off (0)
              Jan-22 6:07:35 PM Info Plugin DSC Security has connected. IP:127.0.0.1:50954
              Jan-22 6:07:34 PM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object
              Jan-22 6:07:31 PM Info Plugin Z-Wave with instance: has disconnected
              Jan-22 6:07:31 PM Z-Wave Z-Net: Exiting Ethernet Communications Thread
              Jan-22 6:07:31 PM Z-Wave Finished: 79 Z-Wave Scenes, applying changes to the database...
              Jan-22 6:07:31 PM Z-Wave Finished processing Z-Wave Devices.
              Jan-22 6:07:30 PM Z-Wave Finished: 79 Z-Wave Devices, applying changes to database...
              Jan-22 6:07:30 PM Z-Wave Saving Z-Wave Devices Information...
              Jan-22 6:07:30 PM Z-Wave Finished processing Z-Wave Network(s).
              Jan-22 6:07:30 PM Z-Wave Finished: 1 Z-Wave Networks, applying changes to database...
              Jan-22 6:07:30 PM Z-Wave Saving Z-Wave Network Information...
              Jan-22 6:07:30 PM Plug-In Shutting down Plug-In: Z-Wave
              Jan-22 6:06:48 PM Error Initializing plug-in(2): DSC Security Instance::Object reference not set to an instance of an objectSTACK: Server stack trace: Exception rethrown at [0]: at (wrapper managed-to-native) System.Object:__icall_wrapper_mono_remoting_wrapper (intptr,intptr) at (wrapper remoting-invoke) HomeSeerAPI.IPlugInAPI:InitIO (string) at Scheduler.clsHSPI.CheckInterfaces () [0x00098] in <8147654499854220932a398529059801>:0



              Current Date/Time: 1/22/2018 6:16:10 PM
              HomeSeer Version: HS3 Pro Edition 3.0.0.402
              Linux version: Linux HS3 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 3 Days 19 Hours 14 Minutes 7 Seconds
              Number of Devices: 368
              Number of Events: 90
              Available Threads: 799
              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.38.0: BLLAN
              3.0.0.56: DSC Security
              3.0.1.10: Kodi
              1.2.0.0: Monoprice Amp
              3.0.6510.21140: Ultra1Wire3
              3.0.0.79: weatherXML
              3.0.0.36: X10
              0.0.0.6: YAMAHA-RECEIVER
              3.0.1.173: Z-Wave
              💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

              Comment


                Originally posted by PCK View Post
                + 1 for upgrade to 404
                Also applied all system patches, note: Mono version 5.4.1.7 was installed

                Current Date/Time: 1/20/2018 7:32:47 PM
                HomeSeer Version: HS3 Pro Edition 3.0.0.404
                Linux version: Linux KFN05 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 0 Days 3 Hours 41 Minutes 14 Seconds
                IP Address: 192.168.2.126
                Number of Devices: 586
                Number of Events: 170
                Available Threads: 799
                HSTouch Enabled: False
                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
                3.0.0.19: Autelis
                2.0.70.0: BLStat
                3.0.0.43: EasyTrigger
                3.0.0.29: EnvisaLinkAdemco
                3.0.0.25: ImperiHome
                3.0.0.30: Nest
                0.0.0.35: Pushover 3P
                3.0.5.6: SDJ-Health
                3.0.6551.15210: UltraECM3
                3.0.6542.35207: UltraWeatherWU3
                3.0.1.173: Z-Wave


                PCK (Pete)

                404 has crashed on me, uptime 2 days 33 minutes

                Comment


                  I am working with Pete on his crash, but has anyone else had a crash on build 404? My test system that was crashing on previous builds is still running. But too soon to say that its better. Memory is stable.

                  One thing I failed to mention. On Linux, if an exception is thrown that is not handled, the exception info is written to a file named "last_exception.txt". So please check if you have this file after a crash.
                  💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                  Comment


                    Originally posted by rjh View Post
                    I am working with Pete on his crash, but has anyone else had a crash on build 404? My test system that was crashing on previous builds is still running. But too soon to say that its better. Memory is stable.

                    One thing I failed to mention. On Linux, if an exception is thrown that is not handled, the exception info is written to a file named "last_exception.txt". So please check if you have this file after a crash.

                    Comment


                      I assume you are using the Linux tar file build. Can you go back to build 368 and see if that crashes the same way? Or did you see a crash with that build also?

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

                      Comment


                        Originally posted by rjh View Post
                        I assume you are using the Linux tar file build. Can you go back to build 368 and see if that crashes the same way? Or did you see a crash with that build also?
                        I was seeing crashes in 368 also. I can go back as far as you want if needed, and yes I am using the Linux tar file build.

                        Comment


                          Try build 318, that was before hstouch was added to the app.

                          Originally posted by PCK View Post
                          I was seeing crashes in 368 also. I can go back as far as you want if needed, and yes I am using the Linux tar file build.
                          💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                          Comment


                            Originally posted by rjh View Post
                            Try build 318, that was before hstouch was added to the app.
                            I've pulled down 318 and I will load it tonight, I'll update when I'm up and running.

                            Comment


                              Moving to Build .404 as requested. Here are the final results for my only session I ran on .402 which had no issue for me:

                              Current Date/Time: 1/22/2018 7:05:58 PM
                              HomeSeer Version: HS3 Pro Edition 3.0.0.402
                              Operating System: Microsoft Windows 10 Pro - Work Station
                              System Uptime: 4 Days 22 Hours 19 Minutes 40 Seconds
                              IP Address: 192.168.5.3
                              Number of Devices: 914
                              Number of Events: 581
                              Available Threads: 400
                              HSTouch Enabled: False
                              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: Windows Defender

                              Enabled Plug-Ins
                              0.0.0.21: drhsIpPlugIn
                              3.0.0.43: EasyTrigger
                              3.0.0.25: ImperiHome
                              3.0.2.4: OMNI
                              0.0.0.35: Pushover 3P
                              3.0.5.6: SDJ-Health
                              3.0.6554.33094: UltraMon3
                              3.0.0.41: UPBSpud
                              3.0.1.184: Z-Wave

                              -Travis

                              Comment


                                Went to 404 yesterday... saw memory hovering around 190MB.

                                Just checked... cpu still low, but memory at 360MB.

                                Biggest offender seems to be BLBackup.

                                Current Date/Time:
                                1/22/2018 7:11:32 PM Pacific Standard Time
                                HomeSeer Version:
                                HS3 Standard Edition 3.0.0.402 (Windows)
                                HomeSeer:
                                Is Registered
                                Operating System:
                                Microsoft Windows 10 Pro - Work Station
                                OS Version:
                                10.0.16299 Service Pack: 0.0
                                System Uptime:
                                1 Day 9 Hours 23 Minutes 46 Seconds
                                User Name and Access Level:
                                tomgru (Admin)
                                LAN IP Address:
                                192.168.1.154 (GruverServer2)
                                Client IP Address:
                                192.168.1.204 (TomSurface3)
                                External IP Address:
                                73.157.62.55 (c-73-157-62-55.hsd1.wa.comcast.net)
                                Network Adapter:
                                Adapter -> Hyper-V Virtual Ethernet Adapter #3 IP: 192.168.1.154/24 MAC: FC:AA:14:CC:BE:07
                                Network Adapter:
                                HomeSeer Adapter -> Loopback Address (localhost) IP: 127.0.0.1
                                Web Server Port:
                                80
                                Number of Devices:
                                420
                                Number of Events:
                                108
                                Event Last Ran:
                                Garage Events : 5 Check if small garage door is open, Ran at 1/22/2018 7:04:13 PM
                                Number of unique event scripts used:
                                0
                                Plug-Ins Enabled:
                                Vista Alarm:,Harmony Hub:,BLShutdown:,SDJ-Health:,BLUPS:,BLBackup:,ImperiHome:,Sonos:,Z-Wave:,Global Cache Pro:,Ecobee:
                                Processor Type and Speed:
                                Intel64 Family 6 Model 60 Stepping 3 at 3.07 GHz
                                Modules/Threads:
                                157 Modules, 116 Threads
                                Available Threads:
                                400
                                System Processes/Load:
                                191 Processes, 7% Load
                                Free / Total Physical Memory:
                                7.14 GBytes / 15.86 GBytes (45% free)
                                Free / Total Virtual Memory:
                                8.81 GBytes / 18.24 GBytes (48% free)
                                HomeSeer Memory Used:
                                118 Mbytes
                                Plug-In Memory Used:
                                11 EXE Plug-Ins using 530 Mbytes
                                Attached Files

                                Comment

                                Working...
                                X