I did do one thing that I thought was creative, but is really only useful in my use case. For the libcamera integration, indi-allsky thinks it is talking to a normal indiserver.

indi-allsky uses the pyindi-client to interact with INDI. Therefore, I had to write a fake pyindi-client class to emulate the behavior of this module. indi-allsky still calls functions like connectServer(), but they do not do anything.

OK, but does this mean that for the time being I cannot use my configuration?

The sd card from my raspy 3 also fails when used in my raspy 4.

I am getting the same error with my Rpi3. I need to go check on my Rpi4, maybe I am running an older version of indi.

So according to the github page the rpi HQ camera is supported witg libcamera on Bullseye 64 bit when compiled on device.

Is there a downside to this or is it fully supported by indi-allsky when done this way?

No downsides other than you have to build indi even though you do not use it. The libcamera support is transparent to the user.

You may want to forgo using Raspian 10 and just use the libcamera support on Raspian 11 64-bit instead.

I guess this is confusing since Raspbian 11 already has libcamera support.

Would it be safe to say for Raspbian 11 arm64:
Compile indi with build_indi.sh for indilib supported cameras
OR
Use libcamera for Raspberry PI HQ camera ?

---Answered own question:

Ah, that would be a NO, build_indi.sh is required regardless.
Thanks

It's alright, I started development of the indi-libcamera driver now. Hopefully in a couple of weeks we'll have something usable.

Thanks, Aaron.

I installed Bullseye 64-bit, used the build_indi script and connected the HQ camera via libcamera (I installed on raspy 4, that's much faster compared to raspi3). This seems to work on raspy 3 & 4 , both services are now running.
I now want to get some experience and might com back with questions if needed.

Thanks
Kurt

Thanks a lot! It's just what I needed. I had to install a few libs:

<code>sudo apt-get install libindi-dev libcamera-dev libcamera-apps libboost-program-options-dev</code>

Unfortunately, I get build errors on buster complaining about "addFitsKeyWords" being unknown and I had to copy the /usr/include/libcamera/libcamera/* files to the parent dir.

Fixing those and starting the driver works, but I can't see images and the size is 0,0, likewise the pixel size.

Any help here would be appreciated!

We shouldn't hijack this thread, I'll create another topic for this driver: indilib.org/forum/ccds-dslrs/12177-indi-libcamera-driver.html