InfluxDB for time-series data in Raspberry Pi - Step-by-Step Execution

Concept Flow - InfluxDB for time-series data

Start Raspberry Pi

↓

Collect Sensor Data

↓

Format Data for InfluxDB

↓

Write Data to InfluxDB

↓

Query Data from InfluxDB

↓

Analyze or Visualize Data

↓

Repeat Data Collection

This flow shows how Raspberry Pi collects sensor data, sends it to InfluxDB, then queries and analyzes the time-series data.

Execution Sample

Raspberry Pi

from influxdb_client import InfluxDBClient
client = InfluxDBClient(url="http://localhost:8086", token="my-token", org="my-org")
write_api = client.write_api()
point = "temperature,sensor=pi value=23.5"
write_api.write(bucket="my-bucket", record=point)
client.close()

This code connects to InfluxDB on Raspberry Pi and writes a temperature data point.

Execution Table

Step	Action	Evaluation	Result
1	Create InfluxDBClient	Connect to http://localhost:8086 with token	Client object ready
2	Create write_api	Prepare write interface	Write API ready
3	Create data point	Format string 'temperature,sensor=pi value=23.5'	Point string ready
4	Write data point	Send point to bucket 'my-bucket'	Data written successfully
5	Close client	Release resources	Client closed

💡 All steps completed, data point stored in InfluxDB

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
client	None	InfluxDBClient object	InfluxDBClient object	InfluxDBClient object	InfluxDBClient object	Closed
write_api	None	None	WriteApi object	WriteApi object	WriteApi object	WriteApi object
point	None	None	None	"temperature,sensor=pi value=23.5"	"temperature,sensor=pi value=23.5"	"temperature,sensor=pi value=23.5"

Key Moments - 3 Insights

Why do we need to create a write_api object before writing data?

The write_api object manages sending data to InfluxDB. Without it, the client cannot write points. See execution_table step 2 where write_api is prepared.

What does the data point string format mean?

It follows InfluxDB line protocol: measurement,sensor_tag value_field. This tells InfluxDB what data and tags to store. See execution_table step 3.

Why do we close the client at the end?

Closing the client frees network and memory resources. It is good practice after finishing writes. See execution_table step 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result after step 3?

A Client object ready

B Point string ready

C Data written successfully

D Write API ready

💡 Hint

Check the 'Result' column for step 3 in execution_table.

At which step is the data actually sent to InfluxDB?

A Step 4

B Step 2

C Step 3

D Step 5

💡 Hint

Look for the action 'Write data point' in execution_table.

If we skip creating write_api, what will happen?

A Data will still be written

B Client will close immediately

C Write operation will fail

D Point string will be invalid

💡 Hint

Refer to key_moments about the role of write_api.

Concept Snapshot

InfluxDB stores time-series data efficiently.
Use InfluxDBClient to connect.
Create write_api to send data points.
Format data as line protocol string.
Write points to a bucket.
Close client when done.

Full Transcript

This visual execution shows how a Raspberry Pi program connects to InfluxDB, prepares a write interface, formats a temperature data point, writes it to the database, and closes the connection. Each step changes variables like client, write_api, and point. Beginners often wonder why write_api is needed or how the data string works. The quiz checks understanding of these steps and their order.