From be2835886bdc8519aac1e917d96a9bc1c513cbf9 Mon Sep 17 00:00:00 2001 From: Peter Olsar Date: Fri, 14 Dec 2018 17:14:04 -0800 Subject: - Added support to specify logger config file on command line. - Added support to specify log directory path in logger config. --- README.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index 6610a98..45fa501 100644 --- a/README.md +++ b/README.md @@ -42,29 +42,37 @@ $ npm start ``` # Logging -By default this app will log the current power usage of each plug every minute, and store 24 hours worth of entries (removing the older entries as new ones are added). This log interval and max retention limit are configurable in the `logger-config.json` file in the root project directory. +By default this app will log the current power usage of each plug every minute, and store 24 hours worth of entries (removing the older entries as new ones are added). This log interval and max retention limit are configurable in the `logger-config.json` file in the root project directory. ``` { + // Directory path where to write log files. It will be created if it doesn't already exist. + "logDirPath": "path/to/logs", + // The number of seconds between each log entry - "logIntervalSeconds": 60, - + "logIntervalSeconds": 60, + // The maximum number of log entries to store "maxLogEntries": 1440 // 24hrs at 1 log/min } ``` The logged data is shown on the 'Logged Usage' graph on the dashboard. -Logs are written in JSON format to the project root directory, with the filename `-log.json` e.g. `8FCA808B79-log.json`. Each file contains all the log entries for that plug, up to the maximum configured number, at which point it will remove the oldest entry when adding a new one. +Logs are written in JSON format, with the filename `-log.json` e.g. `8FCA808B79-log.json`. Each file contains all the log entries for that plug, up to the maximum configured number, at which point it will remove the oldest entry when adding a new one. + +You can specify path to a custom logger config file as the first command-line argument, e.g. +``` +npm start /home/username/tplink-logger-config.json +``` If you are running the app from the Docker image and you want to change the logger config, you can mount your desired config file into `/opt/tplink-monitor/`. The logs can be accessed in the same way. -Each logfile is a JSON array of entries. Each entry contains a timestamp in unix/epoch format `ts`, and a power reading in watts `pw`. +Each logfile is a JSON array of entries. Each entry contains a timestamp in unix/epoch format `ts`, and a power reading in watts `pw`. If you want to analyse the log files in Excel or similar office tools you can convert the JSON file into csv format. This can be done numerous ways including online converters such as [konklone.io/json](https://konklone.io/json/), or if you are on a Unix system (or otherwise have access to `sed`) user [ballachango](https://github.com/jamesbarnett91/tplink-energy-monitor/issues/6#issuecomment-433663873) has posted this sed command `sed -e 's/},{/\\\n/g' -e 's/[]["tspw:}{\\]//g' > log.csv` # Note Because the server needs access to your local network to scan for TP-Link device, you must run the server on the same network which your TP Link plugs are connected to. For the vast majority of people this shouldn't be an issue, and you can still use different network interfaces (i.e. plug(s) on WiFi and server on ethernet) as long as they all connect to the same network. -A note for Windows users: There seems to be an issue with the UDP broadcast the server performs to scan for devices which occurs when you also have VirtualBox installed on your Windows machine. I think this is because the response from the plug is routed to the VirtualBox Host-Only network adapter, rather than your primary network interface (for some reason). +A note for Windows users: There seems to be an issue with the UDP broadcast the server performs to scan for devices which occurs when you also have VirtualBox installed on your Windows machine. I think this is because the response from the plug is routed to the VirtualBox Host-Only network adapter, rather than your primary network interface (for some reason). If you hit this issue you can try disabling the VirtualBox adapter in `Control Panel > Network and Internet > Network Connections` and see if that solves the problem. -- cgit v1.2.3