Fantastic! As long as vendors help INDI, new products can be used within the RPI community. Having RPI support makes purchasing decisions easier.
The udevadm rules process has strict syntax. Testing rules takes knowledge of Raspbian and udevadm. When you get it right, INDI recognizes the device. This is because the driver gets loaded by the rule when required. My QHYCCD devices require loading firmware before being recognized by INDI.
With StellarMate, the complexity just described is controlled by an app. Investigate this app by isolating the device and focusing on finding what INDI needs to use it. Once done, integrate the other devices with it.
Asynchronous devices are a different animal. They want exclusive use of Comm ports. Cameras usually are not Comm port hungry. The LSUSB output says it consumes several USB resources. It might need some ACM action. Let’s use the StellarMate tools first.
The problem I am having is with the INDI Web Manager.
I can't get it to run automatically at boot.
I have to issue the command "indi-web" to get it going.
The command "systemctl status indiwebmanager.service" gives the following output... (see attachment)
In comparison to the output from "systemctl status ssh.service" it does not appear as it it is actually running.
I already did a "systemctl enable indiwebmanager.service" to try to activate it at boot.