-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Thermopro TP828B Meat Thermometers 2 probes #3085
Conversation
Most things in the decoder exist twice, once for the TP829B and once for the TP828B. |
Yes, I will try, my last version of the decoder can be simplified, as the first data part until temp probe 1 is the same, after we have a gap. I can also consolidate into a single
I'm busy, so will try later, your proposition too... |
Thanks! To clarify: the idea is to have two very simple decoders, not because it's less code, but because it's then a very simple flow without any branching or DATA_COND. ("clever" decoders are hard to maintain later on…) Generally I think: If we want a different "model" (because the protocol is somewhat different) then we should try to have multiple decoders. And if we want the same "model" (because only some data bits are different) then we should try to have only one decoders. |
This looks much nicer and easier to follow, I think. Thanks! |
I tried to do the same as for acurite.c where lot of decoders ... and for this one, no dot also at the end of the first line ... not a good example ... I was also wondering about that, now you confirmed my doubt. |
Relate to issue #3082