I am using the instructions from here https://www.digiblur.com/2020/07/how-to-use-sonoff-zigbee-bridge-with.html and when I type the socket://192.168.1.10:888 and set the port speed to 115200 as documented, it says “failed to connect”. The ZBBridge is up and running… I can log right into it… any suggestions?
Follow these instructions.
For Home Assistant (ZHA)
This mode creates a TCP bridge from the zigbee module to Home Assistant. In this case Tasmota is only relaying all the messages from the zigbee module to ZHA and you cannot use any Zigbee commands in Tasmota console in this mode. All setup needs to be done from Home Assistant ZHA integratioon.
After Zigbee firmware is flashed and confirmed working in ZIgbee2Tasmota mode, apply the template:
{"NAME":"ZHA ZBBridge","GPIO":[56,208,0,209,59,58,0,0,0,0,0,0,17],"FLAG":0,"BASE":18}
Copy
Create a rule in Tasmota to start TCPBridge on boot:
Rule1 ON System#Boot do TCPStart 8888 endon
Copy
You can change
8888to a port you prefer.
Enable rule with Rule1 1 and restart ZbBridge.
It sounds to me like you haven’t?
I have a similar issue after migrating hassio to new hardware. Everything was restored from the backup except the bridge. The setup fails with the message “Failed to connect”. I have checked and verified that the TCP port is up and waiting for the connection
There is a bug. If the Sonoff ZBBridge has been disconnected from power, it does not start the Zigbee Radio.
Solution is to set the bridge in Tasmota back to the Sonoff ZbBridge template
{"NAME":"Sonoff ZbBridge","GPIO":[56,165,0,166,215,0,0,0,6,158,5,0,17],"FLAG":0,"BASE":75}
, and then back to
{"NAME":"ZHA ZBBridge","GPIO":[56,208,0,209,59,58,0,0,0,0,0,0,17],"FLAG":0,"BASE":18}
and restart the rule.
2 Likes
no luck
I have a bit the same problem.
Failed to connect, however in the console of tasmota I can see:
16:51:13.025 TCP: Got connection from 192.168.1.55
16:51:14.992 TCP: Got connection from 192.168.1.55
16:54:18.751 TCP: Got connection from 192.168.1.55
16:54:20.387 TCP: Got connection from 192.168.1.55
This is while inputting integration.
I am starting to think Home Assistant is causing some kind of problem since it worked in the past. Tried, resetting the hub, reflashing, …
1 Like
I also had issues with it. I tried to reconfigure it again. No success. I gave up and reinstalled a 2531 and it works flawlessly. Not going back I think
I have a similar problem. After about 14days of testing with 4 devices, I have connected in a total of 19 devices and it stopped working. Now I have last seen on all devices from the moment it worked, and on the coordinator, the last seen increases slowly from time to time.
I tried all above mentioned with no luck.
The ZHA is able to connect to Sonoff, re-adding ZHA is not helping. Switching to module 75, I see previously paired devices communicating, switching back to 0 ZHA sees nothing.
I’m starting to suspect corrupted zigbee.db.
1 Like
Did you get this working OK? I’m having the same issue, having applied the template correctly and verifying it through the tasmota web interface.
I’m able to connect using telnet to the device on port 8888 over the network. I also see a connection on the tasmota console from the correct home assistant source IP address. Yet, I constantly get the failed to connect message in HASS when trying to connect to the socket, using baud 115200.
I thought moving away from a finicky cc2531, and a more expensive one, to a sonoff bridge would be more reliable. This is my third attempt and getting a stable zigbee setup, but this is proving to be a huge pain in the butt too.
I went back to an older Tasmota version (8.5.1) and it worked with this one
1 Like
It was corrupted zigbee.db in my case. I have deleted it and re-added all the devices.
It is working for about a month now.
1 Like
I have same issue
03:27:12.191 TCP: Got connection from 192.168.0.36
03:27:12.192 TCP: to MCU/1: 1AC038BC7E
03:27:14.111 TCP: Got connection from 192.168.0.36
03:27:14.113 TCP: to MCU/1: 1AC038BC7E
did anyone get it works ?
Hi all,
I’ve followed the wiki here: Sonoff Zigbee Bridge (ZBBridge) Zigbee compatibility, but no luck:
10:37:00.142 CMD: Grp 0, Cmnd ‘TCPSTART’, Idx 1, Len 4, Data ‘8888’
10:37:00.146 RSL: RESULT = {“Command”:“Unknown”}
Step I took:
- Tasmotizer: tasmota-zbbridge.bin → ok
- Wifi settings → ok
- Firmware upgrade " ncp-uart-nsw_6.7.9_115200.ota "–> ok?!
- Template: {“NAME”:“ZHA ZBBridge”,“GPIO”:[56,208,0,209,59,58,0,0,0,0,0,0,17],“FLAG”:0,“BASE”:18}
- Rule1 ON System#Boot do TCPStart 8888 endon
But now I have luck with TCPSTART on 8888…
Could someone please guide me what to do?
Thank you so much!
I am having this same console output from this issue. ZHA says “Failed to connect” when the console outputs this. ZHA can see socket://IPADDRESS:8888 but I have no idea what’s failing.
Is it just that something is outdated and no longer works? All the guides show two options in ZHA settings when there’s been a third for a while now (data flow control). Toggling this between both options makes no difference.
I have absolutely no idea what direction to take next but I can’t get my Sonoff Bridge working with ZHA
Double check you have followed everything as in this guide here.
Try uninstalling/reinstalling ZHA, even unplug the device and restart HA. No issues and working fine here.
I’ve followed it to the tee. Re-flashed with the firmware, tried various versions of the firmware, restarted HA, the bridge multiple times.
As far as I can tell, the sonoff bridge was flashed fine. I got the success message, I can modify it and reach it via the web UI. ZHA reaches it fine, as shown in the console. But I get the same messages in the console as above (with my own unique IP address)…
03:27:12.191 TCP: Got connection from 192.168.0.36
03:27:12.192 TCP: to MCU/1: 1AC038BC7E
03:27:14.111 TCP: Got connection from 192.168.0.36
03:27:14.113 TCP: to MCU/1: 1AC038BC7E
With ZHA not completing its installation/configuration, saying “Failed to connect”.
I’m running HA inside a docker container and connecting to a sonoff bridge over wifi. I was initially wondering if the bridge was having difficulty accessing HA, as it’s inside a container, but it should reach it fine as it’s accessible via its mapped port, as a standard HA installation would be.
Hi I have the same problem with :
### ZHA ZBBridge
## Tasmota
|Program Version|11.0.0(tasmota)|
| --- | --- |
|Build Date & Time|2022-02-12T14:13:50|
|Core/SDK Version|2_7_4_9/2.2.2-dev(38a443e)|
|Uptime|0T00:03:04|
|Flash write Count|52 at 0xF5000|
|Boot Count|22|
|Restart Reason|Software/System restart|
|||
|AP1 SSId (RSSI)|vegetaux (82%, -59 dBm) 11n|
|Hostname|Zigbee-bridge-tasmota|
|MAC Address|98:F4:AB:E3:6B:12|
|IP Address (wifi)|192.168.1.64|
|Gateway|192.168.1.1|
|Subnet Mask|255.255.255.0|
|DNS Server1|192.168.1.1|
|DNS Server2|0.0.0.0|
|||
|HTTP API|Enabled|
|||
|MQTT Host||
|MQTT Port|1883|
|MQTT User|DVES_USER|
|MQTT Client|DVES_E36B12|
|MQTT Topic|tasmota_%06X|
|MQTT Group Topic 1|cmnd/tasmotas/|
|MQTT Full Topic|cmnd/tasmota_E36B12/|
|MQTT Fallback Topic|cmnd/DVES_E36B12_fb/|
|MQTT No Retain|Disabled|
|||
|Emulation|None|
|||
|ESP Chip Id|14904082 (ESP8266EX)|
|Flash Chip Id|0x1540A1|
|Flash Size|2048 kB|
|Program Flash Size|1024 kB|
|Program Size|620 kB|
|Free Program Space|380 kB|
|Free Memory|27.1 kB|
[Tasmota 11.0.0 by Theo Arends](https://bit.ly/tasmota)
- ncp-uart-nsw_6.7.9_115200.ota
I have this message in the console :
23:39:17.092 RUL: SYSTEM#BOOT performs "TCPStart 8888"
23:39:17.093 SRC: Rule
23:39:17.094 CMD: Grp 0, Cmnd 'TCPSTART', Idx 1, Len 4, Data '8888'
23:39:17.098 RSL: RESULT = {"Command":"Unknown"}
I’m trying to figure out if there’s an localised configuration I have that’s interfering. ZHA can see the Sonoff Bridge fine. I can’t get beyond “Failed to connect” in the ZHA configuration and don’t believe it produces logs until after this step. So I’m only seeing the Bridges own console logs, as I showed above.
I use PiHole and disabled this with no difference. I also have a firewall in routeros on a mikrotik. The fact ZHA reaches the bridge fine via port 8888 suggests this isn’t an issue. I can’t think of any other rules to enable or disable so I’m assuming I can isolate this issue to being confined to either the Sonoff or HA (running in docker on a rpi4).
same problem here after upgrading HA AND tasmota
Solution is to set the bridge in Tasmota back to the Sonoff ZbBridge template
I followed your suggestion and after applying the first template, the damn thing won’t even turn on. LEd is blinking, yet I see no AP to start from 0.
.
Downgraded to firmware 8.5.1 and getting the same
22:16:29 RUL: SYSTEM#BOOT performs "TCPStart 8888"
22:16:29 RSL: stat/tasmota_E2FA34/RESULT = {"Command":"Unknown"}