Thanks !
a-lurker,
it has been a LONG time since I looked at this… I was still using LogViewer. InfoViewer is heads and tails… awesome work, thank you!
Here is Info Viewer 0.64. It fixes a bug where the Z-Wave information was broken since September when the Wiki page containing the Z-Wave command class list changed. The plug-in no longer relies on the external Wiki page but instead uses the same internal table used by ZShark to interpret Z-Wave commands. The Z-Wave info screen now return more information about the device.
ZShark also has some enhancements. It will now display the route taken by a Z-Wave message to its destination. This is most useful with large Z-Wave networks where Vera may not be able to reach all of the nodes directly.
Cheers!
Gengen
Note. This version was buggy and has been removed. Please use Info Viewer 0.65 further down in this thread.
Interested in this…could someone point to installation info? This would save some guessing and messing
@Zooz: see first post http://forum.micasaverde.com/index.php/topic,13477.0.html
@gengen: great job! have you considered uploading this plugin to the Mios Market?
[quote=“capjay, post:125, topic:174138”]@Zooz: see first post http://forum.micasaverde.com/index.php/topic,13477.0.html
@gengen: great job! have you considered uploading this plugin to the Mios Market?[/quote]
Thanks!
I’m getting ‘Lua Engine failed to start’. Running 1.5.672, no usb logging. Should I try an older Info Viewer version first or something?
This should not cause Lua to fail.
Please get a regular log usins ssh
Cat /var/log/cmh/LuaUPnP.log
Look for message lines in red which might explain the failure.
First time browsing the logs
Some json missing…maybe that causes my problems?
[code]> 02 10/23/14 17:35:14.786 luup_require duplicate json <0x2bcb9680>
50 10/23/14 17:35:14.787 luup_log:83: Neither json nor dkjson found <0x2bcb9680>
01 10/23/14 17:35:14.788 LuaInterface::StartEngine failed run: 83 [string “-- Al Info Viewer 0.64…”]:3912: attempt to call field ‘decode’ (a nil value) <0x2bcb9680>
01 10/23/14 17:35:14.785 luup_require can’t find dkjson <0x2bcb9680>[/code]
Here is Info Viewer 0.65. It uses an internal JSON parser rather than relying on one which may or may not already be installed in UI5.
Thank You! Works well now.
Very interesting info provided by the plugin. Grreat.
Hi gengen,
It seems UI7 does not like it when trying to put a URL in the label text in the JSON file. Anyone having a solution, or must it be done with a javascript tab definition?
Cheers Rene.
I have installed the latest .65 version. With IE9 and remote access I am having issues opening the infoview link. I get the generic HTTP 404 error that i cannot find the webpage.
Anyone else have this issue? Same problem happened with .61.
Thank you!
UI7 remote access suuport may not yet be there yet. Its on my TOD list
Hello. Okay. Looking forward to trying it once available. I hear great things about this plugin.
Are there any screen captures, etc. for UI5/6 that I could see so that I have a sense of how this works and what information is presented. Very curious.
Thank you.
Actually, I’m working on some significant improvements to the log viewer prtion. The current version may work with UI7 but not with remote access. I hope to release the new version next week.
Hi Gengen,
In UI7 the target=“_blank” tag is striped from any URL you include in the JSON file label. I have asked Vera to allow the target tag and they said they will consider it in a future release. I also asked them to look at how the URL now get mangled. Meantime switching to a JS for things like this seems the only option.
Cheers Rene.
Holy log file, Batman…this plug-in is a gold mine! :o
Interesting. The link seems to work for me in UI7.
So, I tied installing this in UI7 by uploading the 5 files. Did I miss a step? After uploading, I can’t find any sign that anything has changed, no new UI appeared anywhere and now new devices or apps are listed. What did I do wrong?
I want to use it for log viewing to troubleshoot other plugins I’d like to use like DataMine and GCal3.
read the first post in this thread. You need to create the device.