Works ok for me.

Does it make a difference that in this case /bin/ash is actually trying to execute a python app/script? Doesn't that conflict in some way?

I did workaround this, tough. Instead of executing /opt/syncevolution/sync.py I do /usr/bin/syncevolution - actual syncevolution application (sync.py is just a front-end for syncevolution). This way my syncing via alarmed works ok.

Generally, I rather wouldn't automatically insert any command execution prefixes as you do with /bin/ash -c 'command-entered-by-user' - if one user is savvy enough to schedule a custom command, he/she should type command exactly as it should run.

General suggestions/wishlist to Alarmed
Since it gladly works as I expected, here's couple of my suggestions to the app:

• Add ability to disable/enable specific jobs, instead of deleting/adding them.
• Automatically remove single-run jobs, ie. "alarm in 5 minutes" - add option to delete that job once it goes off.
• On the jobs list only display name of job given by user (currently job descriptions, especially those based on cron syntax are painfully long).
• Add more built-in functions, ie. launching device backup (suggested by someone before), (dis)connect cellular/wifi adapters, switch 2G/3G modes, change telepathy accounts online/offline statuses etc.