Thanks Rich! I'll try that out and provide feedback.
Announcement
Collapse
No announcement yet.
New Error on .460
Collapse
X
-
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
-
Correct.
Originally posted by simonmason View PostJust 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
-
Originally posted by simonmason View PostJust 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?
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
-
Originally posted by simonmason View PostSeparately 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. ThanksHS 4.2.8.0: 2134 Devices 1252 Events
Z-Wave 3.0.10.0: 133 Nodes on one Z-Net
Comment
-
Guest
Originally posted by sparkman View Post
I'm running z-wave .249 with it and no issues that I've seen.
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)
Sent from my iPhone using Tapatalk
Comment
Comment