💬 Log Parser
-
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? -
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 -
The gist has now been updated to the lastest running on mysensors.org
@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.
-
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
-
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
