An Arduino client library for sending and querying data from InfluxDB 1.x and 2.x, optimized for ESP8266 and ESP32.
InfluxDB Arduino Client is a library that allows Arduino-based microcontrollers, specifically ESP8266 and ESP32, to send sensor data and query information from InfluxDB time-series databases. It solves the problem of efficiently logging IoT device metrics to InfluxDB 1.x or 2.x instances, whether self-hosted or cloud-based, with minimal network overhead.
IoT developers and hobbyists using ESP8266 or ESP32 boards who need to log time-series data (like sensor readings) to an InfluxDB database for monitoring and analysis.
Developers choose this library for its robust feature set tailored for embedded environments, including batching, automatic retries, secure connections, and support for both InfluxDB 1.x and 2.x APIs, all while maintaining a simple and intuitive interface.
Simple library for sending measurements to an InfluxDB with a single network request. Supports ESP8266 and ESP32.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built-in support for TLS with pre-configured InfluxDB Cloud certificates and options for custom certs, ensuring encrypted communication as detailed in the Secure Connection section.
Configurable batch writes and buffer management with automatic retries on failures, reducing network overhead and improving reliability, explained in Writing in Batches and Buffer Handling.
Offers both a modern API and backward compatibility with the original InfluxDB library, easing migration for existing projects, as shown in the Original API section.
Supports various timestamp precisions and automatic time synchronization with NTP, crucial for accurate data logging in batch writes, from the Timestamp and Configure Time sections.
Only compatible with ESP8266 and ESP32 with specific core versions, excluding other Arduino boards and limiting use in diverse microcontroller projects.
Explicitly states that only internal WiFi is supported, preventing use with Ethernet shields or other network modules, which restricts deployment options.
Requires manual certificate handling for secure connections, with frequent updates needed for self-signed certs, or reliance on insecure mode, adding setup complexity.