Skip to content

Sonoff ZbBridgePro - connectivity issues with iobroker.zigbee #1405

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bjoernbusch opened this issue May 12, 2025 · 1 comment
Closed

Sonoff ZbBridgePro - connectivity issues with iobroker.zigbee #1405

bjoernbusch opened this issue May 12, 2025 · 1 comment

Comments

@bjoernbusch
Copy link

bjoernbusch commented May 12, 2025 •
edited
Loading

Hi there,

My setup looks the following:

Sonoff ZbBridgePro with Tasmota 14.6.0.2 (9f764ac-zbbrdgpro) connected via Wifi to Fritzbox (distance about 1.5m, static IP, fixed channel). Ethernet cable to switch, ethernet cable to RaspberryPi with iobroker native installation on NodeJS 20.19.1. iobroker.zigbee adapter in version 3.0.1, which contains "zigbee-herdsman": "3.3.2" and "zigbee-herdsman-converters": "23.13.0". The zigbee network itself looks very stable, I'm not losing any devices, but the iobroker.zigbee adapter and the gateway lose connection at least once a day and I can't pinpoint what I'm doing wrong.

At some point during the day, the iobroker.zigbee adapter loses the connection to the Sonoff ZbBridge Pro. Sometimes it recovers itself, sometimes it can't. Then sometimes I can just manually trigger a reconnect in the adapter successfully. Sometimes that doesn't work, then I restart both adapter and Sonoff ZbBridge Pro and sometimes even that doesn't help, then I wait for a couple of hours and try the whole procedure again and eventually the connection can be established again. During all that time, I can reach both iobroker and Tasmota via the Browser just fine.

I've created an issue on iobroker.zigbee with some logs and that error scenario looked like a Wifi / TCP issue, so I created an issue on Tasmota, but when looking at some more logs, TCP seams to look ok, it more looked like zigbee.herdsman is expecting an answer in 6 seconds and sometimes the Sonoff ZbBridge Pro is not fast enough? arendst/Tasmota#23407 (comment)

I've turned on Zigbee-herdsman debug info, but I don't think this is logging more information on the connect scenario. I'm not sure which logs to provide to you, are the Tasmota logs helpful to you? This is from the latest case, where the connection could not be established again:

05/11/2025,21:34:10,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE1C44810000020479470101007B006C415600000818090A000029AA08A3BB1978
05/11/2025,21:34:10,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C4794704D8D7137374FBA3BB48
05/11/2025,21:34:03,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019000491010D005B00B14E5000000C11710100861205080910000004911DF4
05/11/2025,21:34:00,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019000491010D005B002F714D00000C11700100861205080910000004911D49
05/11/2025,21:33:59,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE224481000019002A36010D007F005B9E4C00000E016401017C11D424070000010100B4771C36
05/11/2025,21:33:59,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C42A3601B4775A
05/11/2025,21:33:57,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019000491010D005B00FA944A00000C116F0100861205080910000004911D61
05/11/2025,21:33:56,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE224481000019002A36010D007B0049C34900000E016301017C11D424070000010100B4771C7F
05/11/2025,21:33:56,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C42A3601B4775A
05/11/2025,21:33:54,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019000491010D005E0090BA4700000C116E0100861205080910000004911D2C
05/11/2025,21:33:54,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00255075
05/11/2025,21:33:54,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C42A3601B4775AFE224481000019002A36010D007B007CE84600000E016201017C11D424070000010100B4771C6F
05/11/2025,21:33:53,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C874FB1AF72FFEFFF52E3C0429FE0B45C874FB1AF72FFEFFF52E3C022F
05/11/2025,21:33:52,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,21:33:51,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019000491010D005B004FE04400000C116D0100861205080910000004911DAC
05/11/2025,21:33:50,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE224481000019002A36010D007B00D50C4400000E016101017C11D424070000010100B4771C23
05/11/2025,21:33:50,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C42A3601B4775A
05/11/2025,21:33:48,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,21:33:47,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE224481000019002A36010D007B009A334100000E016001017C11D424070000010100B4771C57
05/11/2025,21:33:47,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C42A3601B4775A
05/11/2025,21:33:47,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C42A3601B4775A
05/11/2025,21:33:42,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,21:33:36,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,21:33:35,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: EF
05/11/2025,21:33:35,Debug,192.168.1.145,local0,zigbee-gw-stube,"ESP-TCP: Replacing connection in slot 0, closing connection from 192.168.1.10"
05/11/2025,21:33:35,Info,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Got connection from 192.168.1.10 (2 already connected)
05/11/2025,21:33:32,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,21:33:26,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00255075
05/11/2025,21:33:20,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00210120
05/11/2025,21:33:20,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE1C44810000050479470101001D0051FE2600000818080A000021BE13ECC91BD2
05/11/2025,21:33:20,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0745C4794702D8D7ECC990
05/11/2025,21:33:14,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00210120
05/11/2025,21:33:12,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,21:33:08,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00210120
05/11/2025,21:33:07,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: EF
05/11/2025,21:33:07,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Adding connection to slot 1
05/11/2025,21:33:07,Info,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Got connection from 192.168.1.10 (1 already connected)
05/11/2025,21:32:52,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,21:32:51,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C874FB1AF72FFEFFF52E3C022F
05/11/2025,21:32:32,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00255075
05/11/2025,21:32:32,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,21:32:26,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,21:32:20,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,21:32:14,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,21:32:13,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: EF
05/11/2025,21:32:13,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Adding connection to slot 0
05/11/2025,21:32:13,Info,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Got connection from 192.168.1.10 (0 already connected)
05/11/2025,21:32:12,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,21:31:52,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...

In this case, the iobroker.zigbee adapter is reporting:

2025-05-11 21:32:38.582  - error: zigbee.2 (16865) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

Where can I find this timeout? Can I increase this to like 30 seconds?

Thanks for any advice, let me know if there are more meaningful logs that I can provide to you.
@bjoernbusch
Copy link
Author

I had to give up, since the Family-Acceptance-Factor dropped to 0, since the lights were not working all the time.

I switched to a Sonoff ZBDongle-E on USB on a Raspberry Pi with Zigbee2MQTT and now everything is running smooth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bjoernbusch