struggling with this a bit, and love chatGPT´s response.

Q: I am trying to run Kstars and Indi on an ubuntu 22.04 desktop instance. Indi is unable to access the USB connected devices although Linux recognizes the devices. How can I fix this?

chatGPT: There are a few steps you can try to troubleshoot this issue:

Make sure that you have the necessary permissions to access the USB devices. You can check the permissions for the device by running the ls -l /dev/bus/usb/XXX/YYY command, where XXX is the bus number and YYY is the device number. The device should be owned by you or a group that you are a member of, and the permissions should allow you to read and write to the device. If the permissions are not set correctly, you can use the chown and chmod commands to change them.

Check if the Indi server is running as the correct user. The Indi server may not have the necessary permissions to access the USB devices if it is running as a different user. You can check the user that the Indi server is running as by running the ps aux | grep indiserver command. If the Indi server is running as a different user, you can use the sudo command to run it as the correct user.

Make sure that the Indi server is able to detect the USB devices. You can use the lsusb command to list all the USB devices that are connected to your system. If the USB devices are not listed, it could be that the devices are not compatible with Indi or that there is a problem with the USB drivers.

If the Indi server is able to detect the USB devices, but is still unable to access them, it could be that the device drivers are not correctly configured. You can check the configuration of the device drivers by running the indi_debug -l command. This will list all the device drivers that are installed on your system, along with their current configuration. If the configuration is incorrect, you can modify it using the indi_setprop command.

I hope this helps! Let me know if you have any further questions or if you need more assistance.

my actual solution to the problem was to simply enable the "port selector" when devices were connecting. The defaults were garbage I guess.

also verified that I could communicate with other software (terminal) to the connected devices

so chatGPT almost got it right...

my actual solution to the problem was to simply enable the "port selector" when devices were connecting. The defaults were garbage I guess.

also verified that I could communicate with other software (terminal) to the connected devices

so chatGPT almost got it right...

my actual solution to the problem was to simply enable the "port selector" when devices were connecting. The defaults were garbage I guess.

also verified that I could communicate with other software (terminal) to the connected devices

so chatGPT almost got it right...