pimatic-save

---

With this plugin you can save files to a backup medium. It was developed as a spinoff of the pimatic-backup plugin. This thread suggested improvements of which I implemented some in this plugin.

The supported media in this release are FTP and Dropbox.
The save of a file is done via an action rule. The medium independent action syntax is

save “[localpath/]filename” [with timestamp] to <SaveFtpDive | SaveDropboxDevice | SaveMailDevice>

For a daily midnight backup at 1:00, of config.json, you need one of the Save devices and the following rule:

When -> its 1:00
Then -> save “config.json” with timestamp to <your FtpOrDropboxOrMail Device>

With this plugin I will replace my dropbox_uploader script.

If you need something like this, please test it and let me know bugs you found and features you miss.

More info

UPDATE 0.1.6
for the DropboxDevice you can select automatic directory creation based on /year/month/day/. That could be handy for date sorted daily save & backup

UPDATE 0.1.7
improved checking if file exists before saving the rule

UPDATE 0.1.24
add saving a file to an email address

@bertreb said in pimatic-save:

]

Hi,

thank you for this plugin. But I think I need some help because I can’t save the pimatic-database.sqlite file.

Do I need a path or is it enough to only write the name of the file? Because when I write only the name the file is 0 kb big.

And with a path I receive the following error:

error [pimatic]: File 'home/pi/pimatic-app/pimatic-database.sqlite'' does not excist

This is my rule:
then… save “home/pi/pimatic-app/pimatic-database.sqlite” with timestamp to FTP Backup Device

@dnl0319 the path starts at the home directory of pimatic. Mostly /home/pi/pimatic-app.
Tha action part of the rule should be save “pimatic-database.sqlite” with timestamp to FTP Backup Device. And you should use the latest version (0.1.5), because I updated today the file reader.

@bertreb said in pimatic-save:

@dnl0319 the path starts at the home directory of pimatic. Mostly /home/pi/pimatic-app.
Tha action part of the rule should be save “pimatic-database.sqlite” with timestamp to FTP Backup Device. And you should use the latest version (0.1.5), because I updated today the file reader.

Thank you, it worked with the update!!!

@dnl0319 said in pimatic-save:

@bertreb said in pimatic-save:

@dnl0319 the path starts at the home directory of pimatic. Mostly /home/pi/pimatic-app.
Tha action part of the rule should be save “pimatic-database.sqlite” with timestamp to FTP Backup Device. And you should use the latest version (0.1.5), because I updated today the file reader.

Thank you, it worked with the update!!!

Is it possible to use the same pattern for the timestamp as the backup plugin?
backup plugin:
2020-01-19_175732
save-plugin:
20200119-175732

I think its better to read.

thats fine. I discovered that the old version did a 0 bytes upload of my security camera jpg’s. It should now cover all file types.
And i will change the error message, because the ‘path’ is left out and that’s confusing.

yes, i did because of compactness but you are right it should be identical (and readable)

I released version 0.1.6. with the timestamp and error message change.

@bertreb said in pimatic-save:

I released version 0.1.6. with the timestamp and error message change.

works perfectly! thank you!

@bertreb
Hello,

I have the following error for my rule and the cfg is not saved on the server:

When…
its 01:00 or when CFG-Backup is pressed
then…
save “config.json” with timestamp to FTP Backup Device

error [pimatic-save]: Error: can't connect when connection status is: 'connecting'

Did you know why this happend?

I have the same rule for the DB and there is no problem and the DB is saved on the server.

@dnl0319 said in pimatic-save:

connect when connection status is: ‘connecting’

hi, do you get the error now when you push CFG-Backup and do you have more than 1 ftp save rule?

@bertreb said in pimatic-save:

@dnl0319 said in pimatic-save:

connect when connection status is: ‘connecting’

hi, do you get the error now when you push CFG-Backup and do you have more than 1 ftp save rule?

I get this error when the rule is activated at 01:00pm. When I press the CFG-Backup button I don’t get this error.

Yes I have one rule for CFG and one for DB.

and they are triggered at the same time?

@bertreb said in pimatic-save:

and they are triggered at the same time?

Yes I got the problem I think. Yes they are at the some time, that makes sense

@dnl0319 the used ftp library should be capable of setting up multiple connections. Is your ftp server allowing multiple connections?

I changed the ftp client handling a bit and released a new version -> 0.1.8.
You can see (in debug mode) what the initial connection status is before every upload.

Because i don’t want to leave a FTP connection open for a long time, I close the connection after every upload. But when 2 or more uploads are happening at the same time, it’s getting a nice asynchronous challenge

Let me know what the 0.1.8 results are.
And for the short time you can avoid the error by changing the time of the second save

@bertreb said in pimatic-save:

I changed the ftp client handling a bit and released a new version -> 0.1.8.
You can see (in debug mode) what the initial connection status is before every upload.

Because i don’t want to leave a FTP connection open for a long time, I close the connection after every upload. But when 2 or more uploads are happening at the same time, it’s getting a nice asynchronous challenge

Let me know what the 0.1.8 results are.
And for the short time you can avoid the error by changing the time of the second save

Yes I will test the new version.

Yeah I think I will leave the 2 min difference between the two rules. That doesn’t matter.

I tested it and the new version didn’t solve the concurrency problem.
The 2 minutes delay is for now is the best solution
I will come up with a better version.

@dnl0319 version 0.1.9. should be able to do more than 1 save at the same time.
Let me know if it works in your setup.

@bertreb said in pimatic-save:

@dnl0319 version 0.1.9. should be able to do more than 1 save at the same time.
Let me know if it works in your setup.

Thank you. I will test it today.