Anyone else having issues with Zigbee Sonoff Zigbee Bridge not able to connect?

Configuration Zigbee
21

This appeared to be a Tasmota firmware issue. I upgraded it today using the online OTA upgrade and repeated exactly the same steps as before. It worked.

For what it’s worth (and this is just observational and not coming from any expertise. It may just be that I’m naive about what changed) the fix contradicted much of the advice that already exists. Downloading the two main firmware versions in the guides didn’t work. It was only when trying to use the firmware directly from the tasmota site via the OTA upgrade option, that I got it to work with ZHA.

Secondly, it still refused to work with Zigbee2mqtt. Herdsman (in the logs) would say it couldn’t open a socket. Guides say you need to use module 75 for z2m but I got it working when I switched back to module 0, intended for ZHA. I don’t understand why, but it works like a charm now in both ZHA and z2m.

22

This may help others out but I accidently did the normal Over the Air Firmware upgrade of Tasmota which broke mine. The log would attempt to start TCPStart on port 8888 but an “unknown” error would come back.
My fix was to run the following command to reflash it with the correct OTA firmware:

Console Command to set new OTA path:
otaurl http://ota.tasmota.com/tasmota/tasmota-zbbridge.bin.gz

Then In the firmware menu, I ran the OTA. The process seems to do a minimal firmware install first up, so give it a couple of minues to do its thing. Check your console and hopefully that TCPstart has launched now that the command is actually in the firmware.

Good luck

2 Likes
23

I had a similar experience. Downloaded updates always failed with invalid signature. I added the ota URL and the upgrade went as expected.

However, I still cannot pair to HA.

image
image978×1094 36.2 KB

After 10 seconds I get this:
image
image886×734 26.3 KB

the tasmota console does log the connection request:

02:27:33.786 TCP: Got connection from 192.168.1.4

And on start, the logs look healthy:

02:29:29.266 TCP: Starting TCP server on port 8888
02:29:29.267 RSL: RESULT = {"TCPStart":"Done"}
24

Did you find a soltion? I have the same issue

1 Like
25

I did not. I bought a Sonoff zigbee stick.

26

off the top of my head

theres 2 profiles zbbridge (0) ans zbbridge(75)

need to switch to 75 to make changes in the console and back to 0 to allow zha to connect

this was a while ago though but happy to share my config if it helps anyone

1 Like
27

Hello Guys,

I have spent several days to solve it. Just check in Configure template - Name “Sonoff zigbee Pro” if you have GPIO 19 set to TCP TX and GPIO 23 to TCP RX and run the command in a console
backlog rule1 on system#boot do TCPStart 8888 endon ; rule1 1 ; template {"NAME":"Sonoff Zigbee Pro","GPIO":[0,0,576,0,480,0,0,0,0,1,1,5792,0,0,0,5472,0,320,5793,5504,0,640,608,32,0,0,0,0,0,1,0,0,0,0,0,0],"FLAG":0,"BASE":1} ; module

1 Like
28

Hello together,

never ending story?

Also I have the same issue with my Sonoff Bridge Pro and ZHA. After I had problems with Zigbee2MQTT (Home Assistant has often lose the connection), Because of that I have decided to try ZHA. I have exactly the same situation as @uSlackr
Is it really the only one solution to buy other (USB) Bridge?

29

Hi, same issue. Did you solve? Thanks

30

I have tried to mitigate the issue using:

Rule1 ON System#Boot DO Backlog Module {“NAME”:“Sonoff ZbBridge”,“GPIO”:[56,165,0,166,215,0,0,0,6,158,5,0,17],“FLAG”:0,“BASE”:75}; Rule2 1; Rule1 0 ENDON

Rule2 ON System#Start DO Backlog Module {“NAME”:“ZHA ZBBridge”,“GPIO”:[56,208,0,209,59,58,0,0,0,0,0,0,17],“FLAG”:0,“BASE”:18}; TCPStart 8888; Rule1 1; Rule2 0; Restart 1 ENDON

Rule1 1

Rule2 1

I gave the bridge a power off and power on and seems that the web server was started.

31

Probably to late now, but I found a solution for my Sonoff Zigbee Bridge (not the pro version). After two days of trying all new versions of software and even a new Bridge, I went back to what digiblur did (How to use the Sonoff Zigbee Bridge with Home Assistant - Tasmota | digiblurDIY) and used the same ota file, nl ncp-uart-sw_6.7.6_115200.ota to uupgrade the firmware, and it worked seamlessly.