I don't know what cameras you are using, but I cannot recall ever having a connection issue with my QHY5L-II-M and Ekos. The 163M took longer, but as I alluded to, the QHY drivers took a long time to mature across all platforms. I do seem to recall someone having an issue with other combinations of QHY cameras. Yeah, I have mostly stuck with Indi/Ekos to have a compact solution while travelling with my gear, and I use an iPad Mini to do most of the control.
A few people have attributed connection issues to underpowered PSUs, so you might see if you can give it some more juice. There was a recommendation for a while to put the cameras through a dedicated, powered USB hub. While using my Rock64 SBC, I used to do that (Sabrent USB 3 , 7 port hub).
If you want to troubleshoot it, there are people here to assist. The output of "lsusb" and "dmesg" is often useful to know if the computer is even recognizing the devices.
That's what the forum is for. Indi/Ekos is one of the best astrophotograpyhy suites around. It is still on the road to perfection, but it is lightyears ahead of where it was when I first joind 30 months ago.
So be patient!
Atlas Pro AZ-EQ, ASI1600MM-Pro, ASI120MM-S, ES102ED, WO-Z61, Nikon D3300, ASI-EFW, ZWO LRGB,Ha,O3,S2 filter set
Oh good, I'm not the only one who can't get EZCAP_QT running. I tried running it directly (the thing that shows up in your start menu is a script) and it failed. I even tried compliling it according to instructions on QHY's site, but the downloaded source code is missing what appears to be a fairly critical file, so it won't actually compile.
I've had that too with the VNC cutting out. But Ekos over the network seems to work fine.
We probably should create a different thread on the VPN issue....
WiFi Connection dropped on me again Sunday night. I used a lightning-to-rj45 dongle to connect directly. Oddly, the UI said I was still connected via WiFi, but perhaps the act of directly connecting reset the configuration. I disconnected and reconnected for good measure, and no problems the rest of the night.
Re the post below, I'm still unable to get everything resolved and when I switch the pi on again the other day with the QHY cameras connected, the keyboard and mouse USB ports refused to join the debugging game... and hence... game over... and lets get back to the real hobby - imaging, not debugging. indilib.org/forum/astroberry/6827-astrob...kstars-and-indi.html
In answer to the question "Is there actually any success story of a fully stable astroberry / ekos/ inid setup with QHYCCD imaging equipment?" Not sure if it helps but I have a very stable setup running the QHY5L-II M as guide camera on Indi/Ekos on a Rock64, although I built it using the simple download Ubuntu instructions at: indilib.org/download/ubuntu.html. I have been using the setup with changes of equipment for about 2 years. Some learning: use a well powered USB hub; make sure the 12v supply has enough power, I use RoyPow 12V 10A Adapter, wires beats wireless, my Rock64 has a wired ethernet connection. One of the challenges of Indi/Ekos is that there are so many options & settings and it takes some digging to get them right. So recently I found Astrometry stopped solving when I changed spacing on a scope and it took me a while to find the setting to get it to forget the old "FOV". But when then once I have a settled config everything works wonderfully.
I guess you can leave all USB ports plugged in and run ekos / indi without any problems.
For QHY cameras, I have to make sure the QHY camera won't confuse with the other one by plugging in one at a time after certain settings in ekos, but I get some other error with the main camera that I'm unable to resolve.
I'm also an Astroberry (2.0.3) user running on a rpi4. My devices are: eq6r pro mount, electronic focuser, qhy5-ii-l mono guide cam, and a dslr as the main image camera (planning to buy a mono QHY, but still deciding). My 4 usb ports are busy. Everything is working fine. It's true I have had some problems, and actually sometimes kstars crashes or experience some strange behaviour, but I can live with it. The solution is fantastic for remote imaging.
For now I will continue using this setup, and I recommend it.
Can anybody confirm, by the way, if actually two qhy cams work together at the same time flawlessly?