I tried this:

Before starting kstars/ekos, I deleted both ZWO CCD files. I then started kstars and connected Ekos. The console logging warns that no previous configurations are found.

I then go to the ASI294MC tab and change my settings and save. The two ZWO CCD files seen before are re-created. They actually seem to contain a mix of ASI294MC and ASI120MC properties which seems correct.

I then go to the ASI120MC tab and change my settings there and save. I then look at the ZWO CCD_config.xml file and it now only contains ASI120MC options. The ASI294MC options are lost (but they are still in the defaults file).

I then go to the ASI294MC tab again and click save. If I look at the ZWO CCD_config.xml file I again see a mix of ASI294MC and ASI120MC properties.

I then stop Ekos. The ZWO CCD_config.xml file is again updated and now it contains only ASI120MC properties.

Next time I restart everything my ASI294MC settings are gone.



From looking through the code, I see that each Driver has a config.xml. Each driver can support multiple devices. For each device there can be multiple properties. Each property belongs to a device. So a config.xml can contain properties for different devices that are handled by the driver. I didn't see a simple way to make it so that the device name would be used for the config files, thereby having a config per device. However, it does seem like the code should be able to handle this case, it just seems like something with the ASI120MC-S configuration is somehow not following convention and overwriting the already existing properties.

One thing I noticed is that there is an error on the terminal console upon startup of ekos:

Dispatch command error(-1): INDI: Could not find property CCD_TEMPERATURE in ZWO CCD ASI120MC-S