Or maybe a warning that starting EKOS is going to fail because of a device being offline? Maybe by trying to start EKOS when "start scheduler" is pressed for a quick check-up. Now it may happen that I just disconnected a device, scheduled something and when it was time to start it just failed because of that. But it could happen I went to bed already..

It shouldn't start if a device is not connected. Ekos logs?

No, it doesn't do that indeed. What I meant was that it would be nice to have an indication that a connection problem is going to take place when the scheduler wants to start Ekos later on. Now I press "Start Scheduler" and it goes to sleep until the time is right, which could be in the middle of the night when I sleep... I can imagine that I forgot to connect a device, but there's no indication about that when I start the scheduler. That would be nice, maybe.

Well, I added a Notification event when the scheduler aborts for whatever reason. You can use KDE Notification settings to customize what happens on the event, by default it just plays an error sound. You can customize it to do whatever you need like send an email or run a script to wake you up! But predicting the future is not yet in Ekos features list

Oh shoot, I thought you were able to perform miracles! It was just an idea to see if Ekos could check at the start by itself, but ofcourse people can already do that themselves. Thanks for the notification event though!