Thermoworks RFX First Impressions

[schlotz]

Hmm... not much correlation regarding serial numbers

 

[SmoqueBBQ]

I'm curious too. My probe that is lasting around 8 hours was one of the first shipped, it was part of a starter kit that shipped on October 21st. The one that has been going for 22 hours and is still at 60% was a single probe shipped on November 6th. The serial numbers are about 9,500 apart.

It's possible the first batches were not as good. Mine are 7177, 7088, 7089, 7090. I have my second order showing up in a week or two so I'm curious to see how those do.

 

[schlotz]

As of this morning the latest Gateway firmware is 1.1.29-46. I upgraded to this yesterday afternoon but was expecting another by this morning. Maybe TW did get the latest out on Friday like the Tech eluded to?

Ok, started the probe battery life test about 30 min ago. We'll see.....

Interesting: Probe one down to 80% after 3 hours which was the same with ver 1.1.28-45. Probe 2 still at 100% same as before.

 

[jimboc22]

I'm curious too. My probe that is lasting around 8 hours was one of the first shipped, it was part of a starter kit that shipped on October 21st. The one that has been going for 22 hours and is still at 60% was a single probe shipped on November 6th. The serial numbers are about 9,500 apart.

I left that second probe running after the first one died around 8 hours, it's still going this morning with 10% battery left. I'm running gateway firmware 1.1.29-46 and the probes' firmware are 1.2.1. Here are my serial numbers for reference.

Probe 1, 1 degree intervals, ~8 hours, M100006047
Probe 2, 3 degree intervals, ~46 hours (so far), M100015574

 

[bwana_don]

I left that second probe running after the first one died around 8 hours, it's still going this morning with 10% battery left. I'm running gateway firmware 1.1.29-46 and the probes' firmware are 1.2.1. Here are my serial numbers for reference.

Probe 1, 1 second intervals, ~8 hours, M100006047
Probe 2, 3 second intervals, ~46 hours (so far), M100015574

Wow! That is really in getting to as advertised.
I think you meant 1 degree interval.
My testing showed no difference based on settings on the probes. Wonder if it is being hidden by questionalable batteries or something else with the probes.
Would be curious to see what your probe 2 - M100015574 would do with 1 degree interval. That would be really telling.

Next thing I am trying to understand is if we are only getting pushes from the RFX-Gateway to the cloud once a minute. Is that frequent enough for watching a sear?

Don

 

[cwood]

Wow! That is really in getting to as advertised.
I think you meant 1 degree interval.
My testing showed no difference based on settings on the probes. Wonder if it is being hidden by questionalable batteries or something else with the probes.
Would be curious to see what your probe 2 - M100015574 would do with 1 degree interval. That would be really telling.

Next thing I am trying to understand is if we are only getting pushes from the RFX-Gateway to the cloud once a minute. Is that frequent enough for watching a sear?

Don

It would be odd if "cloud" were used for anything other than remote viewing or connection to control when far from the gateway. When local to the devices like when actively working the cook, I would think / hope that data goes probe to gateway to mobile device.

 

[bwana_don]

It would be odd if "cloud" were used for anything other than remote viewing or connection to control when far from the gateway. When local to the devices like when actively working the cook, I would think / hope that data goes probe to gateway to mobile device.

thanks, that makes sense! Wish their documentation had a few more details...

 

[bwana_don]

With that last realization from cwood, I will be starting my tests over, all 4 thermometers set to the same temperature interval of 3 and working my way down. That should identify battery differences between the serial numbers fairly quickly.

 

[schlotz]

If I understand the degree setting it would additionally report within the 60 second interval if the degree setting is hit. Testing with ambient sensor at the end on the probes i.e. just sitting on the counter top, only the 60 second intervals are reported.

UPDATE on my testing: 8 hrs in, probe #1 down to 40%, probe #2 still at 60%

 

[bwana_don]

It would be odd if "cloud" were used for anything other than remote viewing or connection to control when far from the gateway. When local to the devices like when actively working the cook, I would think / hope that data goes probe to gateway to mobile device.

As I check my current test, I am looking at my phone and my laptop. Assume the phone is considered local, on the wifi, and my laptop is getting the data from the cloud. They are updating at the exact same time. I have my setting at the temperature-based interval of 3 degrees.

1. There does not appear to be a difference between cloud and wifi frequency reporting.
2. The update frequency is every 3 minutes for both.

