Complain more about influxdb

content/.obsidian/workspace.json

@@ -25,7 +25,7 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "About.md",
+                "file": "Sensors.md",
                 "mode": "source",
                 "source": false
               }
@@ -90,7 +90,7 @@
             "state": {
               "type": "backlink",
               "state": {
-                "file": "About.md",
+                "file": "Sensors.md",
                 "collapseAll": false,
                 "extraContext": false,
                 "sortOrder": "alphabetical",
@@ -107,7 +107,7 @@
             "state": {
               "type": "outline",
               "state": {
-                "file": "About.md"
+                "file": "Sensors.md"
               }
             }
           }
@@ -129,6 +129,7 @@
   },
   "active": "1f1f024283ea8110",
   "lastOpenFiles": [
+    "About.md",
     "ChatGPT Peanut Butter Cookies.md",
     "Bypassing Ports.md",
     "media/cookies3.jpg",
@@ -141,7 +142,6 @@
     "Fake Dog.md",
     "Things I Recommend.md",
     "Backup Strategy.md",
-    "About.md",
     "Hydroponics.md",
     "Hydroponics Aphid War.md",
     "Hand of Ozymandias.md",

content/Sensors.md

@@ -60,4 +60,6 @@ Most of the data is captured by two cheap RTL-SDRs (software-defined radios) tha
 
 The data gets collected by a central Python script that process and stores it in an InfluxDB database for "efficient" storage. The script also runs a web server that queries the database and exposes the data over an API to the dashboard at various dates and ranges. The dashboard is written in JavaScript / React using a simple chart library.
 
-My biggest regret was using InfluxDB. It's a stupid database and I wouldn't recommend it to anyone. The documentation is confusing and I ran into timezone issues with `group by time()`. It also assumes the column data type is an integer if your sensor happens to send it a whole number at first and it won't let you change that. Just stick to Postgres / SQLite.
+My biggest regret was using InfluxDB. It's a stupid database and I wouldn't recommend it to anyone. The documentation is confusing and I ran into timezone issues with `group by time()`. It also assumes the column data type is an integer if your sensor happens to send it a whole number at first and it won't let you change that. Their docs are bad. They dropped the SQL-like InfluxQL syntax for querying with a pipeline-like syntax called Flux in version 2.0. Debian's repos seem to be staying with version 1.x though.
+
+Just stick to Postgres / SQLite.