OTBR Error

Configuration Matter/Thread
1

I am a newbie. I have a SMLight SLZB-06MR2. I have matter set on radio 1 and ZigBee on radio 2

I think I recently updated the SMLight device in Home Assistant. I then noticed today under integrations an error for the OTBR integration.

I then went to add-ons and saw the below in the log. It just keeps repeating.

[22:01:32] INFO: Starting socat TCP client for OTBR daemon…

2025/11/18 22:01:32 socat[1598] W recvmsg(): Resource temporarily unavailable

2025/11/18 22:01:32 socat[1598] E connect(7, AF=2 192.168.68.122:6638, 16): Connection refused

I tried removing the add on and reinstalling, unplugging the device restarting HA and powering up the device and restarting HA. I still have the same issue when interrogating the log in add-ons.

Also the OTBR in integrations has disappeared.

I’m not sure how this is used in my system as I think all devices are working but clearly there is an issue.

Any help would be great.

2

Although I don’t have an SMLight, assuming that this IP address is that of the SMLight, this would indicate that the SMLight doesn’t have port 6638 available, or something else is currently using that port.

1 Like
3

I have checked the setup on the web interface and it is as below

1000020662
10000206621080×2400 192 KB

4

But your error text says port 6638 and your configuration picture says 7638

5

Config shows it is using port 6638 for Thread/EFR32MG21, so not sure why its not accepting connections from HA. I have seen other types of devices not letting go of the ports when disconnected, so maybe try a power down/up of the MR2 and see if that does anything.

Out of curiosity, is ZigBee working for port 7638?

1 Like
6

That is true.
I did not see the other line in the screenshot. :slight_smile:

1 Like
7

Yes ZigBee is fine. I will try power cycling it again when I get home. I have some matter wall switches and relay and they seem to be working fine which I don’t understand They are all Sonofff so I’m not sure if they are actually using the Ewelink protocol.

8

No change with power cycling. Still erroring constantly

9

Hmmmm… no idea then

1 Like
10

Have you turned off USB on the slzb?

1 Like
11

It was working before and I’ve not changed anything but I do think there was an update. How do I do that ?

12

It looks like USB mode was put on during the update so that error is solved - thanks pyberg.

I still have the following error now -

Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
00:00:36.310 [W] DuaManager----: Failed to perform next registration: NotFound
00:00:36.310 [W] DuaManager----: Failed to perform next registration: NotFound

13

DuaManager is nothing to be concerned about. Its a typical error that can be ignored.

1 Like
14

That’s great. Is here anyway to ‘disable’ or resolve it as I don’t believe I had it before but can’t be sure

15

I understand it to be a feature of Thread1.2 in commercial deployments where there can be multiple Thread networks that have a “common Domain” (was not able to determine what that meant), and apparently it requires a “DuaManager” which I don’t think actually exists, so I think that is why this shows up at boot time; an I don’t know of anyway to disable it.

1 Like