earlier today upon updating a ZBBridgePro from firmware 3.0.0 to 3.1.0 all the zibgee devices went offline…In all there are about 50 devices, 10 of which are mains-powered routers and the rest being children, access has been lost to all except a S26ZB socket that appears online but it’s function is not guaranteed as it sometimes times-out without registering the operation.
In the weeks / months prior to the update there was no apparent issue to report with strong signal on all the children (every sigle one stronger than -69dB) and good mesh performance.
Tried power cycling a few times to no avail., currently waiting for mesh to “self-heal” but I’m not realy hopeful since it’s been a few hours and no nodes appear to connect in the meantime.
[update_1] upon further investigation and despite the nodes in the eWelink app and the webapp showing as offline the HA integration began polling info from temp / motion and presence sensors as soon as there was a change in their status…so it appears that some of the functionality is still there, albeit not showing in the app…Some binary switches also work, most automations don’t…it’s all currently a mess, in await of further developments, will report back. FYI internet access is solid, no changes to backbone / fiber..
So that I can get a dobolenka because if my customers update zbbp they will all call me. I don’t know what’s going on but lately every update is a disaster.
[update_2] the bridge behaves erratically to say the least upon updating to 3.1.0. The app and webUI both don’t update the routers / children any more and the HA integration also appears to have trouble polling data from time to time whereby all the displayed zigbee devices become unavailable and reconnect a few minutes later…This behaviour has a time period of around 8-12 hours…Raised a ticket with support, they claim that it’s my network and the distance between the devices to blame, which makes NO SENSE whatsoever seeing that the webUI / app can’t even poll ANY values upon update…Asked for a downgrade option which I can’t see being available in which case I’m left with no other option but to either wait it out until a new firmware is pushed or i find some other remedy in the meantime…
Another thing of particular importance is that I added a few extra new switches to the bridge which were happily added per the usual procedure, however upon rebooting the bridge a few hours later these ALSO are now inaccessible…irony being that these are located in the very near vicinity to the ZBBridge-P….
[update_3] In an effort to troubleshoot further i re-paired a handful (about 10) of the existing sensors and routers to the bridge. In the process none of the IDs changed - which i found quite interesting tbh, since in the past when a sensor would become unavailable within both the eWelink app and the HA integration chances were ~20-30% that deleting it and repairing would change it’s ID..All was looking normal, fixed the scenes once again with the ones paired to the sensors brought back online within eWelink working as usual…UNTIL i rebooted the bridge once again at which point it all reverted back to all of the sensors being OFFLINE (despite when accessing each one’s details the RSSI signal reporting as usual), scenes dead once again and so on and so forth…
So it yet again becomes obvious that something’s cooked on eWelink’s front and have since begun migrating everything to HA, automations and all…
I’m afraid I’ve had it with SONOFFs..this is probably the last nail to the coffin and while at some point in time being fantastic value for the offering I’m afraid based on the latest developments I can’t recommend these items to friends and colleagues anymore..
Truth be told i never had major issues with Sonoff’s / eWelink’s integration…but this current state of affairs leaves much to be desired….and to add insult to injury Alexa has access to all of the sensors that appear offline within the eWelink app..I suppose there’s no issue with my setup and something indeed broke in firmware 3.1.0 that rendered most of the devices mute towards speaking with the eWelink servers…
I’d come as a big surprise if the next firmware update nerfs the Alexa integration, too…m’ just saying
I hear you… If you search the forum for even the last three months, you’ll find at least a few threads with ZBBridge-P and various problems. I’ve also had a problem for a while now, but it’s supposedly unsolvable.
Others have also had problems with offline sensors. I experienced this myself, and powering off/on, a hard power outage for a few seconds, helped.
Your issue, as you describe, must be firmware-related… I still don’t see 3.1.0, which could mean one of two things: slow cloud propagation per region, or they’ve removed this firmware because it does indeed contain the critical bugs you describe.
This is a harsh lesson for the future: never update too quickly. Wait a month or more, hoping that bugs will be noticed and fixed. But knowing Sonoff/ewelink, I have serious doubts… they treat us like beta testers, typical behavior for companies not to spend too much money.
I’m afraid this doesn’t resolve my situation as I have already gone down that path, re-paired about a dozen of my offline devices, re-set all the automations and scenes only to find out that upon rebooting the bridge i was ONCE AGAIN back to square one…
Per il momento sembra tutto ok. Ho riassociato senza rimuovere i dispositivi. Ho riassegnato i nomi e riattivato le scene che sono rimaste ma non abilitate.
I update 1 of my 4 hubs to version 3.1and have exactly the same issue. All the devices are within 10 feet of the device so it’s not a distance issue. Interestingly enough all the devices still operate fine in ewelink cube on the iHost. Think I’ll wait or not at all before I upgrade the other 3 hubs.
majority of devices still offline, slow-ish support email reply focusing away from issue at hand sidetracking blame to network setup (distance of nodes among others) and existence of SonoffLAN which adds strain to their servers…in all there’s 70 Sonoff devices (wifi+zigbee) in this location, many more on others, i suppose 100 Sonoffs overall is a substantial investment over a couple of years, let alone the costs involved so in all…i reckon the time has come to shift focus away from companies that treat their customers like an opportunity to feast on their appetite to automations and tech in general as money pockets alone; and the party goes on..
Today I have over 300 Sonoff devices activated in different ways: Wi-Fi, Zigbee, etc… and I also had problems with the current system, but I don’t have any major problems that stress me out!
However, I’m not having any problems with my device using either Sonoff LAN or eWeLink Cloud, and everything is working fine with the bridges!
Sonoff’s support has been by far one of the best around, including support for older devices!
Just the fact that you can send an email or come to a forum and make a complaint, and someone from the team helps fix it, is already better than 90% of what exists on the market today!
Sometimes the problem may be in the network, and sometimes not!
Sonoff itself once helped me identify an error that was in my network, and that took about 2 months! But even so, all the support existed!
I don’t think it’s a company that’s just here to suck your money!
I sometimes even see her doing the opposite!
For example, many companies have 4-channel Zigbee switches and matter, but Sonoff only has one large 4-channel switch with Wi-Fi!
Sometimes we have to take into account the response time for support, or whatever it may be, since we are probably in different time zones! I imagine that a large part of the people are not in China or in the region where the support team operates!
Yesterday, I noticed a notification about version 3.1.0 for zbbridge-p. I clicked “update” and got the same problem. All ZB devices are offline in Ewelink and EwelinkWeb, but the ZB network itself works because, for example, scenes between ZB devices are being executed. This company completely lacks understanding of the equipment and services they sell. I’m convinced their cloud servers are controlled by homegrown hackers from Bangladesh, etc.
Good news everybody (hint: Futurama for those who know)
…It’s been a couple of days since the last user reboot of the bridge and its polulating slowly yet steadily…We’ re up to 8/48 devices ONLINE in eWelink app / web now, fingers crossed by the end of the year i might have all back online…It’s a pity i already migrated most of my automations over to HA, which along with Alexa have had access to all of them since the day this conundrum started..steep learning curve which I would have prefered to avoid at this point in time, but AI came to the rescue and have produced good results overall..
P.S. I know I’ve been a bit harsh on one of my e-mail replies to customer support, but still i would have expected a reply, at the end of the day support for the better or worst ends up inflicting much of angry customer’s comments, which must be the daily routine given the circumstances with the deteriorating firmware releases as of late…
One might say it’s either due to staff’s actions monitoring these forums and things took a turn for the worse or it’s all physically downhill from this point onwards since the bridge has now began disconnecting from the WiFi network, too…Same router, same SSID for the last 2 years - yes i know…it’s my network to blame, nothing to do with the latest firmware update
P.S. Bridge wouldn’t reconnect - had to power cycle it..amazing stuff, brilliant support, exquisite experience we’ re all living with this ecosystem lately…perhaps a testament of things to come…and to think i just migrated all my automations to HA, maybe it’s all time to also start flashing tasmota to all of it? Anyone went down that path, any ‘easy’ way to go down that road seeing that there’s a slew of time available in everyone’s life to deal with this just because of a buggy firmware release..
