This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Just bought an RBS40 from Amazon (like new) to extend my existing system which consists of an RBR40 and another RBS40 (both running 2.1.4.16, wired backhaul, stable). Plugged new RBS40 into RBR40 via ethernet and sync'd. Left it a few minutes and logged in to find that all of my devices were now running firware 2.2.1.210 - wasn't expecting that!
I've manually downgraded the existing RBS40 and RBR40 back to 2.1.4.16 and all is well with them. However when I attempt to downgade the new RBS40 it tells me that the firmware file is incorrect and I can't downgrade. This is not the case as it's the same file I used to downgrade the other RBS40. So I'm stuck wondering if the easiest thing to do is to simply return it to Amazon.
Curiously the RBR40 and RBS40 are now telling me that 2.2.1.21o is available to update...
Any ideas as to what's going on, how to proceed or do I simply return the new RBS40 to Amazon and buy a shrink wrapped one?
Thanks very much for the reply. I solved it. Basically I got unlucky that there was a push of new software as I was trying to upgrade the new RBS40 I bought. So the solution was to manually upgrade the new RBS40 from v1.0.x to v2.0.x which got me around its complaint about the 2.1.4 firmware image. From there everything automatically updated to 2.2.1.210. All running ok so far with ethernet backhaul but let's see for a few days....
AFter the system was updated to v210 did you attempt a factory reset and set up from scratch to see if the problem continued? Some have said a factory reset helped them after a reset.
Thanks very much for the reply. I solved it. Basically I got unlucky that there was a push of new software as I was trying to upgrade the new RBS40 I bought. So the solution was to manually upgrade the new RBS40 from v1.0.x to v2.0.x which got me around its complaint about the 2.1.4 firmware image. From there everything automatically updated to 2.2.1.210. All running ok so far with ethernet backhaul but let's see for a few days....
