@Doug: The usual way to get Indi parameters to "stick" is to go to the driver's "Options" subtab, find the "Configuration" line, and click "Save". See the image below. In this case it's on the same subtab as the setting "Dome Policy" that you were recommending. Have you tried saving dome policy that way? It seems to get it to stick for me.
@Shayan: In addition to Doug's good advice about domes, the other thing that can sometimes cause similar problems can be solved by following the advice on this page.
stellarmate.com/support/faq/mounts.html?view=faq&faqid=33
It is my "goto fix" whenever my mount is acting weirdly on slews or parking.
Also about plate solving. With StellarSolver, I find it is useful to understand whether it failed due to star detection or the actual plate solving, as there are separate parameters covering the two cases (and also, of course, things like clouds and poor focus can cause the star detection to fail). I believe if you look through the output on the log below, StellarSolver usually says how many stars are detected. If that's 0 or not many, then double check your image to make sure it's reasonable and reasonably in focus. Also check to make sure in the stellar solver options, you're using a reasonable profile. If you continue to have issues there, you should capture a fits file of the image where your solver fails, and post that along with some screenshots of your stellarsolver settings, and folks could chime in with suggestions. Other common issues with stellarsolver include having the wrong focal length stored in kstars. Rob often suggests unchecking the "Use Scale" and "Use Position" checkboxes to help you diagnose the problem. (e.g. Your plate solving would go slower without them, but if the assumed scale is wrong, you'd try and understand why--likely focal length).
Hy