I think Jasem said it is fixed in nightly. So you either move to the nightly (beta test) build, or wait for the next stable release.

Look at the "Get INDI" menu for instructions on how to change to the nightly build (e.g. under Ubuntu), or build INDI from source after pulling the latest from Github.

If you now have Stellarmate then you can open a support ticket with them.

In StellarMate, indi_lx200am5 is available after you run update_indi_core, just not in KStars since KStars uses an internal driver list. For now you can start the driver on console:

indiserver -v indi_lx200am5 ind_asi_ccd indi_qhy_ccd

Then update the equipment profile to select "remote", and keep everything as is. Just specify "ZWO AM5" in the mount box and then you can connect. When KStars 3.6.1 is released, it should have the AM5 entry.

EDIT: I found the reason why KStars is still using the older name. Would release a KStars fix to KStars later tonight so that the above is not necessary.

Many thanks. It works for me. And also looking forward to the new update tonight. Thanks.

I was able to test under the stars yesterday and indeed I can confirm the above reported issues are gone. Thank you Jasem for the quick fix!
I did notice another weird issue though. Guiding (or tracking?) Stopped somewhere around meridian (i had meridian flip off because I didnt nees it). Need to test again to confirm but anyone else noticed it?

I ran into this trying to use my astroberry to control my AM5 mount. The error messages were, from first to last,

"Couldn't get date format string from device"
then
Error setting UTC offset
followed by the errors in slewing; something to the effect that "Couldn't slew to <<RA, DEC>> JNow (I don't recall the exact words), so I assume the error in getting the date cascaded into an error computing the slew target coordinates.
My astroberry is up to date with respect to the astroberry repositories (but not, of course, with kstars-bleeding)

Hi everyone! Have issue with connecting mount in Ekos.
In log:

2023-05-14T20:46:16 Failed to connect to ZWO AM5. Please ensure device is connected and powered on.
2023-05-14T20:46:06 Connecting INDI devices...
2023-05-14T20:46:06 INDI services started on port 7 624.
2023-05-14T20:46:06 Starting INDI services...

In mobile app and asi mount desktop app working well.
Please help)

Did you check port and baud rate?

No. Where can I check it?

If I understand correctly, this is not baud rate and there is no correct port. But I do not know why

You have your ZWO AM5 set up for Network connection (green) in the Indi Control Panel. Click on the Serial button and then the serial port and baud rate options should be available.

I tried ofcourse. But when i click on Serial the port is not getting available still

Did you check the USB devices on your system with "lsusb"? You should get something like "Bus 001 Device 008: ID 03c3:4001 ZWO Systems ZWO Device" for the AM5.

On the Indi Control Panel for the ZWO AM5, you should see, among others, the AM5 port "ZWO_Systems_ZWO_Device_..." in the System Ports list and the Port being selected should be ZWO_Systems_ZWO_Device... one. Baud rate on mine is 9600, I have the automatic search enabled also.

Other than that, I am not sure of what it can be.