I'm researching this same situation. But in my case, when I land the drone after flying around a bit, the numbers on the controller are way off. I landed on Dec. 22 and the drone said it was 20 feet away from where home should have been, and also that it was at -10 feet in elevation. So I don't think hitting "home" would have been a good option, certainly not all the way to the point of landing.
I very much agree that getting above the trees seems to help stabilize the drone, but not completely - you can see it move around a bit more than I would like. And since clearly something isn't right, I don't want to find myself in a flyaway situation if GPS goes haywire.
For these flights, I have calibrated the accelerometer multiple times, and the compass as well. I put a level on the solid surface where I do the accelerometer calibration, making sure it's level. And I do the compass calibration outside, with electronics and the controller about 10 or so feet away. They always report back that they completed successfully. And I'm seeing 10 to 14 sats.
This has been making landing tricky, since the drone is definitely moving side to side close to the ground. And even while the drone is sitting on the ground, I can see the airspeed flick between 0 and 5, even though it clearly isn't moving. I do need to open the controller status screen to make sure the controller isn't sending random inputs, but I would be surprised to see that.
And conditions are not windy at all. The drone and controller are on the latest software versions.
Is this covered in more detail somewhere else in the forums? What is the point where you attempt to go back to Yuneec and get them involved, realizing that could be a lengthy or unrewarding effort?
Thanks,
Dale