Hi Aaron,
I try to use indi-allsky with a RPI HQ (IMX477) camera and a RPI Zero 2 W (or RPi Zero W). Because of the memory limitations with the indi_pylibcamera driver by scriptorron. In my trials on my desk and after some conversation with scriptorron I now get runtimes of up to 4 days until the camera stops, Maybe the driver can be further improved, but I have little hope because the root cause is hard to identify. It would be good to handle the problem on a higher level within indi-allsky. The system returns to work if I do a restart of the indiserver service on the remote Zero 2 W AND a restart of indi-allsky on my server. Just doing the indiserver restart does not help, because indi-allsky does not recover. A possible solution would be a ssh remote command execution of the indiserver restart initiated by indi-allsky and restarting image acquisition by indi-allsky.. Would it be possible to implement this? Maybe there are other ways of mitigation already available?
Thank you very much for your great work!

CS, Markus

Read More...