💬 Log Parser

[hek]

@Wes,

Here's a gist with the code for the log parser
https://gist.github.com/henrikekblad/c1d652cce16eaf2ef6340eacaefc97b0

[wes]

@hek I believe this should fix the issue:

https://gist.github.com/liwenyip/de6ff2a646ee417fcf2629eae64e6974/revisions#diff-a83c26f29ff664a062308cb4387554c0

AFAIK you can't do a pull request on Github Gists.

Hope that helps.

[hek]

Thanks, updated.

[Nca78]

Hello, it seems only the two rightmost columns are filled, I have the same problem with all the browsers.
Example:
https://www.mysensors.org/build/parser?log=TSF%3AMSG%3ASEND%2C1-1-0-0%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%2Cft%3D0%2Cst%3DOK%3A40 TSF%3AMSG%3AREAD%2C0-0-1%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%3A40 TSF%3AMSG%3AACK TSF%3AMSG%3ASEND%2C1-1-0-0%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%2Cft%3D0%2Cst%3DOK%3A45 TSF%3AMSG%3AREAD%2C0-0-1%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%3A45 TSF%3AMSG%3AACK TSF%3AMSG%3AREAD%2C0-0-255%2Cs%3D255%2Cc%3D3%2Ct%3D20%2Cpt%3D0%2Cl%3D0%2Csg%3D0%3A TSF%3AMSG%3ABC TSF%3AMSG%3ASEND%2C1-1-0-0%2Cs%3D255%2Cc%3D3%2Ct%3D21%2Cpt%3D1%2Cl%3D1%2Csg%3D0%2Cft%3D0%2Cst%3DOK%3A0 TSF%3AMSG%3ASEND%2C1-1-0-0%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%2Cft%3D0%2Cst%3DOK%3A50 TSF%3AMSG%3AREAD%2C0-0-1%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%3A50 TSF%3AMSG%3AACK TSF%3AMSG%3ASEND%2C1-1-0-0%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%2Cft%3D0%2Cst%3DOK%3A55 TSF%3AMSG%3AREAD%2C0-0-1%2Cs%3D5%2Cc%3D1%2Ct%3D38%2Cpt%3D1%2Cl%3D1%2Csg%3D0%3A55 TSF%3AMSG%3AACK

[BoresExpress]

Seems like log parser incorrectly prints command types for signature messages (see picture):

[gbsmith]

Just started MySensors 2.3 project. I have the same problem as Nca78 had 5 months again.
Only the two right columns are filled. Better than nothing but not perfect as intended.
And yes I tried running this code directly: https://gist.github.com/henrikekblad/c1d652cce16eaf2ef6340eacaefc97b0
Is anyone maintaining this code?

[gbsmith]

Clearly the debug log format has changed to something that this tool does not support.
My log entries look like:
228642 TSF:MSG:SEND,1-1-0-0,s=2,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=OK:0
The old log entries looked like this:
0;255;3;0;9;TSF:MSG:READ,12-4-0,s=18,c=1,t=16,pt=1,l=1,sg=0:1

[hek]

The gist has now been updated to the lastest running on mysensors.org

[berkseo]

think it's time to add passive node support :) ||| Unknown | ?TSF:MSG:SEND... | |

[willemx]

No support for Gateway Transport messages?
GWT:TPS:TOPIC=mygateway1-out/19/255/3/0/21,MSG SENT

[alphaHotel]

@hek I was able to add support for stream message types to the log parser but can't perform a pull request against the gist. Here is my diff analysis if you're interested in this small update.

I also made a subsequent one line change to correct the issue that @BoresExpress noted a while back.

[hek]

Thanks a bunch @alphaHotel, incorporated now!

[The Grue]

Logparser is really a helpful tool. But is there a version that I can run offline on my computer?

• It is annoying to be forced to be online, just to interpret logs
• If I had it on my computer, I coult pipe the debug output through the parser and see the results life

[hek]

@The-Grue
The page does not require internet to work (once it has been downloaded).

[Jens Jensen]

I also found the logparser did not handle certain log entries, such as the logfile produced by the mysensors gateway on raspberry pi, e.g. prefixed with timestamps, etc.

Opened pull request to improve this, comments welcome, especially if you are able to test this locally (only need to copy the Logparser directory and open logparser.html locally in a browser):
https://github.com/mysensors/MySensors/pull/1468

[hypnos97]

This post is deleted!