Collectd - openwrt and espeasy
Posted: 20 Jan 2019, 17:04
hi there, I started using esp Easy for my energy monitor project.. it uses and openwrt OS collectd for data collection and influxdb as the database graphing is done either by chonograf or grafana --locally or remotely depending on your preference) and for automation Domoticz.... it work very well and all and the best thing is for inputs it is extremely easy. none of this configuring nodes --. it is done through the format of the MQTT. and you can input data at extremely high rates .. ( 65000 inputs a second)
data collection is handled by collectd 5.8 mqtt (also writing to influx is handles by collectd.) and since its built on openwrt foundation with out infuxdb installed locally, the entire operating system when compress is less then 10 megs.. for a fully functioning energy/ IOT monitor. that can be installed on hundreds of different routers or pi devices ( i use the bananapi r1 or r2 ( support local sata)-- but functions just as well on a $7 orange pi zero or first generation raspberry pi. or archer c7 router if you want ).. since it based on collectd basically you can monitor thousand location very easily
but anyways i can not see how one can formats a custom string for mqtt in espeasy.. the string is not that hard.. example and break down of the string
mosquitto_pub -t 'incoming/OpenWrt/mqtt-Energy/power-grid' -m 'N:21.5'
topic : -t
incoming = what collectd uses to monitor incoming data ( required)
Openwrt = equal the host sending the mqtt - the name of the device sending the info or the absolute location
mqtt = what collectd plugin to use (required)
Energy = what subgroup for graphing with rrd ( my current groups are Energy, Flow, Temp, Humidity, Pressure) if using influxdb you can use anything you want as a subgroup name
power= how collectd processes the data- as absolute, derive, counter or gauge ( categories found in collectd type.db ( require)
grid = another subgroup it can be what ever you want the name of the device or location bathroom, living room etc....
metrics: -m
N = is the time of the data -- either N for now or or specified epoch time
21.5 - the actual data sent
how and where would one formats a custom Mqtt string in espeasy
perhaps at some point the developers of espeasy might naively support collectd mqtt as it is a well established data collection system..
data collection is handled by collectd 5.8 mqtt (also writing to influx is handles by collectd.) and since its built on openwrt foundation with out infuxdb installed locally, the entire operating system when compress is less then 10 megs.. for a fully functioning energy/ IOT monitor. that can be installed on hundreds of different routers or pi devices ( i use the bananapi r1 or r2 ( support local sata)-- but functions just as well on a $7 orange pi zero or first generation raspberry pi. or archer c7 router if you want ).. since it based on collectd basically you can monitor thousand location very easily
but anyways i can not see how one can formats a custom string for mqtt in espeasy.. the string is not that hard.. example and break down of the string
mosquitto_pub -t 'incoming/OpenWrt/mqtt-Energy/power-grid' -m 'N:21.5'
topic : -t
incoming = what collectd uses to monitor incoming data ( required)
Openwrt = equal the host sending the mqtt - the name of the device sending the info or the absolute location
mqtt = what collectd plugin to use (required)
Energy = what subgroup for graphing with rrd ( my current groups are Energy, Flow, Temp, Humidity, Pressure) if using influxdb you can use anything you want as a subgroup name
power= how collectd processes the data- as absolute, derive, counter or gauge ( categories found in collectd type.db ( require)
grid = another subgroup it can be what ever you want the name of the device or location bathroom, living room etc....
metrics: -m
N = is the time of the data -- either N for now or or specified epoch time
21.5 - the actual data sent
how and where would one formats a custom Mqtt string in espeasy
perhaps at some point the developers of espeasy might naively support collectd mqtt as it is a well established data collection system..