Announcement

Collapse
No announcement yet.

Latest update chewing up CPU - Solved!

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

    #16
    Good news?

    I've been sending log files to Bob for what started out as a comm problem, but evolved to include slow response and high CPU load. At his request I just tested version 58. In my initial testing, the response time was very good most of the time, almost as fast as the response from a zone keypad. (I was impatient and started testing almost immediately after restarting HS, so my very first tests probably reflected that, but once HS3 had time to settle down the results all seemed to be consistently good.) The plug-in detected on/off commands from the keypad, but did not detect source selection changes. I have not tested any other keypad functions yet.

    I'm still using the HS2 version, so only connect to HS3 for testing. Now that it seems to be working more like the HS2 version I plan to do more serious testing - probably tomorrow.
    Mike____________________________________________________________ __________________
    HS3 Pro Edition 3.0.0.548, NUC i3

    HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF | RFXCOM | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3 | EtherRain | Ubiquiti

    Comment


      #17
      Can someone send me any older versions they have?
      I don't have many, but here's a copy of 52.
      Attached Files
      Mike____________________________________________________________ __________________
      HS3 Pro Edition 3.0.0.548, NUC i3

      HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF | RFXCOM | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3 | EtherRain | Ubiquiti

      Comment


        #18
        Thanks for the file, Uncle Michael.

        Blade, I'm loading that latest version. I've already lost all my old device configs, so this is pretty much "from scratch" for me; so we'll see how it goes!

        Comment


          #19
          So you can attach a .Zip and not a .Rar?
          Originally posted by rprade
          There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

          Comment


            #20
            Okay... loaded latest and tested. I'm not at home, but I can test through a camera to see if there's sound or not. So I'm just testing with turning a zone on/off.

            Using the latest .58 version, I get an "on" with just a couple seconds delay and the "off" doesn't seem to work at all. Not much in the HS logs even with things turned on:

            Code:
            Feb-01 3:34:40 PM	 	BLRussound Info	Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 00 00 00 00 01 12 F7
            Feb-01 3:34:16 PM	 	BLRussound Info	Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 01 00 00 00 01 13 F7
            Feb-01 3:33:51 PM	 	BLRussound Info	BLRussound Debug Logging Enabled!
            Feb-01 3:28:50 PM	 	BLRussound Info	Russound Com Port - MSCommLib (COM7) Open
            Feb-01 3:28:46 PM	 	Plug-In	Finished initializing plug-in BLRussound
            Feb-01 3:28:46 PM	 	BLRussound start	BLRussound plugin has been initialized
            Feb-01 3:28:45 PM	 	BLRussound start	Controllers have been loaded.
            Feb-01 3:28:44 PM	 	BLRussound start	Loaded configuration successfully
            Feb-01 3:28:44 PM	 	BLRussound start	BLRussound version is: 2.0.58.0
            Feb-01 3:28:44 PM	 	BLRussound start	Initializing BLRussound...
            Feb-01 3:28:44 PM	 	Info	Plugin BLRussound has connected. IP:127.0.0.1:62451
            versus I roll back to the .52 version and do the same thing and it works immediately and the logs look more as expected:
            Code:
            Feb-01 3:40:46 PM	 	BLRussound Info	Message Rcvd --- F0 7F 00 71 00 00 7F 00 03 04 04 03 02 04 00 00 00 01 00 01 00 00 F7
            Feb-01 3:40:46 PM	 	BLRussound Info	Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 3A 00 00 00 00 00 00 2A F7
            Feb-01 3:40:45 PM	 	BLRussound Info	Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 37 00 00 00 00 00 00 27 F7
            Feb-01 3:40:45 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 05 02 01 00 02 01 00 F1 23 00 00 00 00 00 01 22 F7
            Feb-01 3:40:45 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 02 01 01 02 01 01 00 00 01 00 10 00 00 00 00 00 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 61 F7
            Feb-01 3:40:45 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 02 02 04 00 00 00 01 00 01 00 00 17 F7
            Feb-01 3:40:45 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 05 02 04 00 00 00 01 00 01 00 00 1A F7
            Feb-01 3:40:44 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 04 02 04 00 00 00 01 00 01 00 00 19 F7
            Feb-01 3:40:44 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 00 02 04 00 00 00 01 00 01 00 48 5D F7
            Feb-01 3:40:44 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 06 02 04 00 00 00 01 00 01 00 00 1B F7
            Feb-01 3:40:44 PM	 	BLRussound Info	Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 00 00 00 00 01 12 F7
            Feb-01 3:40:23 PM	 	Warning	File does not exist: C:\Program Files (x86)\HomeSeer HS3\html\BLRussoundOptions
            Feb-01 3:40:17 PM	 	BLRussound Info	Message Rcvd --- F0 7F 00 71 00 00 7F 00 03 04 04 03 02 04 00 00 00 01 00 01 00 01 F7
            Feb-01 3:40:17 PM	 	BLRussound Info	Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 3A 00 00 00 01 00 00 2B F7
            Feb-01 3:40:17 PM	 	BLRussound Info	Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 37 00 00 00 08 00 00 2F F7
            Feb-01 3:40:16 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 05 02 01 00 02 01 00 F1 23 00 01 00 00 00 01 23 F7
            Feb-01 3:40:16 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 06 08 03 00 00 05 0F F7
            Feb-01 3:40:16 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 00 02 04 00 00 00 01 00 01 00 11 26 F7
            Feb-01 3:40:16 PM	 	BLRussound Info	Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 06 02 04 00 00 00 01 00 01 00 02 1D F7
            Feb-01 3:40:16 PM	 	BLRussound Info	Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 01 00 00 00 01 13 F7
            I grabbed the really detailed logs as well from both cases - way too much gibberish but I can upload them if it'd help. Short version seems to be no serial data received back?

            I'm using VSPE with a GC-iTach and msCommLib.

            Comment


              #21
              Originally posted by gregoryx View Post
              Okay... loaded latest and tested. I'm not at home, but I can test through a camera to see if there's sound or not. So I'm just testing with turning a zone on/off.

              Using the latest .58 version, I get an "on" with just a couple seconds delay and the "off" doesn't seem to work at all. Not much in the HS logs even with things turned on:

              Code:
              Feb-01 3:34:40 PM         BLRussound Info    Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 00 00 00 00 01 12 F7
              Feb-01 3:34:16 PM         BLRussound Info    Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 01 00 00 00 01 13 F7
              Feb-01 3:33:51 PM         BLRussound Info    BLRussound Debug Logging Enabled!
              Feb-01 3:28:50 PM         BLRussound Info    Russound Com Port - MSCommLib (COM7) Open
              Feb-01 3:28:46 PM         Plug-In    Finished initializing plug-in BLRussound
              Feb-01 3:28:46 PM         BLRussound start    BLRussound plugin has been initialized
              Feb-01 3:28:45 PM         BLRussound start    Controllers have been loaded.
              Feb-01 3:28:44 PM         BLRussound start    Loaded configuration successfully
              Feb-01 3:28:44 PM         BLRussound start    BLRussound version is: 2.0.58.0
              Feb-01 3:28:44 PM         BLRussound start    Initializing BLRussound...
              Feb-01 3:28:44 PM         Info    Plugin BLRussound has connected. IP:127.0.0.1:62451
              versus I roll back to the .52 version and do the same thing and it works immediately and the logs look more as expected:
              Code:
              Feb-01 3:40:46 PM         BLRussound Info    Message Rcvd --- F0 7F 00 71 00 00 7F 00 03 04 04 03 02 04 00 00 00 01 00 01 00 00 F7
              Feb-01 3:40:46 PM         BLRussound Info    Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 3A 00 00 00 00 00 00 2A F7
              Feb-01 3:40:45 PM         BLRussound Info    Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 37 00 00 00 00 00 00 27 F7
              Feb-01 3:40:45 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 05 02 01 00 02 01 00 F1 23 00 00 00 00 00 01 22 F7
              Feb-01 3:40:45 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 02 01 01 02 01 01 00 00 01 00 10 00 00 00 00 00 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 61 F7
              Feb-01 3:40:45 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 02 02 04 00 00 00 01 00 01 00 00 17 F7
              Feb-01 3:40:45 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 05 02 04 00 00 00 01 00 01 00 00 1A F7
              Feb-01 3:40:44 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 04 02 04 00 00 00 01 00 01 00 00 19 F7
              Feb-01 3:40:44 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 00 02 04 00 00 00 01 00 01 00 48 5D F7
              Feb-01 3:40:44 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 06 02 04 00 00 00 01 00 01 00 00 1B F7
              Feb-01 3:40:44 PM         BLRussound Info    Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 00 00 00 00 01 12 F7
              Feb-01 3:40:23 PM         Warning    File does not exist: C:\Program Files (x86)\HomeSeer HS3\html\BLRussoundOptions
              Feb-01 3:40:17 PM         BLRussound Info    Message Rcvd --- F0 7F 00 71 00 00 7F 00 03 04 04 03 02 04 00 00 00 01 00 01 00 01 F7
              Feb-01 3:40:17 PM         BLRussound Info    Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 3A 00 00 00 01 00 00 2B F7
              Feb-01 3:40:17 PM         BLRussound Info    Message Rcvd --- F0 7E 00 71 00 00 7F 05 02 01 00 02 01 00 F1 37 00 00 00 08 00 00 2F F7
              Feb-01 3:40:16 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 05 02 01 00 02 01 00 F1 23 00 01 00 00 00 01 23 F7
              Feb-01 3:40:16 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 06 08 03 00 00 05 0F F7
              Feb-01 3:40:16 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 00 02 04 00 00 00 01 00 01 00 11 26 F7
              Feb-01 3:40:16 PM         BLRussound Info    Message Rcvd --- F0 00 00 7D 00 00 7F 00 03 04 04 06 02 04 00 00 00 01 00 01 00 02 1D F7
              Feb-01 3:40:16 PM         BLRussound Info    Message Sent --> F0 00 00 7F 00 00 71 05 02 02 00 00 F1 23 00 01 00 00 00 01 13 F7
              I grabbed the really detailed logs as well from both cases - way too much gibberish but I can upload them if it'd help. Short version seems to be no serial data received back?

              I'm using VSPE with a GC-iTach and msCommLib.

              Bro. You've gotta create a ticket on Blade's site and upload these files! Your information is priceless!
              Originally posted by rprade
              There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

              Comment


                #22
                Do you have the option selected to log all messages received from the Russound
                I am only seeing sent ones in .58

                Which model of Russound?
                Cheers,
                Bob
                Web site | Help Desk | Feature Requests | Message Board

                Comment


                  #23
                  I'm still seeing the announcement lag in .58 so I caution everyone to continue to avoid updates for now. I have a log in to Blade.
                  Originally posted by rprade
                  There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                  Comment


                    #24
                    Originally posted by S-F View Post
                    I'm still seeing the announcement lag in .58 so I caution everyone to continue to avoid updates for now. I have a log in to Blade.
                    I only addressed cpu usage in 2.0.58. Can u get me a log of the delay. I need to know what announcement was spoken so I can track it down

                    I am going to need to build a service into BLSpeech in order to make this work better. That is going to take me a bit of time to do but I think it will really help the interaction between the two of them
                    I will need to give this some thought
                    Cheers,
                    Bob
                    Web site | Help Desk | Feature Requests | Message Board

                    Comment


                      #25
                      Originally posted by Blade View Post
                      I only addressed cpu usage in 2.0.58. Can u get me a log of the delay. I need to know what announcement was spoken so I can track it down

                      I am going to need to build a service into BLSpeech in order to make this work better. That is going to take me a bit of time to do but I think it will really help the interaction between the two of them
                      I will need to give this some thought

                      I attached a log a little while ago to the ticket I opened on your site. It's only a BLRussound log though. Do you need one from BLSpeech too?
                      Originally posted by rprade
                      There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                      Comment


                        #26
                        Yes a log from BLSpeech would be good so I can see the calls back and forth
                        Cheers,
                        Bob
                        Web site | Help Desk | Feature Requests | Message Board

                        Comment


                          #27
                          Aw man! I just restored from a backup. Is there anyone else out there running one of the newer versions that can get a log? Anybody?
                          Originally posted by rprade
                          There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                          Comment


                            #28
                            Originally posted by S-F View Post
                            Aw man! I just restored from a backup. Is there anyone else out there running one of the newer versions that can get a log? Anybody?
                            I'm running .58 and can test with BLSpeech. What are you looking for, just a sample speak to a zone? What are the symptoms?

                            Sent from my XT1060 using Tapatalk

                            Comment


                              #29
                              Just have any zone speak something. The zone won't turn on for around 20 or so seconds and then it's another 20 or so seconds before the TTS is spoken.
                              Originally posted by rprade
                              There is no rhyme or reason to the anarchy a defective Z-Wave device can cause

                              Comment


                                #30
                                Is CPU usage better in 2.0.58? That was the main goal of this build

                                Sireone, you can directly email me the 2 logs zipped if you want. Make sure you tell me exactly what u did so I can track it down
                                Cheers,
                                Bob
                                Web site | Help Desk | Feature Requests | Message Board

                                Comment

                                Working...
                                X