Announcement

Collapse
No announcement yet.

New Error on .460

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

  • #91
    Thanks Rich! I'll try that out and provide feedback.
    HS 3.0.0.548: 1976 Devices 1156 Events
    Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

    Comment


    • #92
      Just so I understand - under the new queue size the issue doesn't go away - an errant plugin can still cause issues. However, there is a little more breathing room and if the queue doesn't get to 2000 then commands will not be lost? However, if the plugin is causing issues, and it does build up, then it can impact the performance even if doesn't reach the new limit of 2000?

      Comment


      • #93
        Correct.
        Originally posted by simonmason View Post
        Just so I understand - under the new queue size the issue doesn't go away - an errant plugin can still cause issues. However, there is a little more breathing room and if the queue doesn't get to 2000 then commands will not be lost? However, if the plugin is causing issues, and it does build up, then it can impact the performance even if doesn't reach the new limit of 2000?
        website | buy now | support | youtube

        Comment


        • #94
          Originally posted by simonmason View Post
          Just so I understand - under the new queue size the issue doesn't go away - an errant plugin can still cause issues. However, there is a little more breathing room and if the queue doesn't get to 2000 then commands will not be lost? However, if the plugin is causing issues, and it does build up, then it can impact the performance even if doesn't reach the new limit of 2000?
          Honestly I would be surprised if the larger queue size helped in any but very certain cases. In computers queues are generally empty or full, they don't float around the middle. Either the consumer processes the items faster than the are produced (queue stays or very near 0) or the producer generates events faster than the consumer can process them (queue stays full). Ultimately this is an issue with plugins, I have seen many very slow plugins, and until more developers understand they need to audit this code for performance, this issue won't go away. The MOST useful thing that HS can do is report metrics on each plugin, give an average (in microseconds) of the calls to the HSEvent function. That will immediately let people know which plugins need to address their speed issues. I am guessing within a month of that being available, there will be lots of new versions of plugins in the updater.

          Rich, just keep two longs for each plugin. A total time spent in HSEvent (wrap the call and get the difference in mills) and the total calls. When the queue is full (or once a day or something) dump the numbers to the log. The problem will abate quickly after this is available.

          Comment


          • #95
            Up and running on .495 and zero dropped callback messages in the log during startup.
            HS 3.0.0.548: 1976 Devices 1156 Events
            Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

            Comment


            • #96
              Originally posted by sparkman View Post
              Up and running on .495 and zero dropped callback messages in the log during startup.
              same

              Comment


              • #97
                Updating now. Will report back. I did receive an updated plugin which helped, and removed another an things did get better, but I was still seeing queue backups on occasion. Hopefully the additional headroom will resolve this. Stay tuned.

                My home is smarter than your honor roll student.

                Comment


                • #98
                  Looking very promising.
                  My home is smarter than your honor roll student.

                  Comment


                  • #99
                    Another update. I have had zero Dropped Event Callback warnings since installing .495. None during startups and none while HS is running. Thanks rjh !
                    HS 3.0.0.548: 1976 Devices 1156 Events
                    Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

                    Comment


                    • Separately I have read about some issues with this version and z-wave - with z-wave version 255. I am running z-wave 252. Any issues just updating HS3 to .495. I really don't want to cause issues with my z-wave setup. Thanks

                      Comment


                      • Originally posted by simonmason View Post
                        Separately I have read about some issues with this version and z-wave - with z-wave version 255. I am running z-wave 252. Any issues just updating HS3 to .495. I really don't want to cause issues with my z-wave setup. Thanks
                        I'm running z-wave .249 with it and no issues that I've seen.
                        HS 3.0.0.548: 1976 Devices 1156 Events
                        Z-Wave 3.0.1.262: 123 Nodes on one Z-Net

                        Comment


                        • Originally posted by sparkman View Post

                          I'm running z-wave .249 with it and no issues that I've seen.
                          I can't really say what did happen to me ( The time of rebuilding the z wave network was less than analyses whats wrong.. wait or comment on forum etc) ... but had to built my z wave from scratch.

                          I was on .49, updated o .52, try to ping '' all the node.... noone were pingable with the plugin. They seems to be able to report some value thought...

                          I updated to .55 , but no luck..

                          So, removed all the z wave related stuff in my folders. When i mean all , I really mean ALL. Started a fresh network on .55 .

                          Did a backup of both hs3 and the z wave interface when i finished. Seems to run fine since yesterday... From now on, Iwill backup my Data z wave folder somewhere else.


                          I think the database did corrupt or the plugin picked a wrong one.. not sure seriously. I feels like it did'nt like the version transition in some way... and .55 is fine ... ( I hope)

                          Comment


                          • Originally posted by MattL0 View Post

                            I can't really say what did happen to me ( The time of rebuilding the z wave network was less than analyses whats wrong.. wait or comment on forum etc) ... but had to built my z wave from scratch.

                            I was on .49, updated o .52, try to ping '' all the node.... noone were pingable with the plugin. They seems to be able to report some value thought...

                            I updated to .55 , but no luck..

                            So, removed all the z wave related stuff in my folders. When i mean all , I really mean ALL. Started a fresh network on .55 .

                            Did a backup of both hs3 and the z wave interface when i finished. Seems run fine since yesterday... From now one I will backup my Data z wave folder somewhere else.


                            I think the database did corrupt or the plugin picked a wrong one.. not sure seriously. I feels like it did'nt like the version transition in some way... and .55 is fine ... ( I hope)
                            Were you on .495 when you tried the update to z-wave 252? I am already on 252 so hoping the .495 update won’t be a problem


                            Sent from my iPhone using Tapatalk

                            Comment


                            • Originally posted by simonmason View Post

                              Were you on .495 when you tried the update to z-wave 252?

                              Yes

                              Comment


                              • Originally posted by sparkman View Post
                                Another update. I have had zero Dropped Event Callback warnings since installing .495. None during startups and none while HS is running. Thanks rjh !
                                Ditto here.
                                My home is smarter than your honor roll student.

                                Comment

                                Working...
                                X