All of a sudden I get errors about temperature and no image capture.

Does anyone noticed anything similar?

Aaron,

any interest in adding a focuser routine for a 28byj? I find it rather unconvenient refocusing as I always have to open the dome and at times temperature shifts the focus.
I tried to integrate the astroberry focuser to no avail...

BTW Thanks for your wonderful piece of software!

MS

I will take a look at this. I may have have a few ULN2003 stepper controllers already. It may be a month or two before I make much progress on this.

Greetings from Denmark

I just found the project last weekend, and big kudus for making it.

So I set up the indi-allsky server with a ToupTek IMX585 Color, and I can’t seam to get it to behave as expected.
I have been trying to make it work proper for over a week now and I can’t figure if I’m doing something fundamentally wrong or the driver or driver communication with this driver isn’t supported properly.

Frankly it seams random if it works or not as expected from each time I reboot the server.

I don’t want to invest in a fisheye lens, glass/plexi dome, housing etc before I know it I can get working, so I am just testing it with a cheap scope for now.
Any suggestions, config tips etc. is welcome. I really want this to work, but it feels like it is going nowhere, and if I went ahead and build a proper allsky setup I don’t want to hassle around with it several hours each time I reboot it.


I didn’t encounter any problems during the installation. It just took around 50-60 min.

3 primary problems:
1. Temperature and fan control does not seam to work. The fan is just running and temperature is not showing correct.
2. 12 or 16 bit also seam to not work properly when I choose it manually. When set to auto it sometimes work.
3. Bayer pattern, also only seams to work when set to auto.

The camera is powered by 12V 7A power supply.
USB3 cable to USB3 port on raspberry pi 4, 16 gb ram version.
Linux raspberrypi 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux

I am not sure if I misunderstand something but I have lots of questions about how this work.

When I connect remotely from my Mac OS with Kstar/Indi remote the camera works as it should, just as connecting directly to it with kstar/indi on a AstroArch, StellaMate, Astroberry etc. but then it stops working most to the times on the indi-allsky server while I am remote connected. Sometimes it does continue to run and I can change setting remotely. And when I change something in the driver settings it seams to works fine. But if I close Kstar/Indi remote without disconnecting the settings seams to stay as I set them. But if I disconnect and close the Kstar/Indi remote the camera switches off inc. fan and after a few minuts the indi-allsky server starts the camera again and settings is most often messed up and fan/temp doesn’t work again, and most often image looks messed up.

One of the questions I keep wondering is why is there a ‘INDI Camera Configuration field’ in the webpage config, when the settings seams to be represented in a field as well?

I tried this config, but I don’t think it does anything at all. I base that on if I change the resolution it has no effect. Gain the same. I tried the other version as well because I wanted to run 16 bit HDR. But I gave up on that part for now.

{
"TEXT": {},
"PROPERTIES": {
"CCD_OFFSET": {
"OFFSET": 200
},
"CCD_TEMP_RAMP": {
"RAMP_SLOPE": 5,
"RAMP_THRESHOLD": 0.5
}
},
"SWITCHES": {
"TC_CONVERSION_GAIN": {
"on": [
"GAIN_HIGH"
],
"off": [
"GAIN_LOW"
]
},
"CCD_CAPTURE_FORMAT": {
"on": [
"INDI_RAW"
]
},
"CCD_RESOLUTION": {
"on": [
"3856 x 2180"
]
}
}
}

I tried simpler versions as well without any luck.
I can't find a complete list of all the setting as there are on the Indi graphical settings.
When I set things to auto it mostly works, or at least sometimes.

