Today I updated Kstars/Ekos/Indi. Now I will use v3.5.9 of this software solution.
I made a test last hour. I ran a sequence with 700 files (without the TS "Append Time stamp to the prefix"). But I had only 494 image saved. So on 3.5.9 version, we have yet this problem.
I use Astroberry Server. I updated it. But it's only 3.5.9 version. Not 3.6.0 version yet. May be later...
I think it is likely that it started the run by overwriting the same file and then after midnight the sequence started incrementing correctly.
Some additional clues that might help track this down.
I am unable to duplicate it with the simulators.
I have not seen it happen with darks or flats and they never start a sequence with 000 only 001.
I cannot be certain that it has anything to do with the 000 numbering, but it started at the same time, back early last year.
It happens with and without using the scheduler.
It seems to correct itself when midnight occurs.
If it is happening and you stop and start the capture sequence it seems to fix it for the current run.
Losmandy G11 with Gemini 2 controller
QSI 583/683 monochrome cameras with filter wheel
Starlight Xpress Lodestar X2 guide camera
Microtouch Focuser controlled using Arduino UNO emulating Feathertouch controller
Raspberry Pi 2GB with Raspberry Pi OS 64bit Bullseye