Thanks for this, good initiative !
Sugestion: What about providing a rule action, so users can leverage datetime and cron for more flexibility as to when the backups are scheduled.
Although the plugin currently backs up the config, I am already thinking about the power of the plugin: For plugin scalability, the drivers could become devices holding backup parameters (e.g. combined with a resource file on what to backup read by the device). What do you think?
Pimatic-Telegram already is capable of sending files (documents) to a telegram client, for the config backup this could also work.
Also I still have a solid shell script lying around using rsync for backups on the (local) network.
If time permits I wouldn’t mind migrating the backup script etc to a driver and optionally integrating p-telegram, although I am currently working heavily on the TTS plugin. Please let me know your thoughts.
pimatic-telegram | pimatic-tts (pimatic-p2000 | pimatic-oncall)