A snip from the log when set to auto:
2024-03-14T18:57:29.490482+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.getCcdInfo() [532]: Detecting bayer pattern
2024-03-14T18:57:29.951067+01:00 raspberrypi [INFO] Capture-10-2617/MainThread miscDb.addCamera() [101]: Camera DB ID: 2
2024-03-14T18:57:29.957990+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.configureDevice() [710]: Setting switch DEBUG
2024-03-14T18:57:30.058890+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.set_switch() [1352]: Enabling Disable (DISABLE)
2024-03-14T18:57:31.059787+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.updateCcdBlobMode() [409]: Set BLOB mode
2024-03-14T18:57:31.060122+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.configureDevice() [710]: Setting switch CCD_FRAME_TYPE
2024-03-14T18:57:31.160177+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.set_switch() [1352]: Enabling Light (FRAME_LIGHT)
2024-03-14T18:57:32.161509+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture._initialize() [743]: Minimum CCD exposure: 0.30000001 (day)
2024-03-14T18:57:32.161919+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture._initialize() [761]: Minimum CCD exposure: 1.00000000 (night)
2024-03-14T18:57:32.162146+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture._initialize() [782]: Maximum CCD exposure: 10.00000000
2024-03-14T18:57:32.162322+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture._initialize() [821]: Default CCD exposure: 1.00000000
2024-03-14T18:57:32.162521+01:00 raspberrypi [ERROR] Capture-10-2617/MainThread capture._initialize() [847]: CCD day gain below minimum, changing to 100
2024-03-14T18:57:35.166789+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.saferun() [213]: Camera last ready: 0.0s
2024-03-14T18:57:35.167326+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.saferun() [214]: Exposure state: unset
2024-03-14T18:57:35.167696+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.detectNight() [1185]: Sun altitude: -7:06:52.9
2024-03-14T18:57:35.168095+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.detectMoonMode() [1203]: Moon altitude: 42:55:45.7, phase 25.2%
2024-03-14T18:57:35.268572+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.getCcdTemperature() [868]: Sensor temperature: 25.1
2024-03-14T18:57:35.368998+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.getTelescopeRaDec() [853]: Telescope Coord: RA 6.32, Dec 55.91
2024-03-14T18:57:35.419512+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.shoot() [1391]: Taking 1.00000000 s exposure (gain 100)
2024-03-14T18:57:35.519880+01:00 raspberrypi [INFO] Capture-10-2617/MainThread indi.set_number() [1324]: Setting Duration (s) = 1.0
2024-03-14T18:57:35.520499+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.saferun() [408]: Image queue depth: 0
2024-03-14T18:57:35.520782+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.saferun() [439]: Total time since last exposure 0.2530 s
2024-03-14T18:57:37.834260+01:00 raspberrypi [INFO] Capture-10-2617/MainThread capture.saferun() [332]: Exposure received in 2.4143 s (1.4143)

I also tried another ToupTek camera, and now it lists both cameras in the admin menu to choose from. How do I delete the one I am not using? I want to remove the one that I am not using.

Any suggestions or hints to any of this?

Cheers,
Frank

For some reason when running a 'indi_getprop | grep touptek' I saw several of the same lines twice. So I cleared with 'indi_setprop "ToupTek ATR3CMOS08300KPA.CONFIG_PROCESS.CONFIG_PURGE=On"' and '"indi_setprop "ToupTek ATR3CMOS08300KPA.CONFIG_PROCESS.CONFIG_DEFAULT=On"' and after that the camera seamed to work better and I could reboot several times to test if everything started up as it should, and it did.

I had it running for a few hours fine, until I decided to run a apt update and upgrade, and that broke the service.
It seams to be Flask that is broken, or perhaps wrong python version. Something changed for sure. I tried all the instructions I could find to repair it and the db as well. No luck.
When I run installation again it fails in the end. No matter if I run ./setup.sh or the ./web_only_setup.sh it ends with the following parse error:
'parse error: Expected another array element at line 78, column 3'
.....
**** Setting up gunicorn service ****
**** Enabling services ****
**** Setup rsyslog logging ****
**** Indi-allsky config ****
**** Flask config ****
parse error: Expected another array element at line 78, column 3
###############
### ERROR ###
###############

The setup script exited abnormally, please try to run again...

snippo@raspberrypi:~/indi-allsky $ systemctl --user status indi-allsky

Loaded: loaded (/home/snippo/.config/systemd/user/indi-allsky.service; disabled; preset: enabled)
Active: failed (Result: exit-code) since Fri 2024-03-15 15:35:22 CET; 11min ago
Duration: 3.157s
TriggeredBy: ● indi-allsky.timer
Process: 2539 ExecStart=/home/snippo/indi-allsky/virtualenv/indi-allsky/bin/python3 allsky.py --log syslog run (code=exited, status=1/FAILURE)
Main PID: 2539 (code=exited, status=1/FAILURE)
CPU: 3.307s

