No images yet with this particular setup with the secondary Raspberry Pi, but I will after the next clear night! The only difference between what I described in the post and what I normally run is the additional Raspberry Pi dedicated to controlling the mount. That, and now I want to run everything off batteries located on the mount so I don't have cables going anywhere.
I have a couple different setups that I've been running for about a year. Which one I use depends on the camera, and that's mainly because large FITS files tend to slow things down. So, I do both: with smaller FITS files I setup a remote profile in the INDI control panel and do everything locally in KStars and Ekos as if my Mac is connected directly to the devices, and every command in the image sequence (change filters, shoot exposures) goes over wifi, and every image comes back and appears in the viewer as if the devices are local. The same applies to auto focusing, plate solving, guiding, etc.
For narrowband I typically use my Atik414EX, which has 6.45μ pixels at a resolution of 1394x1040, and this produces small FITS files, which transfer quickly. Nothing is stored on the Raspberry Pi in this case, but it does all the direct work with the devices. In the capture tab I have the directory set to "local", which will transfer the captured image to my Mac. You can also set it to "both" and store it on the remote and local machines.
For color imaging I have a ZWO ASI071MC, which has an APS-C sized 16MP sensor with 4.8μ pixels. The 32MB FITS files do not transfer quickly, and so I would rather they remain local to the machine connected directly to the devices. In this case I VNC into the remote machine and run everything from there.
Almost every image I've posted over the last year in my astro journal (
saltwaterwitch.com/astronomy) uses one of these two methods--narrowband: remotely controlled with image data and everything else transferred over wifi, and color: VNC into the remote machine to control it directly and the image remain on the remote machine to be copied off after the night's run.
Here's a screenshot of the Profile Editor in KStars on my Mac for the above setup. Mode is set to "Remote" with the Primary Pi's IP address over port 7624. When you hit "Start INDI" all the devices connect and from my point of view it's as if they are all plugged into my local machine.