Bluetooth Mesh Time Server Multi-Hop

RE: Bluetooth Mesh Time Server Multi-Hop

BjoernS — Thu, 15 Jul 2021 07:34:50 GMT

Hi Marjeris,

thank you very much for the response! That clarifies my question.

RE: Bluetooth Mesh Time Server Multi-Hop

Marjeris Romero — Wed, 14 Jul 2021 20:31:08 GMT

Hi,

Here is an update from the team:

Brief resume:

Time Status as an unsolicited message is sent with 1 hop limitation.

Time Status as a response is sent with configured TTL.

Customer, of course, is able to avoid this limitation for retransmission by removing this line:

https://github.com/nrfconnect/sdk-nrf/blob/master/subsys/bluetooth/mesh/time_srv.c#L471

but it will break spec requirements:

5.3.1.2.2 Sending a Time Status message

...

If sent as an unsolicited message, the Time Status message shall be sent with TTL=0 to avoid building up cumulative time errors resulting from delays in processing the messages by relays.

...

PR with doc clarification here: https://github.com/nrfconnect/sdk-nrf/pull/5109

Best regards,

Marjeris

RE: Bluetooth Mesh Time Server Multi-Hop

Marjeris Romero — Mon, 12 Jul 2021 12:15:40 GMT

Hi,

No update from the Mesh team yet. It's summer vacation time here in Norway so it can take up to 2-3 weeks before I can come back to you with an answer, as much of the staff is on vacation right now. I am sorry for the inconvenience.

Best regards,

Marjeris

RE: Bluetooth Mesh Time Server Multi-Hop

BjoernS — Mon, 12 Jul 2021 09:33:18 GMT

Hi,

just wanted to ask if there are any updates yet?

RE: Bluetooth Mesh Time Server Multi-Hop

Mttrinh — Fri, 09 Jul 2021 15:33:07 GMT

Hi,

I have asked the Mesh team to clarify this, I will update you as soon as I get a response from them.