Announcement

Collapse
No announcement yet.

Update to 3.0.6551.16372 and plug-in keeps crashing

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

  • Update to 3.0.6551.16372 and plug-in keeps crashing

    I upgraded to the latest plug-in version and now the plug-in keeps crashing or going non-responsive and nothing works. Seeing lots of error messages in the log:
    Dec-11 11:09:23 AM Warning No response/improper response from Elk M1 to command 'az00'

    Dec-11 11:09:22 AM Warning No response/improper response from Elk M1 to command 'az00'

    Dec-11 11:09:20 AM Warning No response/improper response from Elk M1 to command 'az00'

    Dec-11 11:09:18 AM Warning No response/improper response from Elk M1 to command 'tr0200'

    Dec-11 11:09:17 AM Warning No response/improper response from Elk M1 to command 'tr0200'

    Dec-11 11:09:15 AM Warning No response/improper response from Elk M1 to command 'tr0200'

    Dec-11 11:09:14 AM Warning No response/improper response from Elk M1 to command 'tr0100'

    Dec-11 11:09:12 AM Warning No response/improper response from Elk M1 to command 'tr0100'

    Dec-11 11:09:11 AM Warning No response/improper response from Elk M1 to command 'tr0100'

    Dec-11 11:09:09 AM Warning No response/improper response from Elk M1 to command 'lw00'

    Dec-11 11:09:08 AM Warning No response/improper response from Elk M1 to command 'lw00'

    Dec-11 11:09:06 AM Warning No response/improper response from Elk M1 to command 'lw00'

    Dec-11 11:09:06 AM Z-Wave Device: Z-Wave Laundry Room Sink Light Set to 0

    Dec-11 11:09:05 AM Device Control Device: Z-Wave Laundry Room Sink Light to Off (0) by/from: CAPI Control Handler

    Dec-11 11:09:05 AM Event Running script in background: C:/Program Files/HomeSeer HS3/scripts/LaundryRoom.cs("LightsOff","""")

    Dec-11 11:09:05 AM Event Event Trigger "Laundry Room Laundry Room Light Switch Off"

    Dec-11 11:09:05 AM Z-Wave Device: Z-Wave Laundry Room Lights Set to OFF

    Dec-11 11:08:06 AM Informational UltraM1G3 version 3.0.6551.16372 initialization complete.

    Dec-11 11:07:50 AM Info Plugin UltraM1G3 has connected. IP:127.0.0.1:56412

    Dec-11 11:07:47 AM Plug-In Finished initializing plug-in UltraM1G3

    Dec-11 11:07:38 AM Info Plugin UltraM1G3 with instance: has disconnected

    Dec-11 11:07:29 AM 1 Error System.Threading.ThreadAbortException: Thread was being aborted. at System.Text.RegularExpressions.Regex..ctor(String pattern, RegexOptions options, TimeSpan matchTimeout, Boolean useCache) at System.Text.RegularExpressions.Regex.Matches(String input, String pattern) at HSPI_ULTRAM1G3.hspi_plugin.ProcessReceived(String strDataRec)

    Dec-11 11:07:27 AM 1 Error System.Threading.ThreadAbortException

    Dec-11 11:07:27 AM Plug-In Shutting down Plug-In: UltraM1G3

  • #2
    Its the worst app on my phone. It crashes every single time, I need to close the app and reopen it every single time my phone turns off the display.

    Its extremely frustrating...

    Comment


    • #3
      I put plug-in version 3.0.5723.33972 back in place and haven't had an error in the log and everything is functioning correctly. There is something wrong with the new version. Hopefully UltraJones will get this corrected ASAP.

      Comment


      • #4
        Same but no crash

        While my version 16372 did not crash, I did have errors as described here by MPodlin. Did not really give it a chance to crash - I restored back to 3.0.6370.28796 almost immediately.

        Comment


        • #5
          The only problem I see is the inability to use the Updater to update any of my plug-ins. When I *just* updated, I had to restart HomeSeer. Please restart HomeSeer to confirm it resolves the issues you are experiencing.

          Regards,
          Ultrajones
          Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

          Comment


          • #6
            Originally posted by Ultrajones View Post
            The only problem I see is the inability to use the Updater to update any of my plug-ins. When I *just* updated, I had to restart HomeSeer. Please restart HomeSeer to confirm it resolves the issues you are experiencing.

            Regards,
            Ultrajones
            I had performed multiple restarts before I reverted. I do not take updating lightly - or - without caution.

            Comment


            • #7
              I restarted HomeSeer multiple times. Rebooted the PC. Tried disabling and enabling the plug-in. All fails.

              I was in contact with Elk this morning because I was unable to connect to the M1G with the ElkRP software. Turns out there is an issue with a windows update that prevents it from communicating and they are working on a update for the ElkRP software. Is it possible that this is also effecting your plug-in? But why is it when I roll back to my older version it runs fine.

              Comment


              • #8
                I have been getting these errors since several versions ago. Errors like this:

                Dec-14 18:09:11 Warning Invalid checksum 0 for command PC as data N525
                Dec-14 18:09:11 Warning Raw data was: 0BPCN52510B0
                Dec-14 17:44:50 Warning Invalid checksum 0 for command PC as data M120
                Dec-14 17:44:50 Warning Raw data was: 0BPCM12010BA
                Dec-14 17:12:40 Warning No response/improper response from Elk M1 to command 'az00'
                Dec-14 17:12:39 Warning Invalid checksum 160 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000
                Dec-14 17:12:39 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000008B
                Dec-14 17:11:52 Warning No response/improper response from Elk M1 to command 'az00'
                Dec-14 17:11:50 Warning Invalid checksum 202 for command Z0 as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000
                Dec-14 17:11:50 Warning Raw data was: DAZ000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000000000008B
                Dec-14 16:46:40 Warning No response/improper response from Elk M1 to command 'az00'
                Dec-14 16:46:38 Warning Invalid checksum 112 for command AZ as data 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 0000000000000000000000000
                Dec-14 16:46:38 Warning Raw data was: D6AZ00000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000000008B
                Dec-14 16:31:08 Warning Invalid checksum 50 for command 04 as data 00
                Dec-14 16:31:08 Warning Raw data was: BC04001088


                There is another thread about the same thing: https://forums.homeseer.com/showthread.php?t=137028

                Some things you can try are listed:
                • Ensure you have the latest firmware on your M1G
                • Check the quality of the RS232 cable
                • Check for packet loss between your HS machine and the ELK M1 XEP

                I have the latest firmware and have tried several cables including shielded cables. I get no packet loss (100% success). But the errors continue.

                It's either a bug in the M1G firmware (or the firmware of whatever interface you are using, M1G to CBus in my case), or a bug in the plugin.

                The errors result in occasional lost commands. Lights don't turn on, or a status change is not detected. Very annoying and not helping WAF.

                I'm happy to help debug as I really want this plugin to work. It's essential in connecting HS to our lighting system and home audio (Speakercraft MZC-88).

                Marty
                iCore5 Win 10 Pro x64 SSD

                HS3 Pro Edition 3.0.0.435 Windows

                BLOccupied:,Device History:,Yamaha:,UltraMon3:,mcsXap:,Restart:,UltraNetatmo3:, UltraM1G3:,Ultra1Wire3:,BLBackup:,Harmony Hub:,DoorBird:,UltraECM3:,Nanoleaf 3P:,UltraRachio3:,Z-Wave:,SDJ-Health:,BLGarbage:,Blue-Iris:,Chromecast:,Pushover 3P:,EasyTrigger:

                Comment


                • #9
                  Can you please post the anti-virus name/version you are all using on your HomeSeer computer? I want to see if it may be related to this issue.
                  Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                  Comment


                  • #10
                    Webroot Secure Anywhere (v9.0.18.44) antivirus and firewall. All Windows firewalls are off, although the recommendation is that both should be on. But for the sake of debugging this plugin I have the windows firewalls off. Windows defender is off.

                    UltraM1G3 is added to the exceptions list in Webroot firewall.

                    Marty
                    iCore5 Win 10 Pro x64 SSD

                    HS3 Pro Edition 3.0.0.435 Windows

                    BLOccupied:,Device History:,Yamaha:,UltraMon3:,mcsXap:,Restart:,UltraNetatmo3:, UltraM1G3:,Ultra1Wire3:,BLBackup:,Harmony Hub:,DoorBird:,UltraECM3:,Nanoleaf 3P:,UltraRachio3:,Z-Wave:,SDJ-Health:,BLGarbage:,Blue-Iris:,Chromecast:,Pushover 3P:,EasyTrigger:

                    Comment


                    • #11
                      Updated my HS3 plugins yesterday.... Now also getting the same issue with the UltraM1G with the following in my logs every minute or so, and events triggered by the M1 zones not firing. The plugin has not crashed, jut not workng correctly.

                      Version with the issues is 3.0.6551.16372

                      Code:
                      ec-27 7:00:02 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0900'
                      Dec-27 7:00:01 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0900'
                      Dec-27 6:59:59 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0900'
                      Dec-27 6:59:57 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0800'
                      Dec-27 6:59:56 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0800'
                      Dec-27 6:59:55 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0800'
                      Dec-27 6:59:53 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0700'
                      Dec-27 6:59:52 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0700'
                      Dec-27 6:59:51 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0700'
                      Dec-27 6:59:48 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0500'
                      Dec-27 6:59:46 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0500'
                      Dec-27 6:59:45 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0500'
                      Dec-27 6:58:40 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv1000'
                      Dec-27 6:58:39 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv1000'
                      Dec-27 6:58:38 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv1000'
                      Dec-27 6:58:36 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0900'
                      Dec-27 6:58:35 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0900'
                      Dec-27 6:58:33 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0900'
                      Dec-27 6:58:32 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0800'
                      Dec-27 6:58:31 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0800'
                      Dec-27 6:58:29 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0800'
                      Dec-27 6:58:28 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0700'
                      Dec-27 6:58:28 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0700'
                      Dec-27 6:58:26 AM 	  	Warning 	No response/improper response from Elk M1 to command 'cv0700'

                      Comment


                      • #12
                        Does anyone have a copy of an older plugin available they could make available for download? (I'm on a Google hosted email and it tends to silently reject emails with EXEs attached, even if they are zipped)

                        I need to roll back but don't have an earlier version on hand... This version is causing WAF unhappiness as HS events are triggering up to 15 minutes late, I guess due to retries and queuing due to the errors...

                        Edit - I just tried increasing the "Wait Time Per Command" in the plugin options from 1.5 to 2.5 and this *appears* to have overcome the problem... (Still set to the default 02 attempts per command)
                        Need to let the system soak for a while to be sure, but so far no errors and zone devices are updating in real time. Wonder if anything in this version may have touched the command response timeouts?

                        Edit 2 - Nope... Within half an hour the errors and delayed actions are back. Back to plan A with the rollback, if anyone can send me an older version. Was worth a try :-(

                        Cheers,
                        Geoff
                        Last edited by geodementia; January 3rd, 2018, 04:16 AM.

                        Comment


                        • #13
                          Randall,

                          I am helping Geoff as I see these messages every once in a while as well. Not convinced that it is the plugin. Is it possible that it could be messages from the Elk with invalid checksums? How does the plugin handle invalid messages?

                          I presume that the answer is to enable logging. Is it possible to enable logging so that the plugin will report all invalid messages but nothing else? I have seen the Elk send messages with invalid checksums. Happens with my thermostats quite frequently...

                          Otherwise, I will update my Elk Datalogger such that we can trace down the issue.
                          HomeSeer 2, HomeSeer 3, Allonis myServer, Amazon Alexa Dots, ELK M1G, ISY 994i, HomeKit, BlueIris, and 6 "4k" Cameras using NVR, and integration between all of these systems. Home Automation since 1980.

                          Comment


                          • #14
                            Originally posted by Krumpy View Post
                            Randall,

                            I am helping Geoff as I see these messages every once in a while as well. Not convinced that it is the plugin. Is it possible that it could be messages from the Elk with invalid checksums? How does the plugin handle invalid messages?

                            I presume that the answer is to enable logging. Is it possible to enable logging so that the plugin will report all invalid messages but nothing else? I have seen the Elk send messages with invalid checksums. Happens with my thermostats quite frequently...

                            Otherwise, I will update my Elk Datalogger such that we can trace down the issue.
                            The Elk ASCII protocol describes a means of verifying the validity of a packet by calculating the checksum. When the plug-in detects an invalid checksum in a received packet, it's written to the logs as an error and the packet is discarded (not processed).

                            Regards,
                            Ultrajones
                            Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                            Comment


                            • #15
                              Can someone experiencing an issue send me debug output along with an explanation of what issue they are seeing?

                              https://forums.homeseer.com/showthread.php?t=130803

                              Regards,
                              Ultrajones
                              Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

                              Comment

                              Working...
                              X