Zigbee Long Poll Interval does not follow the set value

RE: Zigbee Long Poll Interval does not follow the set value

ETnaveen — Tue, 01 Nov 2022 08:15:54 GMT

Hi,
We found the problem to be in setting the value of long poll interval and keep alive timeout. As keep alive timeout is less and it is more or less equal to long poll interval, it created the problem. We are able to achieve the required polling interval by increasing the keep alive timeout to a large value.

Thank you very much for your time and effort.

RE: Zigbee Long Poll Interval does not follow the set value

Simonr — Tue, 18 Oct 2022 06:23:36 GMT

I got an answer from our developers on this, and here are their thoughts on what the issue likely is connected to:

The poll interval is indeed configurable, and depends on the device configuration, Turbo poll functionality, and the configuration commands, sent by the coordinator/hub. Detailed information on this can be found in the "End device keep alive" and "Data polling" mechanism in the ZBOSS documentation:

One of these (likely the config commands) sent by I.E. the Alexa hub is likely the difference between your working and non-working application.

Best regards,

Simon

RE: Zigbee Long Poll Interval does not follow the set value

Simonr — Tue, 11 Oct 2022 07:32:18 GMT

Hi,

From looking at the sniffer traces, they both seem similar, except in the request for setting the poll interval. Where the connection to Conbee II seems to set the keep alive timeout to false, while it is set to true in the other poll interval request.

I think that a gateway will always have the last say when it comes to most parameter negotiations, poll intervals included, so it might be that the Alexa doesn't allow/support the poll interval you're suggesting.

I have asked internally for some of our experts to look at this, but unfortunately it doesn't seem like we can't expect a reply until next week.

Best regards,

Simon

RE: Zigbee Long Poll Interval does not follow the set value

ETnaveen — Fri, 07 Oct 2022 07:09:19 GMT

Hi,

Thanks for the reply.

The coordinator that's working is Conbee II with deconz and some other gateways including Alexa has higher polling interval. So all coordinators are third party devices which we don't have any control over.

Please ignore the power part of ppk screenshot. The intention of ppk is to show the difference in frequency of polling peaks between the two coordinators. This can be validated with the attached wireshark sniffer logs.

If the coordinator can request preferred polling interval, can the end device override the request and stick to a polling interval? Is there any other possible scenario where we are going wrong? I understand that the information is less, but any help is greatly appreciated.

The attached screenshots of the sniffer can give an idea about the difference between the two coordinators.

RE: Zigbee Long Poll Interval does not follow the set value

Simonr — Mon, 03 Oct 2022 14:13:19 GMT

I think I'll need some more details on these gateways you're using. What is the difference between the "particular" working gateway compared to the other one that isn't working? Is this two nRF devices or phones/tablets or some other product? I think gateways can request preferred polling intervals as well, so my guess is that that is what's happening. What are the PPK logs supposed to show here? In what I assume is the non-working one, the poll intervals seemt o be very sporadic, or is the device doing something else than just polling here?

Best regards,

Simon