Interpreting 30.3060.01

[BugsonPL]

I'm using two 30.3060.01 stations with latest RPi build from GIT.

I receive data like below but it is not being interpreted:

038 1543871967 L=56 4b 2d d4 2b 2e 11 72 5d b0 f9 e3 00 d0 00 48 08 57 00 3c 08 5e 00 d0 08 35 00 c3 08 33 00 48 08 57 00 3c 08 5e 00 d0 08 35 00 c3 08 33 1a 60 7c ba fa 00 00 00 40 f8 02 RSSI 80 WHB/11 11725db0f9e3 TEMP1 7.2 HUM1 87 TEMP2 6 HUM2 94 TEMP3 20.8 HUM3 53 TEMP_IN 19.5 HUM_IN 51

039 1543872065 L=56 4b 2d d4 2b 2e 11 23 08 cd 6d 50 3a fc 00 48 08 57 00 3c 08 5e 00 d0 08 35 00 dd 08 30 00 48 08 57 00 3b 08 5e 00 d0 08 35 00 dd 08 30 1a 27 45 76 24 00 00 00 2e 84 00 RSSI 80 WHB/11 112308cd6d50 TEMP1 7.2 HUM1 87 TEMP2 6 HUM2 94 TEMP3 20.8 HUM3 53 TEMP_IN 22.1 HUM_IN 48

Shouldn't it be like ?: " 117addaf2ff60 +22.0 55 1772 0 0 0 1540944521 -> 0=indoor 117addaf2ff6c +11.6 86 1772 0 0 0 1540944521 -> c=sensor#1 117addaf2ff6d +22.2 51 1772 0 0 0 1540944521 -> d=sensor#2 117addaf2ff6e +18.8 62 1772 0 0 0 1540944521 -> e=sensor#3"

Best regards, Marcin

[baycom]

It is already interpreted, with -D you see the various values decoded. The format you want is not explicitely printed, it is the parameter list when calling an external program with the -e option. You can try it with -e /bin/echo, but thats just for debugging. Typically you use instead of /bin/echo a "real" program that inserts the parameters in a data base, transfers them to some external controlling process, etc.

[BugsonPL]

All clear- thanks for explanation !

Again appreciate the work you have done with tfrec!

With regards, Marcin

[uschindler]

Hi, I'd like to reopen this issue. I understand what's happening, but there is some difference: Nothing is printed about those sensors in default log mode. For Klimalog (TFA_1) sensors it prints a short line to stdout for each received packet, with the decoded values. But for Weatherhub sensors (I think all of them), nothing is printed, unless you enable "-D" (and then it prints too much information, like the hexdump of packet).

As noted here, the trigger (external process) is of course executed, but the default output is not really consistent at the moment. It should be consistent and at least print the plain values when default logging is enabled.

Uwe

[baycom]

It is inconsistent and caused by the change of the debug level interpretation (-1: quiet, 0: normal, 1++: debug) . I simply forgot to adapt the other files accordingly...

[baycom]

It should be more consistent now. Without any option, the received values are printed. Also the type (TFA1/2/3, ...) is now always shown.