After the update of my Bridge Ultra to version 2.2.0 it starts behaving weird.
A lot of sensor events (movement sensor, door sensor…) don’t trigger the scene.
My 3 channel switches are completely broken: if I try to turn on light 3, the channel 2 is triggered, if I try to turn on light 2, the channel 1 is triggered, if I try to turn on light 1 an error message appears.
All of this after latest update.
Is there a way to downgrade to the previous version of Bridge Ultra?
Have you checked the status of your network—whether the signal is good or if there is a lot of interference?
All worked perfectly before the update.
After the update a few sensor did not trigger the scene and the 3 channels switch are completely broken.
Cannot be a coincidence
My question is really just to be safe!
Because I have one running the latest version with over 150 devices, and everything is fine!
Have you tried unpairing one and pairing it again to see if that fixes the issue?
Because when sensors don’t respond—and so on—it’s often a signal problem!
And it really could just be a coincidence!
Since, in your case, it seems to be a widespread issue affecting everything!
Yes, I had to remove and re-pair the 3 channel switches because otherwise I couldn’t turn on the lights via automation. It solved the problem tho, but even if there is an interference (that wasn’t present 2 days ago) how can be the cause of completely break the 3 channel switch? Let me be clear what happened after the update
Channel 1 → light 1
Channel 2 → light 2
Channel 3 ->> light 3
When I activate light 3 via automation the actual light 2 is on
When I activate light 2 via automation the actual light 1 is on
When I activate light 1 via automation an error about “it’s not responding” appears
That’s purely indexing problem of the firmware.
This version contains some bug, no doubt abou it
I understand. I also gather that the Zigbee device isn’t a Sonoff product—it must be a supported third-party device. That support could have broken for any number of reasons. I recommend submitting feedback via the app or the hub’s web interface with more details so it can be fixed in the next version. Updates can often break third-party products—like those from Tuya, for example.
In a test environment, I experienced similar issues with some Zemismart devices (which are Tuya-based), using both ZHA and Z2M in Home Assistant.
Hello, we sincerely apologize for the inconvenience you have experienced. Thank you for your feedback. To help our technical team investigate the issue more accurately, we would like to ask you to provide the following information:
The device model(s) and device ID(s) of the devices that are not triggering scenes (e.g., 3‑channel switches, motion sensors, door sensors, etc.).
The trigger conditions and actions of the automation scenes configured for the channel switch in question, along with a screenshot of any error message that appears.
In the meantime, please submit the logs via the eWeLink App: go to “Me” → “Feedback”, select the corresponding ZBBridge‑U device, and make sure to check the “Upload logs” option. Our technical team will review the system logs to further investigate the issue. Thank you for your cooperation and support!