Add support for Grill Thermometer (RF-T0912)

[eshaz]

• Adds support for the "Remote Grill Thermometer" (RF-T0912)
  • FCC ID: TXRFPT0912
  • Product Manual:
    

[zuckschwerdt]

If the temp is 255-x then maybe the bits are inverted? I.e. use bitbuffer_invert(bitbuffer);

[eshaz]

If the temp is 255-x then maybe the bits are inverted? I.e. use bitbuffer_invert(bitbuffer);

They probably are inverted. Since the output we care about is only one byte, I'm thinking it makes more sense to just do the one subtraction operation at the end, vs. invert the entire data.

[zuckschwerdt]

one subtraction operation at the end, vs. invert the entire data.

Maybe do an xor, it's easier to glance what's going on then.

[zuckschwerdt]

Looks good already. Please split the multi-assign lines (40, 68).

If possible abort on all 1's and all 0's in temp -- those are very likely false positive.

Currently a broken code at the end will cancel repeats and abort, right? Might be better to just find the most repeated row with bitbuffer_find_repeated_row(), e.g.

int min_repeats = MAX(3, bitbuffer->num_rows / 2 + 1);
int row = bitbuffer_find_repeated_row(bitbuffer, min_repeats, 24);

[zuckschwerdt]

The "model" needs to be"RF-T0912" -- our rule is alphanum+ - alphanum+

[eshaz]

The "model" needs to be"RF-T0912" -- our rule is alphanum+ - alphanum+

I was just looking at this. There are no labels on the device, other than the FCC ID which I had to look up in their database to get the model number. Wondering if it makes sense to allow more description here so it's easier to identify this device in the rtl_433 output?

[merbanan]

The documentation line should have the "Remote Grill Thermometer" name and the short model name.

[eshaz]

The documentation line should have the "Remote Grill Thermometer" name and the short model name.

I'll make the change, but I still think could be confusing to omit this data from the event. Is there any place where I can add a "Remote Grill Thermometer" description on the output data for the decode events?

[eshaz]

I did some more testing with the device and it appears to support a two byte temperature range (around 9F to 410F) and also uses checksum validation, which makes more sense than what I previously thought. I've added these changes.