Secrets are now hardcoded in the python and ansible files. At least the database user and password would be nice to have in a separate file.

See for example https://blues.com/blog/tips-tricks-optimizing-raspberry-pi-power/

We have a USB power meter in the kelder

Timestamps should be a unix timestamp, they are now returned as a datetime string.

We possibly want to add a simple endpoint that returns the current time of the station. This way we can query all stations and check how close to each other they are.

We had some concerns speed wise about the FastAPI app. Scaling to multiple workers already helped a lot. Might be worh looking into PyPy to see if this gives us any significant speedup.

This makes sure the detections are processed in order in Telraam.

At the moment, it's not clear what programs are calling endpoints (and how frequently). It would be nice to log the User-Agent header and log how frequently what User-Agent calls what endpoint.

Some concerns:

• just logging every request to a file would lead to more wear on the SD-card of the Pi (maybe logging to tmpfs could be possible)?
• having a global object and storing the stats in there might not work well, since there are multitple workers (but we can use https://docs.python.org/3/library/multiprocessing.html#managers)
• some scripts might not have a User-Agent header, or the header might be the same for two programs running on another machine, so it probably makes sense to also log the IP address

the json response fields are camelcase but should be snake case

For reference, the Telraam java class that parses a Ronny detection

   5   │ public class RonnyDetection {
   6   │     public int id;
   7   │     public String mac;
   8   │     public int rssi;
   9   │     public float battery;
  10   │     @JsonProperty("uptime_ms")
  11   │     public long uptimeMs;
  12   │     @JsonProperty("detection_timestamp")
  13   │     public double detectionTimestamp;
  14   │ }

This was adhoc installed from apt during the event last time.

Better would be to install from the git releases as the apt version is 2 years old at the moment. The organisation has official ansible playbooks for this.

• network bottleneck? -> more efficient serialization format is certainly possible
• CPU bottleneck?
• ...