Maximum number of generic level messages that a node can handle

RE: Maximum number of generic level messages that a node can handle

Mttrinh — Thu, 02 May 2019 13:29:04 GMT

Can you try setting the transition time to 1 second? Can you try sending Unacknowledged Level SET messages while sliding the slider, and send the final message (when user stops sliding) as Acknowledged Level Set?

Do the slider moves as desired? Can you send me the full log?

RE: Maximum number of generic level messages that a node can handle

DeveloperZ — Mon, 29 Apr 2019 15:34:52 GMT

What might be causing the issue then?
It happens when it has to process around 100 level messages in a minute!

RE: Maximum number of generic level messages that a node can handle

Mttrinh — Mon, 29 Apr 2019 14:08:29 GMT

There aren't any limit on the number of messages a node can process within a certain amount of time. It is only limited by the time taken by the internal processing logic to push the message to the higher layers one after the other.

RE: Maximum number of generic level messages that a node can handle

DeveloperZ — Fri, 26 Apr 2019 13:07:05 GMT

Hi,

It is the generic level server example but with the customized App. On the iOS App, we made changes to the slider used to setting the level such that on a scale of 0-100%, the app send a generic level message with different levels in different ranges with a transition time. Thus the node receives numerous levels as we move the slider back and forth.

I am not sure on how you can reproduce it :(

Maybe you can try it by setting a transition time of 2 sec and continuously setting the levels on the app at a rapid rate so that the node keeps receiving numerous messages and observe it!!!

RE: Maximum number of generic level messages that a node can handle

Mttrinh — Fri, 26 Apr 2019 12:51:21 GMT

Hi,

I'm not sure what is causing this issue. Is the generic level server example unmodified? Could you give me a step-by-step procedure on how I can reproduce this?

Best Regards,

Martin