You must have Kstars from the OS's repository installed? It's possible that version isn't recent enough to support offline astrometry plate solving.
So yes, best get the Kstars from the ppa in the links previously.
To help in daylight and without need of attaching mounts and such, you can create an additional Ekos profile. I call mine "Simulators" and I add a bunch of things like
Telescope Simulator for the mount
CCD Simulator for the imaging camera
Guide Simulator for the guide camera
That allows you to do a certain amount of "playing around".
Yeah... so still doesn't work. Let's go over my setup real quick:
INDI server running on RPi3. Now includes the astrometry driver which i confirmed is running.
I've confirmed that the astrometry program is installed as is Kstars (but I haven't done anything with them... should I be launching Kstars on the pi?)
Kstars/EKOS client is a Windows 10 machine.
The equipment profile has Astrometry as an Aux driver.
We've confirmed the index files are where they are supposed to be and permissions are ok.
I get the same behavior: it captures a picture, sends it to the solver and then solver fails.
I didn't realize you were accessing the RPi via KStars running in Windows; I thought you were running KStars directly on the RPi but via a VNC or browser interface from Windows.
I haven't yet set up a remote astrometry solver. As you're running Windows on your workstation, you don't have much choice in the matter, but I wouldn't normally set it up with the remote astrometry server running on the Pi as its processing power is limited compared to workstations. I mean I have it running locally on the Pi, but that's to ensure I have it when I'm in the middle of nowhere.
After an hour or so at this using my desktop machine as the putative astrometry server and a laptop as the client doing astrometry look-ups, all I get are solver failed errors.
I had the indi astrometry driver loaded and enabled on the server profile (with Telescope Simulator and CCD Simulator) and the same on the client, with it connecting to the server's IP address. Everything appears to load up fine on the client machine. From the server machine, I can do a local (i.e. offline) "Resolve and Slew" on an existing FITS but when I try that on the client with "remote" set it just fails.
Is there a guide somewhere detailing exactly what has to be configured for remote astrometry to work, on both the server machine and the client machines?