Data file retrieval

[patricktokeeffe]

New feature: make retrieved EBAM data available to anonymous download. Methods?:

• ftp - easy
• http - easy
• https - would require DNS entry +certbot or self-signed certs
• samba - easy
• mqtt - publishing/easy, serving/hard; only supports 'latest' data

These all support hierarchical publishing / folder structures. Existing disk directory /var/log/ebam/ would be served directly:

• folder of daily-bundled data files
• folder of files with values only - essentially /var/run/ebam/...
• a cumulative data file?

Standing questions:

• how to handle alarms? save as one file per day, if any present? or as cumulative file?
• system settings
  • how to present those under 'latest'? as individual files, or a general "report" file
  • how freq to query? hourly with data prob makes sense - does that make more daily files?
• the cumulative file....
  • does it have system settings merged in, so users can track major changes?

[patricktokeeffe]

Possible directory structure:

/var/log/ebam
+-- /daily
    +-- EBAM_SN_YYYYMMDD.csv
    +-- EBAM_SN_YYYYMMDD.csv
    +-- ...
+-- /latest
    +-- AT
    +-- BP
    +-- ...
+-- EBAM_SN.csv

The latest folder includes

• data report values (ConcRT, ConcHR, Flow, WS, WD, AT, RH, BP, FT, FRH, BV, PM, Status)
• an alarm file, latest alarm report (possibly reset to empty when alarms are cleared?)
• settings values (see response to settings report)
• device info (Model/Part/Revision, firmware info, etc)

Other thoughts:

• would be nice to provide users a metadata file
  • → see pg 28 of 7500 protocol doc: 'request all descriptor information'