ASIAIR mini completely failing GoTo

Recently ZWO issued a series of firmware updates that weren’t the most stable, including issues with meridian flips and plate solving. They seem to have fixed most of the issues in v2.2.2 (I think). If you’re already on that version, have you tried restoring it back to the original and re-updating it?

Did you turn the mount manually (by unlocking the clutch) after you power on the AIR and the mount? This will mess up communication between the devices.
If not, you can try replacing the USB/connection cables, as those are the most common sources of errors.

sometimes if the phone location is turned off or you don't put in your coordinates, the AA thinks you're somewhere in the other hemisphere (China I guess), and it slews and solves, slews and solves, non-stop

turning on location and restarting the AA and mount solved the problem for me.

this was with an AA app version from sometime earlier last year; I have updated to the newest version and haven't had a problem; I noticed guiding numbers looked better with this new version

try turning off the mount and AA then back on, but also make sure you put in the correct date/time/location in your hand controller (assuming your hand controller requires that like my AVX HC does)

I also want to give everyone a tip if you already put in the correct coordinates and time, or your time was off a little accidentally, and you're slewing the ground or a yard fence, or a house or anywhere with no stars:

when this happens, once the slew is complete, before the app has a chance to try to platesolve, cancel the platesolve, release the clutches and manually push the scope to the opposite direction it was slewing to (so, if scope went from sky to ground, push it back to the sky), tighten the clutches again, continue slew

if scope points to the ground or the horizon still, repeat process, release clutches, point to sky, tighten clutches, slew again, and this usually should be enough to be pointing to the sky, and the AA can take over.

this doesn't disrupt communication between devices, like Johannes is saying; or it could be that every mount acts differently? idk, my mount is fine with it.