Does this mean the interval setting is not temperature based?
Early videos from this summer showed it as time based but had settings down to 1 second for searing.
Also wondering about my previous tests now, if each probe has a different setting and it is time based, does it default to the lowest common denominator for all probes? That is what the detailed readings for each session seems to indicate.

I guess I will be reaching out to TW for some clarification.

Don

 

[jimboc22]

I think you meant 1 degree interval.

Yep, I meant degree. Thanks, I'll update it to avoid confusion.

Would be curious to see what your probe 2 - M100015574 would do with 1 degree interval. That would be really telling.

What the heck, maybe I'll do that next.

I'm not home right now. But just checked the app. Probe 2 is still going with 10% left. It's passed the mythical 50 hour mark.

 

[cwood]

As I check my current test, I am looking at my phone and my laptop. Assume the phone is considered local, on the wifi, and my laptop is getting the data from the cloud. They are updating at the exact same time. I have my setting at the temperature-based interval of 3 degrees.

1. There does not appear to be a difference between cloud and wifi frequency reporting.
2. The update frequency is every 3 minutes for both.

Does this mean the interval setting is not temperature based?
Early videos from this summer showed it as time based but had settings down to 1 second for searing.
Also wondering about my previous tests now, if each probe has a different setting and it is time based, does it default to the lowest common denominator for all probes? That is what the detailed readings for each session seems to indicate.

I guess I will be reaching out to TW for some clarification.

Don

Also keep in mind that it is a VERY tiny amount of data by internet connection and bandwidth standards of the day so cloud posting of the same values may seem simultaneous.

 

[Fraser]

It would be odd if "cloud" were used for anything other than remote viewing or connection to control when far from the gateway. When local to the devices like when actively working the cook, I would think / hope that data goes probe to gateway to mobile device.

Don’t think that’s the case. At present, the Gateway doesn’t ‘speak’ bluetooth. Wi-fi is currently required (stay tuned). Probe to Gateway (to wi-fi) to Cloud then device.

 

[schlotz]

Well the results of the 3rd test using the latest Gateway firmware 1.1.29-46 were disappointing. Actually they took a slight step backwards from the previous version which achieved 17+ hours of battery life.

