From ce760ab63306021dd89b3315a15154e013305d6e Mon Sep 17 00:00:00 2001 From: jwansek Date: Mon, 25 Dec 2023 18:50:00 +0000 Subject: Updated readme --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index c2532f9..9be58c2 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,13 @@ # power.eda.gay -Logs Tasmota-flashed power usage monitors to InfluxDB and Grafana using MQTT. +Logs Tasmota-flashed power usage monitors, and Tp-Link Omada POE switches, to InfluxDB and Grafana using MQTT. Looking for the Mikrotik POE usage monitor/exporter? That's been moved to [MikrotikPOEPowerExporter](https://github.com/jwansek/MikrotikPOEPowerExporter) ![InfluxDB screenshot](https://pbs.twimg.com/media/F_U75tVXwAA5QfG?format=jpg&name=medium) +![InfluxDB screenshot 2](https://i.imgur.com/B1J0j4O.png) + ## Setup - `cp power.env.example power.env` @@ -20,3 +22,9 @@ Looking for the Mikrotik POE usage monitor/exporter? That's been moved to [Mikro - Test with the `mosquitto_sub` and `mosquitto_pub` commands, the name of the package on debian is `mosquitto-clients` - Change the config in the Tasmota MQTT web UI, then check the logs to make sure it connects nicely - I like to run `TelePeriod 30` in the Tasmota console to set it to send MQTT messages every 30 seconds, for example. The default is every 5 minutes I believe + +## Switch setup + +You must enable SNMP in the Omada controller with the community string `tplink`: + +![SNMP](https://i.imgur.com/bWUGPQO.png) -- cgit v1.2.3