Z wave monitor to prevent freeze

[cag014 628]

Hi all,

I see that some users have downloaded

Please login or register to see this link.

script and I think it could be a good idea to share our data and know-how to optimize our Z-wave performance.

In my case I have manage to reduce Z-wave traffic from average of event per 1.7 sec. to 4.8 sec (24 hours monitoring, 78 physical devices, 382 IDs), but I don't know if this is a good number. It will be interesting if anyone could share  an average of his system. That way we can compare and might be to achieve the right number and stable performance which may be could prevent Z-wave freeze in the future.

I think average of Z-wave traffic somehow depends on number of the devices in the system and again I believe we need team work to find correct formula for that.

Few users have shared with me that they have found devices, which "bombarding" the traffic with unnecessary reports and they fixed the issue.

It could be very helpful to all of us to share our solutions and fixes...  we all can learn from others

If you think it could violate your privacy,   please ignore this message...

Thank you

 

 

[nicopret 16]

70 physical devices on HC2 with the following being reported:

Please login or register to see this image.

/monthly_2023_02/image.png.2caf3180d0e4226a707b036014637524.png" />

 

I noticed @cag014 mentioned elsewhere that RPT should be less than 10%. One of my FGS22 switches (Device ID 182-184) have generated too many RPT during the monitoring period in question and I'm trying to figure out why as part of my quest to resolve my daily 503 errors.

Please login or register to see this spoiler.

 

 I'll appreciate feedback from others that have managed to solve their 503 errors. Thank you.

Edited February 8, 2023 by nicopret