User Tools
Site Tools
Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| app-notes:ein-mqtt-server-fuer-iot-telemetry-sensoren [2023/11/09 14:46] – [5. Pass on information from the MQTT network to a free messenger.] gray | app-notes:ein-mqtt-server-fuer-iot-telemetry-sensoren [2023/11/09 15:08] – [4. The visualization of the telemetry data with the help of Grafana] gray | ||
|---|---|---|---|
| Line 356: | Line 356: | ||
| ===== - Bring data from the MQTT broker structured into a database ===== | ===== - Bring data from the MQTT broker structured into a database ===== | ||
| - | Create an influx | + | An Influx |
| - | + | ||
| - | The structure in the database is then created with a Python script, using a Json format. | + | |
| - | + | ||
| - | <code c > | + | |
| - | | + | |
| - | { | + | |
| - | ' | + | |
| - | ' | + | |
| - | ' | + | |
| - | }, | + | |
| - | ' | + | |
| - | ' | + | |
| - | } | + | |
| - | } | + | |
| - | ] | + | |
| - | influxdb_client.write_points(json_body) | + | |
| - | </ | + | |
| - | + | ||
| ---- | ---- | ||
| - | |||
| - | |||
| - | With the help of the Python script, you can specifically query data from the broker and store it in the database in a structured way. | ||
| <code c shellyplusht subscribe_datenbank.py> | <code c shellyplusht subscribe_datenbank.py> | ||
| Line 516: | Line 495: | ||
| ---- | ---- | ||
| - | The Python | + | A cronjob starts the Python |
| - | + | ||
| - | < | + | |
| - | + | ||
| - | # Das Skript wird alle 1 Minuten plus 20 sekunden gestartet | + | |
| - | * * * * * sleep 20; / | + | |
| - | + | ||
| - | </ | + | |
| - | + | ||
| - | The script checks if the process is still running. If it is, it does nothing. If the process was terminated it is started again. The Python scripts run endlessly. The cronjob only checks if they are still running. | + | |
| < | < | ||
| Line 560: | Line 530: | ||
| From now on you have access to the data that is already in the database and that will be added over time. | From now on you have access to the data that is already in the database and that will be added over time. | ||
| - | Which measurements have been deposited in the database: | ||
| - | |||
| - | < | ||
| - | :~ $ influx | ||
| - | Connected to http:// | ||
| - | InfluxDB shell version: 1.8.10 | ||
| - | :> use Shelly | ||
| - | Using database Shelly | ||
| - | :> show series | ||
| - | key | ||
| - | --- | ||
| - | power, | ||
| - | rh, | ||
| - | tC, | ||
| - | tC, | ||
| - | tC, | ||
| - | temperatur, | ||
| - | temperatur, | ||
| - | temperatur, | ||
| - | temperatur, | ||
| - | value, | ||
| - | value, | ||
| - | voltage, | ||
| - | voltage, | ||
| - | </ | ||
| ==== - The first visualization under Grafana ==== | ==== - The first visualization under Grafana ==== | ||
| Line 608: | Line 553: | ||
| With this function Grafana Discover I would try more function under the programs. One comes here quickly on solutions that are helpful in the implementation in the dashboard. | With this function Grafana Discover I would try more function under the programs. One comes here quickly on solutions that are helpful in the implementation in the dashboard. | ||
| - | |||
| - | If one is then with the conversion for a dashboard, one can fall back on information here. | ||
| - | |||
| - | {{: | ||
| ---- | ---- | ||