Why are you running it from there? Create equipment profile in Ekos and select ASI CCD as your camera and that's it. The Devices --> Device Manager is used WITHOUT Ekos.
I found the way it handled equipment very non-intuitive. It worked connecting the mount that way and so it seemed logical for the camera to work the same way. I was starting just by using Kstars to control the mount and was then using Firecapture for imaging but wanted to hook up the camera to kstars as well so that I could evaluate moving off Firecapture (more likely for DSO work).
2020-08-07T14:49:04 INDI services started on port 7624.
2020-08-07T14:49:04 Starting INDI services...
2020-08-07T14:49:03 INDI services stopped.
2020-08-07T14:48:45 Unable to establish:
+ ZWO CCD
Please ensure the device is connected and powered on.
Also just wanted to add that the camera is connected directly to USB on the computer and there is no hub. It also doesn't matter which USB port I use.
I just pushed an updated INDI ASI driver in GIT. If you can compile that, please install libopencv-dev first and then run cmake.
This would build the asi_camera_test binary that uses the SDK to communicate with the camera. This is independent of INDI. It's using the demo file from ZWO but this file can probably best improved to remove opencv dependency so that it's available for all
Downloaded the SDK from ASI and swapped the symlink for libASICamera2.so.1 to point to the new library rather than the old one.
rw-r--r-- 1 root root 1773128 Aug 7 07:28 /usr/lib/x86_64-linux-gnu/libASICamera2.so.1.15.0430 <--- OLD INDI VSN
-rw-r--r-- 1 root root 2068128 Aug 915:30 /usr/lib/x86_64-linux-gnu/libASICamera2.so.1.15.0617 <--- NEW ASI VSN
Don't know how to fix this properly in INDI, but the above should make it easy to fix for anyone else.