pscharff FWIW, I saw similar behavior a last weekend when I was shooting with the S50 in the mountains out of cell coverage. The problem was, my phone didn't have a solid location fix to feed to the Seestar unit. Cell phones all have a built in GPS receiver that can get an accurate fix by themselves, but they normally rely heavily on the cell network to do the heavy lifting (the phone actually receives all the GPS signals, and sends em to the network to do the calculations), and may be lazy about getting an accurate fix when off network if you're not using any apps that it recognizes as requiring it.
Symptoms were similar to above. I'd power it up under clear skies and tell it to go look at a target, and it'd try finding it many degrees off angle, and fail. One time it even seemed to start the capture, but stacked nothing, and I found it way off in the Sky Atlas. My fix, I have a GPS Status app that will force the phone to get an accurate fix using internal GPS receiver, and as long as I had that app running, Seestar found the target accurately.
I figured I'd only need to do it once, but it failed the same way on next GoTo, so it appears to be required every time.
Ok.. so what? Surely you're on the network right? Problem is, if you're starting things up while inside of a building, your location fix may be really bad, even while on the network, because it can't hear the GPS signals (can be bad even if you can only see half the sky).
TL;DR: Try making sure that your phone has an accurate location fix before GoTo.