Probe-1 (#6334) lasted 15hrs 2min, Probe-2 (#8258) lasted 15hrs 19min. I'll call TW on Monday to report. Starting to think these specific 2 probes are defective. FYI the gateway was plugged in for the test duration and probes were sitting on the desk.

 

[jimboc22]

Well, some probes do have the potential to go the distance with FW 1.1.29-46. Probe M100015574 lasted 56 hours and 21 seconds.

I'll be patient through one more firmware update, and if that doesn't fix the earlier probe, I'm going to request that they replace it.

 

[bwana_don]

Well the results of the 3rd test using the latest Gateway firmware 1.1.29-46 were disappointing. Actually they took a slight step backwards from the previous version which achieved 17+ hours of battery life.

Probe-1 (#6334) lasted 15hrs 2min, Probe-2 (#8258) lasted 15hrs 19min. I'll call TW on Monday to report. Starting to think these specific 2 probes are defective. FYI the gateway was plugged in for the test duration and probes were sitting on the desk.

I am in the middle of my second test on 1.1.29-46.

First test 4 probes set to 1, 1.5, 2, and 3. Readings and changes on the app for temperature were showing up every minute for all probes, I was able to verify by looking at the history of the sessions. The only exception was the first 2 minutes where there were many readings. Battery life ranged from 14.32 - 23.23 hours.

2nd test I am at 23 hours, all probes are set to 3 (temperature interval setting???). One probe is at 80%, the other 3 are at 60%. Readings/last seen are coming in every 3 minutes for all probes. I can verify that by drilling down on the chart and looking at the intervals on the chart using the web interface. Cant look at detailed history until the sessions end. Based on what I am seeing now, I expect all the probes in this test will reach 50+ hours. By far the longest I have seen.

My speculation at this time and it is only speculation - is they have provided a work around to so that we can see longer battery life and it is based on time and not on temperature interval. For some reason that work around does not respect individual probe settings and my first test caused them to all act like they were on a setting of 1 (reporting at 1 minute). Or it could be I turned on probe 1 with a setting of 1 first and that set the setting for all, or guess your best.

My next test (test 3 for 1.1.29-46) will be all probes set to 1, if my speculation is correct, I will see batterly life that mirrors test 1 - reasonably similar in times for each probe. I definitely have two probes that do not seem to last as long as the other two, I expect that to show consistent diffence when all probes are set to the same.

The good and the bad, the current test will not end until late tomorrow based on current battery %'s. The bad I can't start the next test, I could also throw in a quick test and see if the order in which the probes are started with and having different settings makes a difference.

 

[Fraser]

they have provided a work around to so that we can see longer battery life and it is based on time and not on temperature interval.

From my conversation with TW, the RFX has a ‘heartbeat’ in addition to the TBTI. When asked if this isn’t redundant to the TBTI the answer was yes and would be eventually phased out to become totally delta-T triggered. I suspect this is was a residual artifact from development. When the RFX becomes solely TBTI-triggered, you’ll likely see battery life skyrocket.

 

[SmoqueBBQ]

Don’t think that’s the case. At present, the Gateway doesn’t ‘speak’ bluetooth. Wi-fi is currently required (stay tuned). Probe to Gateway (to wi-fi) to Cloud then device.

I was curious about this so I just tested it and you are correct.

I blocked the RFX Gateway from my Wi-Fi through my Unifi UDM. Once I did, the temp updates stopped, even though I connected to the Gateway with Bluetooth to my phone via the Gateway settings prior to disconnecting the Wi-Fi.

Once I unblocked and reconnected the RFX Gateway to the Wi-Fi the temp updates resumed.

Based on that it appears the data path goes RFX Meat - RFX Gateway - Cloud - Device. There doesn't seem to be a path to the phone or app without going to the cloud.

In my commercial environment having Wi-Fi isn't an issue, but for someone who wants to use it as a stand-alone temperature probe in a remote environment without Wi-Fi it would be a problem.

 

[jimboc22]

From my conversation with TW, the RFX has a ‘heartbeat’ in addition to the TBTI. When asked if this isn’t redundant to the TBTI the answer was yes and would be eventually phased out to become totally delta-T triggered. I suspect this is was a residual artifact from development. When the RFX becomes solely TBTI-triggered, you’ll likely see battery life skyrocket.

This should have been 'phased out' before release. I feel like the pre-orders ended up being their beta testers. Don't get me wrong, I love Thermoworks but the roll out of this product has been botched every step of the way. I held off on purchasing the meater and other wireless probes because I knew that one day they would release their own version that would be better than any of the other options out there.

Their tech support has been top notch up to this point (most companies won't respond to emails or phone calls, or just plain give you the run around), which is the main reason I continue to support them as a company. I'm confident they will resolve the issues we've experienced, whether it be app/FW updates or replacements.

 

[schlotz]

I am in the middle of my second test on 1.1.29-46.

First test 4 probes set to 1, 1.5, 2, and 3. Readings and changes on the app for temperature were showing up every minute for all probes, I was able to verify by looking at the history of the sessions. The only exception was the first 2 minutes where there were many readings. Battery life ranged from 14.32 - 23.23 hours.

2nd test I am at 23 hours, all probes are set to 3 (temperature interval setting???). One probe is at 80%, the other 3 are at 60%. Readings/last seen are coming in every 3 minutes for all probes. I can verify that by drilling down on the chart and looking at the intervals on the chart using the web interface. Cant look at detailed history until the sessions end. Based on what I am seeing now, I expect all the probes in this test will reach 50+ hours. By far the longest I have seen.

My speculation at this time and it is only speculation - is they have provided a work around to so that we can see longer battery life and it is based on time and not on temperature interval. For some reason that work around does not respect individual probe settings and my first test caused them to all act like they were on a setting of 1 (reporting at 1 minute). Or it could be I turned on probe 1 with a setting of 1 first and that set the setting for all, or guess your best.

My next test (test 3 for 1.1.29-46) will be all probes set to 1, if my speculation is correct, I will see batterly life that mirrors test 1 - reasonably similar in times for each probe. I definitely have two probes that do not seem to last as long as the other two, I expect that to show consistent diffence when all probes are set to the same.

The good and the bad, the current test will not end until late tomorrow based on current battery %'s. The bad I can't start the next test, I could also throw in a quick test and see if the order in which the probes are started with and having different settings makes a difference.

Don, what are you doing to limit the reading to 3 minutes? All of mine consistently repot once a minute.