{actor} created a new topic '...

My computer that runs Ekos has a habit of hanging a few hours in the imaging session. It is unpredictable, so I haven't figured out what is going on yet. Meanwhile, I configured watchdog so it just restarts the whole thing on its own. It automatically launches KStars and runs a script that pokes at KStars/Ekos DBus and INDI interfaces. I leave a simple config file for it with a few parameters. I was able to get the following:

Select configured Ekos profile and start it.
Select configured telescope config slot.
Load configured schedule and start it.

These are all the major steps needed, it mostly works. It even did its job a couple of times already when the computer hung in the middle of night.
Some random ideas:

Some settings are not saved between sessions, like: guiding camera bin level and gain, align capture target accuracy and dark subtraction. There may be more; those I noticed and keep flipping every time I start new Ekos. Unless Ekos saves its settings immediately when changed, I would like to have a button to force sync when I'm done tweaking it, so that I am sure in case of a restart I get where I left it.
Once in a while my INDI drivers fail to start. Mostly it is the SX drivers fails to find its camera, but it can be anything. There should be an easy way to tell if starting INDI was successful. Otherwise I would opt to restart the machine and try again.
Maybe have that startup sequence built into Ekos? Like a single DBus message to start with last state, optionally giving the schedule file.