Mar 15 15:35:21 raspberrypi python3[2539]: ^^^^^^^^^^^^^^^^^^^^^^^^^^
Mar 15 15:35:21 raspberrypi python3[2539]: File "/usr/lib/python3.11/json/decoder.py", line 337, in decode
Mar 15 15:35:21 raspberrypi python3[2539]: obj, end = self.raw_decode(s, idx=_w(s, 0).end())
Mar 15 15:35:21 raspberrypi python3[2539]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Mar 15 15:35:21 raspberrypi python3[2539]: File "/usr/lib/python3.11/json/decoder.py", line 355, in raw_decode
Mar 15 15:35:21 raspberrypi python3[2539]: raise JSONDecodeError("Expecting value", s, err.value) from None
Mar 15 15:35:21 raspberrypi python3[2539]: json.decoder.JSONDecodeError: Expecting value: line 33 column 3 (char 1467)
Mar 15 15:35:22 raspberrypi systemd[834]: indi-allsky.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 15:35:22 raspberrypi systemd[834]: indi-allsky.service: Failed with result 'exit-code'.
Mar 15 15:35:22 raspberrypi systemd[834]: indi-allsky.service: Consumed 3.307s CPU time.

Dammit, it was a one week old install witch was updated only a few days ago. Thats why I always hated debian/ubuntu.. these things always happened in the past.
Is there any chance that indi-allsky will install on AstroArch or a Manjaro? I really don't wanna test it and break my AstroArch installation. It is the most stable from all the Astro distro I have tried, also compared to StellaMate. I could try it on a fresh Manjaro building everything from scratch, but I really don't wanna waste my time on if anyone already know it is will not work.

Any ideas on that, or how to solve this problem?

Cheers,

The temperature control should be in the indi-allsky config page on the Camera Tab.

I have just started putting some consideration toward installing on Arch, but it is not ready yet. Automating configs on Arch is a bit more difficult than it is on a Debian distribution since Arch has not fully embraced the .d directory style configurations.

The JSON error you are seeing are not due to an upgrade. There is likely a typo in "/etc/indi-allsky/flask.json". Can you provide the output of "cat /etc/indi-allsky/flask.json | json_pp > /dev/null" ?

I do not have a Touptek camera to test with, but I do have an Altair Astro, which are related in the INDI drivers. My Altair camera outputs 12-bit numbers, so I would select 12-bit for your camera. What behavior are you seeing here?

I would leave the bayer pattern at Auto, unless you have a problem with the wrong bayer pattern being used. This is a very rare occurrence.

Connecting from KStars/EKOS can lead to undesired behavior because it can change settings on the camera while indi-allsky is managing it. EKOS also has a tendency to save settings, which alters the expected defaults. You can clear these by deleting the XML files in "$HOME/.indi/"

The final question is why there is an INDI configuration section vs settings in the web page... Some settings are common across all cameras, like exposure, bin mode, temperature target, etc. Other settings are vendor or even camera specific. The custom settings can even change between INDI releases. What is interesting about EKOS is the settings panels you see are all dynamically generated. EKOS queries the camera/device for its settings, EKOS builds the interface based on each setting and each setting type. Some settings even appear/disappear based on the state of other settings.

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

I just merged a change that should allow you to restart the indiserver at will on the Raspberry Pi and indi-allsky should self-recover. The indiclient emits a signal when the indiserver disconnects, I finally did something with that signal. Just setup a cronjob on the Raspi to restart the indiserver once a day.

Hi Aaron,
thank you for the change, a first step to mitigate the problem. I will do a daily restart of the indiserver now. Worst case, it will be out of service for almost 24h. Doing the remote indiserver restart if indi-allsky detects the out of order condition would be really nice.
another queston: in your wiki about the indi_pylibcamera github.com/aaronwmorris/indi-allsky/wiki...ra-setup#indi-config you mention a indi config change for AWB. Where exactly do I have to do this change? I was to dumb to find the place. Would it be good to have a specific indi_pylibcamera ini file?

CS, Markus

You can ignore that INDI configuration. That was just a reference on how to enable AWB if you want it enabled. I do NOT recommend enabling AWB via libcamera.

I am not sure about indi-allsky trying to fix the indiserver by itself. There are some people who use the indiserver to manage devices other than just the all sky camera.

Instead of just restarting the indiserver, you may consider just rebooting the Pi Zero daily (during the day). There is a lot that may go wrong with libcamera that does not exist within the indiserver.

