It was not the update !!!! Hello does the 2026.5.4 update work for openthread esphome in general.
My devices where all disconnected. And I restored 5.4.
Regards Frank
Hello, it was not the update, I fear the Sonoff borderrouter needed a power off, as warmstart did not solve the issue. Strange.
Sorry it happens again and again this is hopefully a log that helps
I have a sonoff v3 dongle with thread firmware, it worked all fine till yesterday
:13:21.026 [N] Mle-----------: Different partition (peer:1703433202, local:2034078248)
01:13:21.026 [W] Mle-----------: Failed to process Advertisement: LinkMarginLow
01:13:21.919 [N] MeshForwarder-: Dropping IPv6 TCP msg, len:80, chksum:3da6, ecn:no, sec:yes, error:Drop, prio:low, radio:all
01:13:21.919 [N] MeshForwarder-: src:[fdd7:75b9:f165:1:bb96:d0ad:a9c8:ccea]:55182
01:13:21.919 [N] MeshForwarder-: dst:[fdd7:75b9:f165:1:b6fa:4187:27cb:5f13]:6053
01:13:25.247 [N] MeshForwarder-: Dropping IPv6 TCP msg, len:80, chksum:751d, ecn:no, sec:yes, error:Drop, prio:low, radio:all
01:13:25.247 [N] MeshForwarder-: src:[fdd7:75b9:f165:1:bb96:d0ad:a9c8:ccea]:51136
01:13:25.247 [N] MeshForwarder-: dst:[fdd7:75b9:f165:1:3e45:7d3f:fbe0:f1ac]:6053
01:13:25.935 [N] Mle-----------: Different partition (peer:1703433202, local:2034078248)
01:13:25.936 [N] Mle-----------: Attach attempt 0, BetterPartition
01:13:27.295 [N] MeshForwarder-: Dropping IPv6 TCP msg, len:80, chksum:19c6, ecn:no, sec:yes, error:Drop, prio:low, radio:all
01:13:27.296 [N] MeshForwarder-: src:[fdd7:75b9:f165:1:bb96:d0ad:a9c8:ccea]:59716
01:13:27.296 [N] MeshForwarder-: dst:[fdd7:75b9:f165:1:db4e:8ea1:cf3d:f7df]:6053
01:13:28.723 [N] Mle-----------: Role leader -> detached
01:13:28.723 [N] Mle-----------: RLOC16 b000 -> 1405
01:13:28.727 [N] Mle-----------: Role detached -> child
01:13:28.728 [N] Mle-----------: Sending message to inform previous parent 0x3000
[NOTE]-BBA-----: BackboneAgent: Backbone Router resigns Primary to Secondary!
01:13:34.571 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:92, chksum:2d01, ecn:no, to:ceba2cae15d9f2b2, sec:no, error:NoAck, prio:net, radio:all
01:13:34.571 [N] MeshForwarder-: src:[fe80:0:0:0:588d:fa8a:9370:d4ee]:19788
Hard to figure out what the underlying problem is, but the logs indicate the Thread network is partitioning which generally means there are weak RF links between Thread devices.
It also appears you have more than one TBR, as this one has become secondary, and while this is generally OK, some TBRs don't handle working with other TBRs so well.
1 Like