Compare commits

..

No commits in common. "12a1c86435eaba3fd928448c2693c002de30ce70" and "3add7982f7e9e54cf6069114607d759ae3dee921" have entirely different histories.

3 changed files with 6 additions and 8 deletions

View File

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

View File

@ -60,6 +60,4 @@ 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. 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.
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.

View File

@ -1,2 +1,2 @@
{% block meta %}{% endblock %}<link rel=icon href=data:>{% block style %}{% endblock %}{% block content %}
{% block meta %}{% endblock %}<link rel=icon href=data:,>{% block style %}{% endblock %}{% block content %}
{% endblock %}