Make sure to reboot after running this command (it is an overkill, but just to be safe).

Update and lingering issue - I was able to work on this issue intermittently over the last few days. I checked the dialout group and my user was indeed already included. What ended up fixing my serial connections was to follow the instructions from the website ask Ubuntu . Admittedly, I don't fully understand why this worked other than there seemed to be a product ID conflict and commenting this out did allow me to connect to my devices via /dev/ttyusb0,1,2,3...

Here is the solution :
1) Edit /usr/lib/udev/rules.d/85-brltty.rules
2) Search for this line and comment it out: ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm", GOTO="brltty_usb_run"
3) Reboot


LINGERING ISSUE - I still cannot get my QHY183c to be recognized by Ekos. When I start the service in Kstars Device manager I see the following:
2023-05-09T03:18:40: startup: /usr/bin/indiserver -v -p 7624 -m 1024 -r 0 -f /tmp/indififo88932c7a
2023-05-09T03:18:40: listening to port 7624 on fd 5
2023-05-09T03:18:40: Local server: listening on local domain at: @/tmp/indiserver
2023-05-09T03:18:40: FIFO: start indi_qhy_ccd
2023-05-09T03:18:40: FIFO: Starting driver indi_qhy_ccd
2023-05-09T03:18:40: Driver indi_qhy_ccd: pid=3013 rfd=9 wfd=9 efd=10
2023-05-09T03:18:40: Client 8: new arrival from 127.0.0.1:49540 - welcome!
2023-05-09T03:18:40: Driver indi_qhy_ccd: -- qhyccd.cpp param
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|libusb_version 1.0.25.11696
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|libusb_init(libqhyccd_context) called...
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
2023-05-09T03:18:40: Driver indi_qhy_ccd: ************************** config file path 23.3.26.4 svn: 1 ************************************
2023-05-09T03:18:40: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /home/orangepi fileName = qhyccd.ini

When I run lsusb in terminal it doesn't recognize the device as QHY, it's seeing it as Cypress WestBridge. I did read that there could be an issue with the fxload file. So I downloaded the latest SDK from QHY's Linux support page for arm64. I decompressed it and found the fxload and replace my /sbin/fxload, but that did not work.

Has anyone else had this issue?

The Cypress WestBridge device is the firmware loader for the camera. Once the firmware is loaded, the camera will begin to function.

If the camera is USB3, the version of fxload in your distribution might not support fx3 (USB3) targets. I wrote these instructions for indi-allsky for building a version of fxload that will work:
github.com/aaronwmorris/indi-allsky/wiki...oad-for-USB3-support

The device ID and firmware will be different for each model camera.

I run your script in an opi5 with m.2 ssd for the system and data. My rig comprises nikon camera, az-eq5 mount and sv305 guide camera. All working fine. I'm willing to install an wifi usb adapter in order to connect from phone to monitor kstars.
I see that the opi5 manual indicates three adapter but I'm not sure if they support AP mode. Have you had success enabling AP in some wifi adapter worth being recommended.

@Fausto
Instead of using USB dongle, I decided to use PCIe card, inserted into m.2. I used couple of different Intel based WfFi cards and both of them worked. I think USB also should work, but I decided that it is more important to have higher speed of WiFi as opposed to disk, so used the PCIe card for Wifi.
My script already installs everything for Access Point, all you need to do is to modify /etc/create_ap.conf to point to correct device names for ethernet and wireless adapter.