How come you’re calm? My ZB regularly reports that the device is offline but it’s functional. It’s quite annoying, and I also use the regular offline state to restart the gateway and I can’t do it here because the restart would keep happening and wouldn’t solve anything.
Of course I’m not satisfied, I require full functionality and reliability. The house just calmed down because Sonoff messed it up and I had to run after customers. The problems persist and I don’t see them trying to fix it.
Since 10.03, all my devices (100+) have been offline. I’ve been on 1.18.3 for some time, and even though it was not super stable (some devices became offline for a few hours after restarting), it worked most of the time. Suddenly, all devices went offline (I can still control them via switches, however), and I cannot bring them up even after several restarts. Even after waiting for a few hours, the devices are not back on. What is even more, now the bridge reports an error if I try to add any Zigbee device, just after 5 seconds of “searching”. It also reports an error if I try to scan for Zigbee channels - it just looks like the Zigbee part of the bridge is down (I can access the bridge via app or web, but it still just refuses to work). I thought about forcing the bright to reinstall the latest firmware, but I have no idea if that’s possible, and if that would help. Now all automation in my house is dead 
Any ideas?
try to re pairing some devices and check if they keeps online
As I mentioned, the gate reports an error just after 5 seconds whenever I try to add a new device. So that won’t work. Also, repairing 100+ devices, most of which are hidden diy switches, would be a nightmare. Just because the gate was restarted… That’s the last option I’d try.
Just wondering, if there is any way to backup whole configuration from the bridge (including devices, scenes, preferences, etc) to a file or a cloud, perform the factory reset of the bridge and restore all settings from backup?
Not sure who to ping the best, so mentioning all staff I’ve found here 
@Minnie @Jemma @yi.liu
As I mentioned on 12. March, my ZBBridge-U (firmware 1.18.3) stopped working in very strange circumstances. I’ve noticed that all my Zigbee devices (over 100) went offline at once (not sure if in the same minute, but a quarter earlier, all scenes worked fine), and didn’t return online for an hour or so. So I restarted the bridge. It didn’t help. I restarted several times and even waited for a few hours - still without success. Then I tried adding a new device - after 5 seconds of “scanning” the error occurred (I’ve repeated that a few times - the same result). For an additional check, I’ve tried to scan Zigbee channels - same result - 5 seconds and error. The only option that worked was deleting an existing device. So I suspected that it may be a hardware failure - everything but Zigbee looked ok (i.e., I was able to connect to the bridge via eWeLink app and web page). I bought another ZBBridge-U, upgraded it to 1.18.3, and tried scanning Zigbee channels as well as adding new devices - everything worked fine. Then I’ve tried ” replacing” the old bridge with the new one via the option from eWeLink app. The transfer worked - everything was moved, but… every device remained offline. Now, the most strange thing: The Zigbee options in a new bridge stopped working - I was not able to add any device, nor scan the Zigbee channels. But the old bridge (after re-adding it to my network) was “healed” - it had no devices added, but I was able to add the new devices and scan the channels! I tried switching the “content” between the bridges, and the one that contained “the content” was “broken”, while the “empty” one was working fine. Therefore, I suspect that there’s an issue with the internal configuration.
My old bridge id is 100262c0cb and my new bridge id is 100297b7c7. Can anyone support me with that issue? Dozens of automations in my house just stopped working, and this is annoying… Now I’ve got 2 bridges, and neither of them works fine with my existing devices. Yes, I know I can re-add the devices, but for me that’s the last option - over half of 100 devices are inside the walls…
We sincerely apologize for the disruption this has caused. To help us resolve this issue effectively, we need to pinpoint the exact root cause. Could you please assist us by providing the following two critical pieces of information?
Gateway Device ID: You can find this in the Device Details page within the eWeLink App.
System Logs: In the eWeLink App, go to the Feedback section, select ZBBridge-U from the device list, and make sure to check the box for ‘Upload Running Logs’ (or ‘Include Logs’) before submitting.
zdá se, že se tu objevují dva problémy. odpojení zařízení a chybná identifikace stavu offline kdy systém hlásí, že zařízení je off-line ale stále funguje pohybové senzory detektory úniku vody. doufám, že se problém vyřeší a ne že se s příchodem nové generace mostu na problémy zapomene.
There seem to be two problems here. Device disconnection and incorrect offline status identification when the system reports that the device is offline but still works motion sensors water leak detectors. I hope that the problem will be solved and not that the problems will be forgotten with the arrival of the new generation of the bridge.
Moc sa im nedarí poslednú dobu.
Thank you for your feedback. We have a preliminary diagnosis regarding the situation you described. We will release a new version as soon as possible to fix the issue where some sub-devices show an abnormal offline status. Please stay tuned for updates on the -U Gateway. If you have any further questions, feel free to contact us.
Thanks for the prompt answer. As mentioned in the post, my old bridge id is 100262c0cb, and my new bridge id is 100297b7c7. I’ve sent the logs from the old bridge. Currently, all devices are synced with that bridge.
To clarify, the issue looks like every Zigbee feature of the bridge the devices are assigned to is broken: connecting to the device, adding a new device, and scanning channels.
I completely understand how you feel. I have checked the feedback you submitted via the backend, and our developers are currently pinpointing the issue. We sincerely apologize for the inconvenience caused and will resolve this as soon as possible. Thank you for your understanding!
updated - restarted. apart from the new features, I haven’t noticed any improvement in the zigbee status and offline status reports yet. I’ll wait 24 hours to see if the network stabilizes.
Hello, we’re very sorry for the unpleasant experience this has caused. Our developers are currently working on fixing this issue, and we’ve already made some initial progress. We will release a fix as soon as possible.
It seems that the problem with offline reporting has been solved, one motion sensor does not want to log in by itself and since they cannot get there now I cannot do it manually and the network situation has stabilized. It is just sad that at one address I am using a test ZBG-AB1-GL it is 1/3 of the price and covers about 50 M2 but without a single outage. It has limited capabilities but sometimes stability is more than capabilities. Sonoff gateways have been struggling with the ZigBee problem for a long time, some updates will worsen the situation, others will improve it. The question is then whether the problem is in the hardware or a pure software solution. For the ultra model I would appreciate the ability to display a network map before the local web interface.
Some issues have been fixed after the update. However, the problem of the motion sensor and buttons sometimes appearing offline persists.
I am glad to receive your message confirming that the offline reporting issue has been resolved. At the same time, I sincerely apologize for the inconveniences you mentioned.
-
Regarding the motion sensor’s inability to come online automatically: When convenient, please try manually re-pairing the device. If the issue persists, please retain the logs, upload them, and provide us with the Device ID. Our team will resolve this for you as soon as possible.
-
Concerning the request for a Zigbee device topology map: This is already on our internal backlog. Once we have finalized certain details, we will promptly announce the release schedule.
-
As you correctly noted, we attach great importance to this matter and are dedicated to making the connection between the -U hub and Zigbee sub-devices more stable. We are indeed continuously improving stability and device compatibility through software iterations.
Thank you all for your understanding and support!
Hello, we sincerely apologize that some devices are still experiencing offline issues.
Could you please provide the following information:
-
The specific model and Device ID of the affected device(s)?
-
Could you share the logs from the -U gateway with our technical team to help us pinpoint the issue?
Thank you for your understanding and support!
Quick info - upgrade to 1.19.0 did not help - all 100 devices still offline, even after few restarts… Any timeline when to expect more details about the cause, and the solution?