I use several concurrent transactions (up to two additional messages started before a requested "report" is received from the network) with essentially no delays between transactions. Admittedly, I'm pushing the controller much more aggressively than the current OZW library. If the average failure is after 100,000 transactions, it would take almost 70 days (at 1 transaction per minute) to observe the issue. ![]() Just slowing down the rate at which transactions are started on the controller might just extend the time required to observe a failure. If they won't/can't fix the firmware, I'm hoping that they'll at least diagnose the issue carefully enough that a reasonable workaround can be devised. I suspect that it's a firmware bug (like some buffer overflows). ![]() While I'm glad they've acknowledged the issue, I'm not sure what they mean by "the interval time of receiving messages is less than 1 minute." Every Z-Wave software of which I'm aware sends substantially more than one message per minute, so I'm hoping that's not what they meant! I've emailed back to ask them for more clarification and to offer some help (in the form of a program that can pretty consistently "break" the Z-Stick by making it unresponsive) if they'll further diagnose the issue. This will not happen if the interval time of receiving messages is more than 1 minute.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |