Eric Claeys

@jsalsburg, Hi. What's the status of this Issue? Is it still a problem that Allsky needs to address? Or was it "user error" and can be closed? I added your...

ok, thanks. I'll close the Issue. Your comments about notifying the user for an almost-full disk are included in the "new WebUI" effort. I find a lot of "user error"...

The problem is when `capture_??? -cc_file` is run. For the imx708 camera with a minimum gain of ~ 1.2, it displays the minimum as 1.00.

@WirthmU, ASI_ERROR_GENERAL_ERROR indicates a hardware problem - could be the camera itself, the USB cable, or the Pi. Is this a new camera? Things to try: 1. Is the cable...

An easy way to check if it's the new Allsky is to try `allsky-OLD` if you still have it. Other than a new Allsky, what else is different than what...

Run: `./uhubctl --help` It's something like ~~~ ./uhubctl --action off --exact --search 03C3:0 sleep 3 ./uhubctl --action on --exact --search 03C3:0 ~~~ Where 03C3 is the code for ZWO.

@WirthmU, what would a watchdog timer do? If Allsky finds the uhubctl command it will automatically invoke it after 5 USB-related errors. I think it will do that two times,...

I have never been able to figure out how uhubctl's "location" and "port" map to what lsusb returns, which is how Allsky determines if a camera exists. And it doesn't...

@aaronwmorris, in the next Allsky release allsky.sh only power cycles the port the ZWO camera is on: ~~~ SEARCH="${ZWO_VENDOR}:${ZWO_CAMERA_ID}" # e.g., 03C3:385b sudo "${ALLSKY_BIN}/uhubctl" --action off --exact --search "${SEARCH}" sleep...

Closing Issue - we believe it's a hardware problem, not software. User was able to get his camera working again.