I have found that my Orchid v2.0.4 stops recording after a restart of my Pi.
My Pi NTP daemon is pulling from the same NTP servers that my Windows PC pulls from.
If I restart my Pi with everything working perfectly(including video capture and streaming), my Pi takes about 10 to 12 seconds to go down and come back up.
I then log into Orchid and attempt to view live stream. It times out, showing no video. The clock icon in the title bar produces a message stating that "The client time and server time are off by 13 seconds.
You should seek to correct this using NTP server, as it may cause playback issues."
If I VNC into the Pi and execute "timedatectl status", while having my Windows PC time applet up, they show to be exactly in perfect sync.
So, what I presume is happening is that the Pi is 10 seconds "behind" as soon as the Pi starts up, but the NTP is updating system time within about 10 seconds after the Pi has finished coming up, but since this is occurring just after the Orchid service has started, Orchid is not "recovering"(for lack of a better description) in spite of the fact that just a few seconds after it started, system time was corrected and is being maintained.
In this state, both live view and archiving are broken.
If I navigate to "System Status" and click "RESTART", both archiving and live streaming resume working and will run without error until the next restart of the Pi.
Considering how time is maintained on a Pi, not having a true hardware clock, shouldn't Orchid have an internal mechanism to do it's own periodic check for sync of time? Might anyone have a suggestion for a work-around, to perhaps, for example, literally set a delay of some sort of how Orchid starts up after a reboot of the Pi?
any ideas or suggestions would be greatly appreciated