After several tests, I found that I had the following problems.
1. The ParkOff button on the mount controller is not functioning.
2. The default value of the mount is no longer North Pole.
If I click ParkOff multiple times in the control panel of the mount driver and Sync the incorrect mount position with the North Pole, I can use it, but even after saving the driver settings, if I reconnect the driver, I cannot use it without repeating the above steps.
There has been a lot of work on that driver lately. I suggest getting the github version and compiling for some of the latest changes and fixes. Some versions of Ekos may crash on driver connection, however if you keep the scope powered off until after starting the Ekos/Indi connections, then turn the scope on and connect in Indi, it should behave for the rest of the session. The mount controller panel in Ekos has had some issues and is being worked on. Some improvements have been made. If the latest compiled version still gives your trouble with the mount controller, then the mount controls in Indi may be used. Not as convenient, I know.
I now use that driver exclusively with my scope, and find that the plate-solving and Kstars GOTO methods of pointing all but remove any need for manual control.
The way the park function works in the current compile version is much better. Basically, you unpark at the beginning and it does nothing (no slew), but then you can move the scope. If you park at the end of your session it will slew to horizon Alt and North Az. This has value for those who program a sequence of targets and need the scope pointed for dome or roof closure at the end. I agree for use as a portable DOB, there is little value for a park at the end of the session.
The latest version has much better tracking than previous versions. Guiding also now works pretty well with the internal Ekos guider for an Alt/Az mount. However, you may have to un-comment the two lines in the code to renable guiding in the current compile. The last time I looked, that hadn't been done yet. If the guiding tab does not show up in INDI, that will be the reason. Those two lines are below a comment that is easy to find as it has the string "TODO" in it and is the only instance of that string in the code.
I haven't tested the mount controller in the latest version, as I don't use it. I do know that the Joystick implementation works very well. The last time I used the mount controller, I did not have good results, but it may have been seen too since then.
There is still some work to be done on the guiding and, as far as I know, the mount controller simulated hand control may still be buggy (I don't use it). I do know that the Joystick control is solid. It is fairly easy to compile from github if you follow the instructions down near the bottom of the page.
I have also had issues with KStars crashing on driver connect. On my systems (Raspberry Pi4 running Ubuntu Server), it seems to be a timing thing. If I start Ekos, then wait a bit (30 seconds or so), it starts without issue and runs normally.
Thank you for your reply.
Indi is a very nice environment, but I would like you to consider the compatibility of the initial setting file when reviewing the driver setting items and updating.
Even though the function does not change, items related to parks and domes are added to the driver and it does not work, or the initial settings are not read and problems often occur.
I should let you know that I am not directly associated with indilib. I have written a documentation for a driver and am a retired programmer, though like you, am an end user. While it is likely others with some actual authority will be reading this thread, I have none.
This community thrives on suggestions and bug reports are always helpful. The community also works best with the combined experience of experienced and users contributing input and potential solutions. The community frequently comes up with options, methods and work-arounds for issues which arise in the software. It is a monumental job to keep up with the changes in hardware and software for all the hardware and software supported with every change and to maintain the codebase.
In the case of this particular driver, it was an adaptation from another driver for a different mount. So, it is not so much that the Park and Dome were added and non-working as they were carried over from the previous driver and time for debug work did not allow the discovery of the issue. I speculate that the original modification for the intended mount may have fallen aside with the arrival of the SynScan device and subsequent indi_synscan_telescope driver, creating a duplication of drivers for the same scope, despite different methods
Recently, there has been some significant work done to the driver to address some of the issues. Park now works as expected and some of the code that caused that and other issues has been removed. I am currently using this driver for every session with my 250P with good success. There are still 3 bugs on my list, but they are more inconvenient than detrimental.
I run Linux on RPi4's, and indi is the only reasonable choice. Having run programming shops in my working life, I am amazed at the amount of code that is written and maintained by so few, especially with most of it being available at the raw code level. Indi is a very nice environment, and astronomy is on fire globally at the moment. With patience and reasonable suggestions for improvements, I believe it can only get better.