OTBR Leader election takes more time

[muralidhar-bn]

I have setup Raspberry Pi 4 - 2 devices with OTBR agent - One becomes a leader and other as router. Along with this 3 nanoleaf bulbs are joined to Thread network to form a mesh network. When i try to switch of Leader OTBR i observed electing new Leader takes lot of time 3 ~ 10 minutes. Is this normal behaviour ?

[jwhui]

Thread devices detect when the Leader is disconnected by observing that they are no longer receiving updates from the Leader. This timeout is set to a few minutes.

[vasukanster]

@jwhui Thanks for you kind answers and support, we are new to this Thread protocol
Below is one of our test setup for testing
OTBR connects to-->Nanoleaf bulb1 connects to --> Nanoleaf bulb2 (everything is within 15meters)
Sometimes we noticed that OTBR is not receiving any service details (like SRP records info) for Nanoleaf bulbs even though devices are placed nearby.
Is the protocol/otbr side any configurations can we try to increase the detection logics so that we can enhance the protocol behavior?

[jwhui]

What firmware version is running on the Nanoleaf bulbs?

[gadekula]

Please find the version 3.6.196

[jwhui]

The Nanoleaf bulbs should be sending SRP Update messages when they attach to the network.

Are you observing that the SRP server table is empty? For example, with the srp server service command?

Note that this discussion has diverged to a different topic. You may want to open a separate discussion.

[vasukanster]

Yes, we observed srp server service is empty. Yes we can have separate discussion