A Log Viewer plugin to try out - it displays the log file in your web browser. This plugin has three main advantages:
Ver 0.51
[ul][li]It has a PAUSE button[/li]
[li]No need to SSH into Vera[/li]
[li]You can specify a ‘Lua pattern’ to narrow down the log entries to those of interest.[/li][/ul]
This plugin has been tested using the Vera U15 interface and Firefox 17.0.1 only.
Installation for U15:
Go to U15–>APPS–>Develop Apps–>Luup files and upload the five files.
Select the “Create device” button on the same page. Enter ‘D_LogViewer1.xml’ into the ‘Upnp Device Filename’ entry box and select the ‘Create device’ button immediately below.
Notes:
You access the log file web page by clicking on the link that can be found on the Log Viewer device’s ‘Set Pattern’ tab. You also enter a ‘Lua pattern’ to filter the log file. Examples of patterns can be found here:
To remove all filtering just leave the pattern entry box blank and hit the ‘Update’ button.
The pattern can be updated in the U15 page while the Log Viewer page is running - it will change to reflect the new pattern.
You can Pause/Continue by clicking on the light bulb icon on the web page and then scroll back and forth as needed.
The page is set to go back 1000 lines when it first opens. So if you want to check a Vera startup process, just click on the link, once Vera has finished starting up. If you click on the link too early ie prior to start up completion, you will get a ‘500 - Internal Server Error’ or a ‘No handler’ error.
The lines will just keep piling up in the web page. I have no idea how many lines can be shown on the page before the browser blows up but I’ve had it running with no filter for over a day.
Log file rotates done by Vera are automatically accommodated.
The log file is expected to be at it’s default location ie /var/log/cmh/
The log file web page will not be visible outside you local LAN.
Due to a bug in the Vera UI 15 - patterns entered must be URL encoded - so if you need a % symbol write %25 instead.
Due to a bug in the Vera log file generator, the log file contains escape characters and characters above 7Fh. As the log file is sent to the browser as UTF8 encoded XML, I have had to replace them with ASCII characters.
All control characters are shown as ‘ctrl_chr’ and characters above 7Fh are displayed as ‘intl_chr’. My apologies to non English speakers but I can’t see a better way to handle these characters in this case.
Will be interested to hear if this plugin works OK but I have no immediate plans to do any more work on it.
Ver 0.52
This gives more definitive error messages, rather than the “XML is malformed” message.
For those who have installed ver 0.51, you will also benefit from some other minor improvements. When the Lua filter pattern is changed; this now gets marked on the output like so:
****** Lua pattern changed to: Ping ******
It also goes back to the start of the log file to find all entries rather than starting at the current location.
Ver 0.53
Turned off the debug mode
Ver 0.54
Hardened pattern input and caught a few edge cases. A few more messages are now output to the user. It’s recommended to update to this version.
Ver 0.55
Fixed a regression
If you have any previous version installed already, you only need to update the file ‘L_LogViewer1.lua’ The version number can be seen on line 11.
Ver 0.56
Fixed a problem where the Lua pattern wasn’t handled properly between engine restarts
If you have any previous version already installed, you only need to update the file ‘L_LogViewer1.lua’ The version number can be seen on line 11.
Log Viewer no longer supported. Please use Info Viewer instead:
http://forum.micasaverde.com/index.php/topic,13477.0.html
