Skip to content
This repository has been archived by the owner on May 20, 2024. It is now read-only.

dgomes/ha_rrd_recorder

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

55 Commits
 
 
 
 
 
 
 
 

Repository files navigation

THIS PROJECT IS OBSOLETE

Ever since the introducation of Long-term statistics this project reason to exist has vanished.

RRD Recorder for Home Assistant

This integration is similar to other recorders (e.g. influxdb) but uses RRDTool as a backend. The main benefit of using RRD Recorder is that you can store data for long periods of time without the complexity of adding servers/addon's, unfortunantely it comes with the cost of loss of detailed information for older periods of time (the concept is that you don't need details to the second for data generated a year ago, the average of the day year ago is enough)

Currently, this integration records to the RRD database files and has a "Camera" platform that will generate the graphs

Installation

If you are running Home Assistant OS or Container, you don't need to install anything extra.

Operating System dependencies

RRD Recorder depends on librrd which is a C library.

You will need to follow the steps in https://pythonhosted.org/rrdtool/install.html before this integration will work.

Most likely this will suffice in Debian/Ubuntu:

$ sudo apt-get install librrd-dev libpython3-dev

If you are using Alpine Linux (the base of many Docker Images):

$ apk add build-base rrdtool-dev ttf-dejavu python3-dev py-pip

Actual integration installation

Manual

  • Place the custom_components folder in your configuration directory (or add its contents to an existing custom_components folder). It should look similar to this:
<config directory>/
|-- custom_components/
|   |-- rrd_recorder/
|       |-- __init__.py
|       |-- camera.py
|       |-- const.py
|       |-- manifest.py
|       |-- utils.py
  • Edit your configuration.yaml file according to the example bellow

HACS

If you want HACS to handle installation and updates, add RRD Recorder as a custom repository or find it in the default list of custom integrations.

Configuration

Example:

# Example configuration.yaml
rrd_recorder:
  path: '/rrd'
  databases:
    - name: internet_connection
      step: 30s
      data_sources:
        - sensor: sensor.upnp_router_bytes_received
          name: recv
          cf: COUNTER
          heartbeat: 300
        - sensor: sensor.upnp_router_bytes_sent
          name: sent
          cf: COUNTER
          heartbeat: 300
      round_robin_archives:
        - cf: AVERAGE
          steps: 1m
          rows: 1h
        - cf: AVERAGE
          steps: 5m
          rows: 1d
        - cf: AVERAGE
          steps: 1h
          rows: 1w
        - cf: AVERAGE
          steps: 1d
          rows: 12M

camera:
  - platform: rrd
    name: vodafone
    rrdfile: /rrd/mydata.rrd
    timerange: 2d  
    args:   #if you don't define any args you will get lines corresponding to the DS's in the file
      - "VDEF:vrecv=Recv,MAXIMUM"
      - "VRULE:vrecv#FF3300:MAX"
      - "VDEF:sent=Sent,MAXIMUM"
      - "VRULE:sent#000000:MAX"
      - "AREA:Recv#00FF00:Received Bytes"
      - "LINE1:Sent#0033FF:Sent Bytes"
    rrdgraph_options:   # Optional graph enhancements
      - "--no-legend"
      - "--lower-limit"
      - "0"

RRD Configuration

path:
  description: The location relative to your HA config path where you want to store your rrd database files
  required: false
  type: string
databases:
  description: List of RRD databases (files) 
  required: true
  type: list
  keys:
    name:
      description: Name of the database
      required: true
      type: string
    step: 
      description: how often to expect updates
      required: false
      type: seconds
      default: 300
    data_sources:
      description: Data Sources (DS) of the database
      required: true
      type: list
      keys:
        sensor:
          description: entity id to keep record of
          required: true
          type: entity_id
        name:
          description: short name to be used internally by RRD
          required: true
        cf: 
          description: consolidation function (check https://oss.oetiker.ch/rrdtool/doc/rrdcreate.en.html) for available functions
          required: true
          type: list
        heartbeat:
          description: amount of time after which DS is considered unknown
    round_robin_archives:
      description: Round Robin Archives stored
      required: true
      type: list
      keys:
        cf: 
          description: consolidation function (check https://oss.oetiker.ch/rrdtool/doc/rrdcreate.en.html) for available functions. Possible values are 'MIN','MAX','AVERAGE','LAST'
          required: true
          type: list
        steps:
          description: periodicy of records (a record is stored every step)
          required: true
          type: seconds
        rows:
          description: amount of steps recorded in the database
          required: true
          type: int

Camera configuration

name:
  description: Name of the camera entity 
  required: true
  type: string
rrdfile:
  description: path to the rrd file
  required: true
width:
  description: width of the generated graph
  required: false
  default: 400
height:
  description: height of the generated graph
  required: false
  default: 100
timerange:
  description: amount of time to be displayed
  required: false
  default: 1d
args:
  description: common arguments used by *rrdtool graph*
  required: false
rrdgraph_options:
  description: additional `rrdgraph` command line options 
  require: false

The camera component renders RRD graphs for displaying in HASS frontend.

It tries to guess everything from the rrd file automatically. Alternatively you can anytime pass new arguments in args or command line options in rrdgraph_options.

args

For basic rrd graph, you do not need to make any own configuration in args. In this case rrd graph will render a line for each datasource of rrdfile automatically.

For advanced graph rendering you can use args for definitions of parameters CDEF, VDEF, LINE1, ARRAY, etc. If you will use own args configuration there is automatically generated DEF for each RRA of each datasource.

Example:

Rrd file example1.rrd has configuration:

rrdtool create example1.rrd \
--step '900' \
'DS:temperature:GAUGE:1800:U:U' \
'RRA:AVERAGE:0.5:4:48' \
'RRA:AVERAGE:0.5:96:365'     

For this example1.rrd there are following DEF variables, which you can use in args.

  • Temperature
  • Temperature_AVERAGE_4
  • Temperature_AVERAGE_96

Note: As you see in example a vname is always a capitalized name of ds-name.

Hint use a tool such as http://rrdwizard.appspot.com/rrdgraph.php

rrdgraph_options

This optional configuration allows passing any additional rrdgraph command line options. Each command line parameter must be defined as separate array item.

Example: Dark Mode

rrdgraph_options:
  - "-c"
  - "CANVAS#000000"
  - "-c"
  - "FONT#FFFFFF"
  - "-c"
  - "BACK#1C1C1C"
  - "-c"
  - "SHADEA#1C1C1C"
  - "-c"
  - "SHADEB#1C1C1C"

Example: Vertical Label

rrdgraph_options:
  - "--vertical-label"
  - "Power [W]"

Example: Hiding Graph Legend

rrdgraph_options:
  - "--no-legend"

Example: Force X-axis from zero

rrdgraph_options:
  - "--lower-limit"
  - "0"

Authors