Android devices keep getting thrown off the Orbi WiFi

OK - so I did some more research on this last night. Not sure if that helps anybody, but maybe someone can confirm or debunk my preliminary conclusions.

As mentioned earlier, the problem was greatly reduced if disabling the 5GHz. That lead me to check more thoroughly what AP the phone connected to and what frequency was used when the disconnects occured. I used the open source Wifi Analyzer for the purpose, and also tried another app with the same name for a "second opinion" with the same results.

With my router and sattelite I essentially have 4 accesspoints; Sattelite 2.4GHz and 5GHz (hereafter called S2 and S5), and R2 / R5 for the routers accesspoints respectively.

During some hours I worked through several areas of my 3-storage house with my old Galaxy Note 3 (with Android 6 if memory serves me right), and my LG G5 with Android 7.

My observations:
When walking around, the old Note 3 seems to handle the switching between accesspoints more smoothly, that is; without really loosing the connection. The LG tends to stick to an accesspoint longer, and then drops the connection for up to a few seconds when switching. This seems to be the case both when switching between router and sattelite, and switching frequency.

When it comes to certain areas, like my bedroom, it gets interesting. The LG on Android 7 seems more eager to connect to the 5GHz than the Note. With the current placement of router and sattelite, the sattelite is the one to cover the bedroom. Hovever, the sattelite is one store down, and some meters aside, so the direct line from my bed to the sattelite goes through one floor and one wall (both wooden). The Sattelite 5GHz (S5) signal is therefore quite some weaker than the S2 signal, but still strong enough to support Youtube streaming in high quality. When connected to S2, the speed is also good.

What happens is that the LG now normally connects to S2 for a few seconds, then drops the connection and reconnects to S2. It may do that for minutes until it connects to S5, then the looping stops for a while. If it then switches to S2 for some reason the process starts again.

The Note 3 behaves differently. When it connects to S2 or S5, it seems more prone to stick to that choice.

So, the obvious solution for this is to move the sattelite. Which I did, only to find that this behaviour now moves to another location in the house...

My natural response to these observations is that the root cause of this behaviour more likely lies in my LG or Android 7 than in the Orbi. And maybe the causes for all the reports of drops in this thread cannot be blamed on the Orbi. But it is suspicious that so many people report this with the Orbi and I have not been able to find similar reports on e.g. the Velop.

So in the end I guess I won't take the chance that the root cause is in the Orbi, and will probably return it while I still can get back my money.

It is also worth to mention that i performed factory reset on the Orbi twice - trying both Router mode (with the Orbi as DHCP server) and Accesspoint mode with my ipFire firewall as the DHCP server. No difference in behaviour there. Also tested different channels to no avail. Will also try a network reset on my LG, and maybe also a full reset if I find the time, in addition to testing fixed ip-adress.

Any views on these observations, especially the difference in behaviour between the phones and/or Android versions are highly appreciated before my deadline for return on Friday :-)