your signal catching and capture process restart does work. Had a hung camera this morning, manually restarted the indiserver and pictures came in again. The log showed the catch of the signal and the restart.
I think the remote restart could be an optional feature or just a driver restart like the indi web manager is capable of doing. Something like if the camera is BUSY for more than 60s do a driver restart, if more than 180s do an indiserver restart, if more than 360s do a remote reboot.

CS, Markus

Hello everyone. I'm trying to install indi allsky on a raspberry Pi 4, but after running./setup.sh the following error is displayed:

ERROR: Exception:
Traceback (most recent call last):
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/urllib3/response.py", line 438, in _error_catcher
yield
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/urllib3/response.py", line 561, in read
data = self._fp_read(amt) if not fp_closed else b""
^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/urllib3/response.py", line 527, in _fp_read
return self._fp.read(amt) if amt is not None else self._fp.read()
^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/cachecontrol/filewrapper.py", line 98, in read
data: bytes = self.__fp.read(amt)
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/http/client.py", line 465, in read
s = self.fp.read(amt)
^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/socket.py", line 706, in readinto
return self._sock.recv_into(b)
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/ssl.py", line 1278, in recv_into
return self.read(nbytes, buffer)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/ssl.py", line 1134, in read
return self._sslobj.read(len, buffer)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TimeoutError: The read operation timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/cli/base_command.py", line 180, in exc_logging_wrapper
status = run_func(*args)
^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/cli/req_command.py", line 245, in wrapper
return func(self, options, args)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/commands/install.py", line 377, in run
requirement_set = resolver.resolve(
^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 95, in resolve
result = self._result = resolver.resolve(
^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
state = resolution.resolve(requirements, max_rounds=max_rounds)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 427, in resolve
failure_causes = self._attempt_to_pin_criterion(name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 239, in _attempt_to_pin_criterion
criteria = self._get_updated_criteria(candidate)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 230, in _get_updated_criteria
self._add_to_criteria(criteria, requirement, parent=candidate)
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/resolvelib/resolvers.py", line 173, in _add_to_criteria
if not criterion.candidates:
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/resolvelib/structs.py", line 156, in __bool__
return bool(self._sequence)
^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 155, in __bool__
return any(self)
^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 143, in <genexpr>
return (c for c in iterator if id(c) not in self._incompatible_ids)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/found_candidates.py", line 47, in _iter_built
candidate = func()
^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 182, in _make_candidate_from_link
base: Optional[BaseCandidate] = self._make_base_candidate_from_link(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 228, in _make_base_candidate_from_link
self._link_candidate_cache[link] = LinkCandidate(
^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 290, in __init__
super().__init__(
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 156, in __init__
self.dist = self._prepare()
^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 222, in _prepare
dist = self._prepare_distribution()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 301, in _prepare_distribution
return preparer.prepare_linked_requirement(self._ireq, parallel_builds=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/operations/prepare.py", line 525, in prepare_linked_requirement
return self._prepare_linked_requirement(req, parallel_builds)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/operations/prepare.py", line 596, in _prepare_linked_requirement
local_file = unpack_url(
^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/operations/prepare.py", line 168, in unpack_url
file = get_http_url(
^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/operations/prepare.py", line 109, in get_http_url
from_path, content_type = download(link, temp_dir.path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/network/download.py", line 147, in __call__
for chunk in chunks:
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/cli/progress_bars.py", line 53, in _rich_progress_bar
for chunk in iterable:
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_internal/network/utils.py", line 63, in response_chunks
for chunk in response.raw.stream(
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/urllib3/response.py", line 622, in stream
data = self.read(amt=amt, decode_content=decode_content)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/urllib3/response.py", line 560, in read
with self._error_catcher():
File "/usr/lib/python3.11/contextlib.py", line 155, in __exit__
self.gen.throw(typ, value, traceback)
File "/home/leo/indi-allsky/virtualenv/indi-allsky/lib/python3.11/site-packages/pip/_vendor/urllib3/response.py", line 443, in _error_catcher
raise ReadTimeoutError(self._pool, None, "Read timed out.")
pip._vendor.urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='www.piwheels.org', port=443): Read timed out.


###############
### ERROR ###
###############

The setup script exited abnormally, please try to run again...


Can anyone help sort it out? Thank you.