-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Sonoff ZbBridgePro - connectivity issues with iobroker.zigbee #23407
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.
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
Comments
Another disconnect just now, connection recovered by itself. iobroker.zigbee: 2025-05-11 11:01:22.487 - info: zigbee.2 (27602) Failed to ping 0x000b57fffeeb86a5 TRADFRI bulb E14 WS opal 400lm
2025-05-11 11:01:33.344 - info: zigbee.2 (27602) Failed to ping 0x3c2ef5fffe2ff71a TRADFRI Driver 10W
2025-05-11 11:07:29.951 - error: zigbee.2 (27602) Adapter disconnected, stopping
2025-05-11 11:07:40.028 - info: zigbee.2 (27602) Try to reconnect.
2025-05-11 11:07:40.029 - info: zigbee.2 (27602) Starting Adapter npm ...
2025-05-11 11:07:40.035 - info: zigbee.2 (27602) Installed Version: iobroker.zigbee@3.0.1 (Converters 23.13.0 Herdsman 3.3.2)
2025-05-11 11:07:40.036 - info: zigbee.2 (27602) Starting Zigbee-Herdsman
2025-05-11 11:07:42.890 - info: zigbee.2 (27602) Zigbee-Herdsman started successfully with Coordinator firmware version: zStack3x0 : 20220219 (2-1.2.7.1)
2025-05-11 11:07:42.892 - info: zigbee.2 (27602) Unable to disable LED, unsupported function.
2025-05-11 11:07:42.899 - info: zigbee.2 (27602) 0x00158d0007e20d64 (addr 17060): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
2025-05-11 11:07:42.905 - info: zigbee.2 (27602) 0x70ac08fffeb52197 (addr 21241): LED1934G3 - IKEA TRADFRI bulb E26/E27, warm white, globe, clear, 250 lm (Router)
2025-05-11 11:07:42.911 - info: zigbee.2 (27602) 0x28dba7fffe86c5bc (addr 21460): LED2102G3 - IKEA TRADFRI bulb E26/E27, warm white, globe, clear, 440/450/470 lm (Router)
2025-05-11 11:07:42.916 - info: zigbee.2 (27602) 0xdc8e95fffe57ee3b (addr 48035): LED1934G3 - IKEA TRADFRI bulb E26/E27, warm white, globe, clear, 250 lm (Router)
2025-05-11 11:07:42.921 - info: zigbee.2 (27602) 0x000b57fffeeb86a5 (addr 55256): LED1536G5 - IKEA TRADFRI bulb E12/E14, white spectrum, globe, opal, 400 lm (Router) Sonoff ZbBridge Pro: 05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE03611C0001552A
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE04211C6000000059
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE026113010071
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE022113600050
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE1A611C00180001030507090B0D0F00020406080A0C0DE501005ADB23003A
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE04211C82000000BB
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE026113180068
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE0221138200B2
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0A610202010207013B89340100E9
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210223
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE02610159063D
05/11/2025,11:07:41,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,11:07:40,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: EF
05/11/2025,11:07:40,Info,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Got connection from 192.168.1.10
05/11/2025,11:07:24,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,11:07:23,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: IPv6 Global fd7a:3b05:998e:cafe:ea6b:eaff:fef2:ae68
05/11/2025,11:07:23,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: IPv6 Global 2a01:8b81:4800:4100:ea6b:eaff:fef2:ae68
05/11/2025,11:07:22,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: IPv6 Local fe80::ea6b:eaff:fef2:ae68%st6
05/11/2025,11:07:22,Debug,192.168.1.145,local0,zigbee-gw-stube,"ESP-WIF: IPv4 192.168.1.145, mask 255.255.255.0, gateway 192.168.1.1"
05/11/2025,11:07:14,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE1C44810000050479470101006D00BDAED500000818940A000021E925A3BB192F
05/11/2025,11:07:14,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C4794704D8D7137374FBA3BB48
05/11/2025,11:07:04,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection... RaspberryPi May 11 11:07:29 homepi bash[630]: [2025-05-11T09:07:29.947Z] zh:zstack:znp: Socket error Error: read ECONNRESET |
And another disconnect, this time iobroker.zigbee can't establish the connection again, even when restarting the adapter. 05/11/2025,15:18:07,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:18:02,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C874FB1AF72FFEFFF52E3C022F
05/11/2025,15:17:56,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE1C44810000050479470101007B0047CC9E00000818620A0000219714A3BB1953
05/11/2025,15:17:56,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C4794704D8D7137374FBA3BB48
05/11/2025,15:17:50,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE1C448100000504404B01010062005DA59800000818240A000021190ED4531C42FE25448100000304404B010100620014A79800001118250A000029BF03140028FF1000297825D4531C2A
05/11/2025,15:17:50,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C4404B01D45309FE0545C4404B01D45309FE0545C4404B01D45309FE1C448100000204404B0101005B00D6A39800000818230A000029990AD4531C7A
05/11/2025,15:17:47,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:17:27,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:17:17,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00255075
05/11/2025,15:17:11,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,15:17:07,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:17:05,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,15:17:02,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C874FB1AF72FFEFFF52E3C062BFE0B45C874FB1AF72FFEFFF52E3C022F
05/11/2025,15:17:01,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C874FB1AF72FFEFFF52E3C072A
05/11/2025,15:16:59,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,15:16:58,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: EF
05/11/2025,15:16:58,Info,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Got connection from 192.168.1.10
05/11/2025,15:16:47,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:16:27,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:16:21,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00255075
05/11/2025,15:16:15,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00210120
05/11/2025,15:16:09,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00210120
05/11/2025,15:16:07,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:16:03,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: FE00210120
05/11/2025,15:16:02,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/2: EF
05/11/2025,15:16:02,Info,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Got connection from 192.168.1.10
05/11/2025,15:16:00,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C874FB1AF72FFEFFF52E3C022F
05/11/2025,15:15:47,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE404481000000007F94010100910021972300002C18B40A01FF42250121D10B0421A8430521C6C2062401000000006429B7086521DE10662B1D7701000A2100007F941DCD
05/11/2025,15:15:47,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:15:39,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-HTP: Console
05/11/2025,15:15:38,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-HTP: Tools
05/11/2025,15:15:36,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-HTP: Main Menu
05/11/2025,15:15:33,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019001FE8010D005B009BA61500000C1175010086120A2004100000EA7D1C3C
05/11/2025,15:15:32,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C41FE801EA7DE5
05/11/2025,15:15:30,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019001FE8010D006200EECD1200000C1174010086120A2004100000EA7D1C1D
05/11/2025,15:15:29,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C41FE801EA7DE5
05/11/2025,15:15:28,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00255075
05/11/2025,15:15:27,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:15:27,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019001FE8010D005B00ADF40F00000C1173010086120A2004100000EA7D1C44
05/11/2025,15:15:27,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C41FE801EA7DE5
05/11/2025,15:15:24,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019001FE8010D005E00FB1F0D00000C1172010086120A2004100000EA7D1CFF
05/11/2025,15:15:24,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C41FE801EA7DE5
05/11/2025,15:15:22,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,15:15:21,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE204481000019001FE8010D00620029430A00000C1171010086120A2004100000EA7D1C49
05/11/2025,15:15:21,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C41FE801EA7DE5
05/11/2025,15:15:19,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C41FE801EA7DE5
05/11/2025,15:15:16,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,15:15:10,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: FE00210120
05/11/2025,15:15:08,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: to MCU/1: EF
05/11/2025,15:15:08,Info,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: Got connection from 192.168.1.10
05/11/2025,15:15:07,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-WIF: Checking connection...
05/11/2025,15:14:59,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0B45C874FB1AF72FFEFFF52E3C022F
05/11/2025,15:14:55,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE224481000019002A36010D00740080EFE100000E013501017C11D424070000010100B4771C6B
05/11/2025,15:14:55,Debug,192.168.1.145,local0,zigbee-gw-stube,ESP-TCP: from MCU: FE0545C42A3601B4775A |
From you last log I see that your gateway connected 3 times to Tasmota, which seems wrong. However the logs contain both What would be useful is to have a Wireshark capture to understand which end closes the TCP connection. I will also add some logging when a previous connection is closed, and how many active connections are in place |
Please try again with the latest version from the development branch. tcp bridge has more logging. |
Thanks, installed the latest build 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... The debug logs of iobroker.zigbee only show a timeout
Is it a timing issue? |
I see really nothing wrong on the TCP side. The 3rd TCP connection is received while 2 other TCP are still alive. It could be indeed a timeout on the broker side that considers that the connection is lost, although the TCP connection is still alive and valid. |
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. |
PROBLEM DESCRIPTION
In short, the iobroker.zigbee adapter looses connection to the gateway ~once a day or several times. I have been having this issue for longer now, tried various different things and now I'm running out of ideas, so I would appreciate any further ideas.
Long story: I have a Sonoff ZbBridge Pro, which was initially flashed via serial with the manual on notenoughtech. Subsequent FW updates were performed via the webinterface and currently it's using 14.6.0.1. I have applied the TCP template, since I want to integrate it into iobroker. I could successfully integrate it, change all the network parameters and learn 25 devices of different vendors. The connection to the actual zigbee devices looks stable to me, they don't disappear, signal strength is ok. The Sonoff ZbBridge Pro is connected via Wifi to the Router, which is like 1.5m away. The router is a Fritzbox, there are repeaters in the network. I have followed the above mentioned FAQ to assign a less crowded, fixed wifi channel and also assigned a static IP on the bridge (I also tried assigning static DNS servers, but they were gone after a reboot, might be a different issue). Performed
Reset 3
with power cycle. Removing the repeaters is difficult, since the issue is not manually reproducible, I would have to wait for ~24 hours. The iobroker.zigbee is running on a RaspberryPi4, which is connected via ethernet to a switch and then to the router, where also the Sonoff ZbBridge Pro is connected.The problem then occurs at any time during the day that the iobroker.zigbee adapter reports connection loss. Sometimes it recovers by itself, sometimes it can't. Then I try rebooting the bridge, if that doesn't help the iobroker, if that doesn't help I unplug the bridge. If that doesn't help, I wait for like 3 hours and try the whole procedure again and eventually the connection can be established again.
In the Tasmota logs, it looks to me like there is something with the Wifi connection, but there are no errors or explicit disconnects. During the time that the iobroker.zigbee can't properly connect, I can properly reach it via the webinterface and I also see that the intial connect is reaching the Sonoff ZbBridge Pro.
When it lost connection yesterday, I now captured all the logs and I would appreciate advice what else to try. (The assumption that I f*** up somewhere and didn't properly read the manual is well possible). It looks a little like this disucssion, but the final issue points to ZHA, which is not involved here.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log. I don't have weblog available, since it's not manually reproducible, but I have syslog configured. The connection was lost at 7:31:41. Logs from iobroker and RaspberryPi further down.TO REPRODUCE
Steps to reproduce the behavior:
None, it occurs randomly.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
Connection should be stable
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
No screenshots
ADDITIONAL CONTEXT
Add any other context about the problem here.
Here are the logs from the iobroker.zigbee adapter from the same time:
Here are the logs from the RaspberryPi from the same time:
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: