minor: -R12 Oregon THGR810 add TX-button

[ghost]

changes:
729 "channel", "Channel", DATA_INT, channel,
+730 "TX-button", "TX", DATA_COND, (msg[0] & 1), DATA_INT, 1,

980 "channel",
+981 "TX-button",

have fun

[zuckschwerdt]

Thanks! Interesting to see what the unknown bits in the sensor_id are used for!

int sensor_id   = (msg[0] << 8) | msg[1];
if ((sensor_id & 0xf0ff) == ID_THGR810 ...

[zuckschwerdt]

Add with 70726f5

[ghost]

thx Christian,

the result:

as u can see: if the signal is overdriven (+2dB in this case), the battery flag is "0"- ALLWAYS
nothing can change this.., but thats another story
also: channel is "0", should be "1"

[ghost]

ups, mb a new bug.
even with -g16 and -6dB the values are wrong.
Battery is 1.48V and 1.47V, channel should be 1, NO CHECKSUM !
but no big deal, i look at the sources.

[zuckschwerdt]

That's strange. Can you grab the packet data with -R12:v?

[ghost]

with my decoder (false flag R1) the correct values;

need some time to investigate this

[ghost]

R12:v

[ghost]

i changed for test:
685 int channel = ((msg[2] >> 4) & 0x0f) +1; // not for CM sensor types
689 int battery_ok = battery_low;
715 "battery_ok", "Battery", DATA_INT, battery_ok,

makes no sense but this works
sanity check is still missing or faulty, dunno whats going on here..

[zuckschwerdt]

It the same protocol but some fields (channel, battey) are wrong / different? Is there a good way to known if it is a THGR810 or a "v3"?

[ghost]

this two commands are missing:
718 "mic", "Integrity", DATA_STRING, "CHECKSUM",
1003 "mic",
now it works