Phillips Hue Bridge and Thanos Integration

Powerful performance with an easy integration, powered by Telegraf, the open source data connector built by InfluxData.

info

This is not the recommended configuration for real-time query at scale. For query and compression optimization, high-speed ingest, and high availability, you may want to consider Phillips Hue Bridge and InfluxDB.

5B+

Telegraf downloads

#1

Time series database
Source: DB Engines

1B+

Downloads of InfluxDB

2,800+

Contributors

Table of Contents

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Input and output integration overview

This plugin gathers status from Hue Bridge devices using the CLIP API interface.

This plugin sends metrics from Telegraf to Thanos using the Prometheus remote write protocol over HTTP, allowing efficient and scalable ingestion into Thanos Receive components.

Integration details

Phillips Hue Bridge

The Hue Bridge plugin allows users to gather real-time status from Philips Hue Bridge devices utilizing the CLIP API interface. By communicating with Hue Bridges, this plugin is capable of retrieving various metrics related to home lighting and environmental conditions. It offers multiple schemes for accessing the bridges, such as local LAN, cloud, and mDNS, ensuring flexibility in deployment scenarios. The plugin can handle diverse configurations such as room assignments for devices, which optimizes the evaluation of statuses, especially in environments with many devices. Furthermore, it provides various monitoring metrics applicable to lights, temperature sensors, motion sensors, and device power status, thereby enabling comprehensive insights into a smart home setup. The configuration options allow users to tailor their connections to optimize performance and security, including optional TLS configurations for secure communication.

Thanos

Telegraf’s HTTP plugin can send metrics directly to Thanos via its Remote Write-compatible Receive component. By setting the data format to prometheusremotewrite, Telegraf can serialize metrics into the same protobuf-based format used by native Prometheus clients. This setup enables high-throughput, low-latency metric ingestion into Thanos, facilitating centralized observability at scale. It is particularly useful in hybrid environments where Telegraf is collecting metrics from systems outside Prometheus’ native reach, such as SNMP devices, Windows hosts, or custom apps, and streams them directly to Thanos for long-term storage and global querying.

Configuration

Phillips Hue Bridge

[[inputs.huebridge]]
  ## URL of bridges to query in the form ://:@
/ ## See documentation for available schemes. bridges = [ "address://:@/" ] ## Manual device to room assignments to apply during status evaluation. ## E.g. for motion sensors which are reported without a room assignment. # room_assignments = { "Motion sensor 1" = "Living room", "Motion sensor 2" = "Corridor" } ## Timeout for gathering information # timeout = "10s" ## Optional TLS Config # tls_ca = "/etc/telegraf/ca.pem" # tls_cert = "/etc/telegraf/cert.pem" # tls_key = "/etc/telegraf/key.pem" # tls_key_pwd = "secret" ## Use TLS but skip chain & host verification # insecure_skip_verify = false </code></pre>

Thanos

[[outputs.http]]
  ## Thanos Receive endpoint for remote write
  url = "http://thanos-receive.example.com/api/v1/receive"

  ## HTTP method
  method = "POST"

  ## Data format set to Prometheus remote write
  data_format = "prometheusremotewrite"

  ## Optional headers (authorization, etc.)
  # [outputs.http.headers]
  #   Authorization = "Bearer YOUR_TOKEN"

  ## Optional TLS configuration
  # tls_ca = "/path/to/ca.pem"
  # tls_cert = "/path/to/cert.pem"
  # tls_key = "/path/to/key.pem"
  # insecure_skip_verify = false

  ## Request timeout
  timeout = "10s"

Input and output integration examples

Phillips Hue Bridge

  1. Automated Lighting Control Based on Room Occupancy: Utilize the Hue Bridge plugin to monitor motion sensors within various rooms of a home. When motion is detected, the system can automatically trigger the lights to turn on, providing convenience and energy efficiency. This integration could significantly enhance user experience and preferences, adapting the lighting to occupancy levels without manual intervention.

  2. Environmental Monitoring in Smart Homes: Implement the Hue Bridge plugin to track temperature and light levels within the house. By continuously monitoring these metrics, users can create a comfortable indoor climate, adjusting heating and cooling systems based on temperature trends or activating lights based on light levels detected. This data-driven approach leads to smart home automation that responds to actual environmental conditions.

  3. Integration with Home Automation Systems: Leverage this plugin to integrate Philips Hue Bridge statistics into broader home automation frameworks. For example, collecting light and temperature data can feed into a centralized dashboard that provides homeowners with insights about their energy usage patterns. Environments can be programmed to respond proactively to user habits, promoting efficiency and energy conservation.

  4. Battery Monitoring for Smart Devices: Use the Hue Bridge plugin to monitor battery levels across various connected smart devices. By being alerted about low battery states, homeowners can take timely actions to replace or recharge devices, preventing outages and ensuring smooth operation of their smart home systems.

Thanos

  1. Agentless Cloud Monitoring: Deploy Telegraf agents across cloud VMs to collect system and application metrics, then stream them directly into Thanos using Remote Write. This provides centralized observability without requiring Prometheus nodes at each location.

  2. Scalable Windows Host Monitoring: Use Telegraf on Windows machines to collect OS-level metrics and send them via Remote Write to Thanos Receive. This enables observability across heterogeneous environments with native Prometheus support only on Linux.

  3. Cross-Region Metrics Federation: Telegraf agents in multiple geographic regions can push data to region-local Thanos Receivers using this plugin. From there, Thanos can deduplicate and query metrics globally, reducing latency and network egress costs.

  4. Integrating Third-Party Data into Thanos: Collect metrics from custom telemetry sources such as REST APIs or proprietary logs using Telegraf inputs and forward them to Thanos via Remote Write. This brings non-native data into a Prometheus-compatible, long-term analytics pipeline.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.

Powerful Performance, Limitless Scale

Collect, organize, and act on massive volumes of high-velocity data. Any data is more valuable when you think of it as time series data. with InfluxDB, the #1 time series platform built to scale with Telegraf.

See Ways to Get Started

Related Integrations

HTTP and InfluxDB Integration

The HTTP plugin collects metrics from one or more HTTP(S) endpoints. It supports various authentication methods and configuration options for data formats.

View Integration

Kafka and InfluxDB Integration

This plugin reads messages from Kafka and allows the creation of metrics based on those messages. It supports various configurations including different Kafka settings and message processing options.

View Integration

Kinesis and InfluxDB Integration

The Kinesis plugin allows for reading metrics from AWS Kinesis streams. It supports multiple input data formats and offers checkpointing features with DynamoDB for reliable message processing.

View Integration