Hi,

Suppose these problems were introducted when aliases for devices were introduced? (Already was true in previous release as well)

I was trying to create a new setup with a raspberry pi4 used as a server (only drivers, not for kstars). Connecting this with 1GB ethernet cable to my local network and accessing witj Kstars "remote" profiles. Both systems running Ubuntu 20.04 (server arm64 bit on the rpi). Noticed that I could not connect ASIcamera1 and Asicamera2. (It worked when only using the multi device camera)

What I see:
- the remote machine does not return the "correct" device names
- Kstarts gets confused. (if I connect iEQ in the control panel, kstars seems happy, but did not test if it really works)
- Only see one tab for the camera (although 2 processes of asi_single_camera_ccd are launched)


To make sure it is not PI related I tested on my main machine with "local" and "remote localhost" on my main (Intel) machine.

Results:

Local mode:


 
 

[2021-11-17T09:48:04.533 CET INFO ][           org.kde.kstars.ekos] - "Starting INDI services..."
[2021-11-17T09:48:04.539 CET INFO ][           org.kde.kstars.ekos] - "INDI services started on port 7624. Please connect devices."
[2021-11-17T09:48:04.569 CET INFO ][           org.kde.kstars.ekos] - Ekos received a new device:  "ZWO Camera 1"
[2021-11-17T09:48:04.573 CET INFO ][           org.kde.kstars.ekos] - Ekos received a new device:  "ZWO Camera 2"
[2021-11-17T09:48:04.632 CET INFO ][           org.kde.kstars.ekos] - Ekos received a new device:  "iOptron CEM60"

Remote mode:
 


[2021-11-17T09:52:58.136 CET INFO ][           org.kde.kstars.ekos] - "Starting profile on remote INDI Web Manager..."
[2021-11-17T09:52:58.137 CET INFO ][           org.kde.kstars.ekos] - "Connecting to remote INDI server at localhost on port 7.624 ..."
[2021-11-17T09:52:58.137 CET INFO ][           org.kde.kstars.ekos] - "INDI services started. Connection to remote INDI server is successful. Waiting for devices..."
[2021-11-17T09:52:58.144 CET INFO ][           org.kde.kstars.ekos] - Ekos received a new device:  "ZWO Camera"
[2021-11-17T09:52:58.193 CET INFO ][           org.kde.kstars.ekos] - Ekos received a new device:  "iEQ"
[2021-11-17T09:52:58.193 CET WARN ][                       default] - QLayout: Cannot add a null widget to QGridLayout/
[2021-11-17T09:53:12.916 CET INFO ][           org.kde.kstars.ekos] - "Unable to establish remote devices:\n+ ZWO Camera 1\n+ ZWO Camera 2\n+ iOptron CEM60\nPlease ensure remote device name corresponds to actual device name."


Maybe something I forgot to configure? But these things used to work without problems earlier. (And I want to run on a big screen instead of the small vnc window)
Also had some problems with the remote openweathermap interface (really weird, need to investigate further, but when connect button is pressed, it jumps to another tab in control panel) and AsI294 (with the multi driver) where bin1 hangs (Used to work on my RPI with raspbian previous (september build)

Hope someone will sort this out

Paul

Well, since nobody seems to care about basic functionaliy that should worked (and used to work) think I am done with Indi/Ekos



Paul

Try to use ZWO CCD instead of ZWO Camera 1/2/3
I'm also fucked with these 1/2/3, and confused what ware they meaning for.

The ZWO camera 1,2,3 are explained here: indilib.org/ccds/zwo-optics-asi-cameras.html

Well it took only six months to get an answer that I already knew when i wrote the first message.
The point is that there is something wrong in the remote model with driver names, but no developers seem to have reacted, this is probably not important. (btw the standard driver gave too many problems with missed captures when 2 zwo cams are active)

But don't worry. I gave up on Indi completely, switeched to NINA never had a problem again. (Even with Beta versions)

You can remove me from this forum (there seems to be no option to do this myself)

P.

Good luck Paul with NINA, it's a great software!

I actually just checked this issue and the remote camera ZWO 1 and ZWO 2 start just fine. At any rate, will close this topic.