This week, Tasmota 9.3.1 was released and I updated the Sonoff Zigbee Bridge from Tasmota 9.3.0 to 9.3.1. I’m running the Zigbee Bridge with the ZHA integration.
Within a day of updating, devices started dropping off the Zigbee network, including both of the IKEA TRADFRI repeaters, which then caused multiple other devices to drop-off the network!
Back on Feb.11, I updated the HA Supervisor to 2021.02.11 and I saw no Zigbee device drop-offs until I updated the Sonoff ZbBridge to Tasmota zbbridge 9.3.1.
I have since rolled the Sonoff ZbBridge back to Tasmota 9.3.0.
I’ll keep watching the behavior.
I wonder if anyone else has noticed Zigbee device drop-offs after update to zbbridge Tasmota 9.3.1?
Update: even after rolling back the Tasmota version to 9.3.0, the device disconnections continue.
I guess I have to conclude that this instability isn’t the fault of the Tasmota firmware version.
Maybe some recent change to HA core or the HA supervisor has made the Zigbee system less stable…maybe changes in zigpy or bellows?
The HA logs show daily trouble with bellows…
CRC error in frame b’26aced5f7a7e’ (b’5f7a’ != b’8c6a’)
11:14:59 AM – /usr/local/lib/python3.8/site-packages/bellows/uart.py (ERROR) - message first occurred at March 5, 2021, 12:01:13 PM and shows up 2 times
NCP entered failed state. Requesting APP controller restart
10:08:57 AM – /usr/local/lib/python3.8/site-packages/bellows/ezsp/init.py (ERROR) - message first occurred at March 4, 2021, 2:10:52 PM and shows up 40 times
Error doing job: Task was destroyed but it is pending!
2:59:20 AM – runner.py (ERROR) - message first occurred at March 4, 2021, 11:58:17 PM and shows up 12 times
Lost serial connection: read failed: [Errno 104] Connection reset by peer
March 5, 2021, 11:17:47 PM – /usr/local/lib/python3.8/site-packages/bellows/uart.py (ERROR) - message first occurred at March 4, 2021, 2:40:12 PM and shows up 7 times
Watchdog heartbeat timeout:
March 5, 2021, 11:17:44 PM – /usr/local/lib/python3.8/site-packages/bellows/zigbee/application.py (WARNING) - message first occurred at March 5, 2021, 9:12:45 PM and shows up 2 times
Over the last 2 weeks, the IKEA TRADFRI Zigbee repeaters have been the devices that drop out of the Zigbee network. Then, all contact with their paired devices is lost. Simply re-pairing the TRADFRI repeaters with the Sonoff Zigbee Bridge brings all the devices back, but we should not have to intervene once a week!
same problem here with 9.3.1, but after upgrading to 9.3.1.1 it works. some sensors have to be re-paired. shall I wait for the upcoming update and then pair them?
craciunbogdan.mbogdanx
some sensors have to be re-paired. shall I wait for the upcoming update and then pair them?
I’d re-pair them now. I don’t think waiting for a future firmware fix is realistic.
Unfortunately, you’re going to be re-pairing them several times per month or week.
From what I’m reading, Zigbee devices come unpaired because data packets get lost or missed in the wifi-to-zigbee link, inside the Sonoff Zigbee Bridge. It sounds like a fundamental architecture flaw, which could mean it’s not fixable without a new version of the Sonoff Zigbee Bridge hardware.
Note the warning in the brown box on this page:
This week, I removed the Sonoff Zigbee Bridge and moved on to using a CC2531 USB stick coordinator. Thus far there have been zero instances of Zigbee devices coming unpaired.
I’m still running the 8.5.1 from when i first flashed it, been 100% rock solid from day 1, loads better than the cc2531 I was using. What are you hoping to gain from updating?
@ Bobby_Nobble
I’m running ZHA.
I was updating Tasmota firmware because something connected with the Sonoff Zigbee Bridge is broken. My hope was that the broken behavior would be fixed in “the next version”.
After nearly 6 months of it not working properly, I’ve ditched the Sonoff Zigbee Bridge.
I’ve been running for a week with a CC2531 USB coordinator and its been solid - no Zigbee devices becoming un-paired, etc. I have no regrets from switching.
@Bobby_Nobble I started with Tasmota zbridge 8.5.1 on October 2, 2020.
I was already seeing Sonoff temperature sensors stop communicating with the Zibgee Bridge, so the system was already broken with 8.5.1. Since the system was already broken, there wasn’t a reason to stay with the 8.5.1 firmware, and updating to 9.x.x firmware offered the possibility of a fix.
The Tasmota 9.x.x firmware updates had bug fixes and feature additions,
see Tasmota/CHANGELOG.md at c2f8730b1e2d93f3d78aa877014dd482b49ca5c9 · arendst/Tasmota · GitHub
so I updated to see if it would fix the Zigbee device disconnection problem.
The disconnection problems persisted.
For 2 months, I did a lot of Zigbee research and experiments (such as changing my wifi to a channel on the other end of the spectrum) to try and fix the disconnection problem. In early December, I saw forum posts that other people were experiencing the same disconnections. It wasn’t just my system.
Further reading led me to the realization that there could be no fix from Tasmota firmware, because the Sonoff Zigbee Bridge hardware had a architecture shortcoming.
Since changing to a CC2531 USB coordinator, the ZHA system has become stable, and no Zigbee devices have disconnected from the network.
Feel free to elaborate with an explanation of how the wifi could be the problem, and be specific with the relevant aspects.
Keep in mind, others are having problems with Zigbee devices disconnecting from the Sonoff Zigbee Bridge.
Does everyone have a wifi problem?
I doubt it.
I could, but first you elaborate with an explanation of how you came to the conclusion that the Sonoff Zigbee Bridge hardware has a architecture shortcoming
I’ve made a conclusion, on the basis of evidence, not an accusation.
If you read the previous posts in this thread, you can see the steps in the process of elimination.
A major piece of evidence is the greenish brown warning box on this page.
I’m done 