My station (ID:819) doesn’t execute some scheduled observations. Here is how the client comes to see the scheduled observations. When I launch the client I can see that there is an update of the scheduled observations that is done every minutes.
However the problem is that if I look at the web interface of the client the scheduled observations appear for 1 minute then desappear during 1 minute and then appear with the updates …
And when the scheduled observations disappear if an scheduled observation were to start in this same time (during 1 minute approximatively) this observation doesn’t run because for my station durring this time there is no scheduled observation.
It is like this update of the scheduled observations took 1 minute to do this and suddenly my station considers that there is no observation of programmed during this period.
Unfortunately the interface wasn’t implemented in the best way, so it has several issues, this is why we have removed it from the latest (development) version in order to implemented from scratch with a different architecture.
Could you restart your station and then run it for sometime without opening at all the web interface?
I suspect that the problem comes from the web interface but I need to confirm it.
EDIT: Have you checked both web interface and journalctl logs for errors?
That’s strange indeed. The last time I have seen such a behavior was when I have accidentally set wrong longitude and latitude on the client settings.
I have one more guess, that probably is a time issue. Could you check that the time in rpi is the right one and make sure that it is synchronized?
This could explain the missing start times, when there is a sync and the time is moved forward more than 30s. And also the wrong signal curve could be explained with having right TLE and station location but not right time.