Repository navigation
App FTP Client
FTP Client documents BLL coding in text arguments. Configure a server and destination in FTP Client, then use a supported filename field, such as in the image-saving Flow:
snapshot-{[ date("yyyy-MM-dd") ]}.jpg
For a date such as 2026-11-12, this produces snapshot-2026-11-12.jpg.
For more frequent uploads, add the time:
snapshot-{[ date("yyyy-MM-dd-HH-mm-ss") ]}.jpg
The expressions are evaluated when the card runs. Two uploads producing the same path can overwrite a file, depending on server behavior. Avoid secrets in filenames. See the FTP Client BLL examples.
The original BLL users topic
shows a Save Image Token Flow and the resulting file. The card displays
Micro Web Server - _Test as the selected destination. These screenshots
illustrate an earlier version of the apps; use the current format codes
documented above when adapting the example.
Historical Flow screenshot: a BLL date expression is used in the destination filename.
Community result: the saved image uses the timestamped filename.
The FTP announcement shows both a custom date pattern and a shared named format:
Historical Flow screenshot: an explicit date pattern is embedded in the image filename.
Historical Flow screenshot: the filename uses BLL's shared
shortdatetime format.
The second screenshot uses {[ date("shortdatetime") ]}.jpg. Shared formats
are configurable in BLL, so the resulting filename depends on your settings.
For portable filenames, prefer an explicit pattern such as
camera-{[ date("yyyy-MM-dd-HH-mm-ss") ]}.jpg. This is an adaptation:
it avoids slashes and colons that a locale-dependent display format might
produce. Date codes in older screenshots can differ from current examples.
The Base64-saving announcement demonstrates Simple (Sys) LOG exporting its complete log as Excel Base64, then FTP Client saving that content as a file:
Historical Flow screenshot: an Excel Base64 export is connected to FTP Client's Base64-saving action.
The screenshot saves log.xlsx. For the complete scheduled workflow,
format choices, and retaining daily copies, follow
Simple (Sys) Log's FTP export walkthrough.
Use FTP Client's Save File from base64 to decode the export, not a
plain-text file action. See the current
FTP save card reference
for destination fields and upload behavior.
The same announcement explicitly mentions BLL variables as another source. Use Get all variables, select Excel (base64) as its format, and pass the Variables output token to FTP Client's Save File from base64:
bll-variables-{[ date("yyyy-MM-dd-HH-mm-ss") ]}.xlsx
This is an adaptation of the documented export-to-file workflow, not a separate forum screenshot. See BLL exports for available formats. Use settings' variable export/import when you need the app's corresponding data-transfer workflow; an Excel report is not a complete Homey backup.
Verify the saved file can be opened, set a retention policy on the server, and protect exported values and camera images. Use an appropriately secured server connection supported by your installed FTP Client version.
Support development - If Better Logic Library is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!




