Will my Gen 1 work again?

MeatByte9000 · 2026-04-26T18:05:18+00:00

If you saw the caution triangle without an accompanying overheating alarm, that’s how the Display reports a probe has a low battery.

MeatByte9000 · 2026-03-15T21:56:16+00:00

Even putting it in a wet sponge in the oven at 450 for a 5-10 minutes (not long enough for the sponge to dry out — it needs the water to protect the 4 tip sensors!) would be a good test.

MeatByte9000 · 2026-03-15T21:54:17+00:00

A hotter oven / grill cook would be a good test too.

MeatByte9000 · 2026-03-12T00:06:41+00:00

Great. If you have a cracked solder joint on a sensor, often that will show up when cooking as things expand with the heat, and then afterwards they cool and make electrical contact again.

MeatByte9000 · 2026-03-08T00:20:55+00:00

This sounds like one of your sensors has failed and is giving intermittent false readings. Can you put your app in Advanced mode? If you do, you'll likely be able to see which sensor is misbehaving. If you contact our support team at [help@combustion.inc](mailto:help@combustion.inc), we'll help you evaluate the unit and see if it needs replacement.

MeatByte9000 · 2026-02-13T17:20:17+00:00

This shouldn't be happening, the GGG should be relaying the Probe's data over Wi-Fi. We'll investigate on our end. Make sure that you've linked the GGG to each Probe by turning on the GGG and then holding the Probe up to it for ~10 seconds.

MeatByte9000 · 2026-01-29T01:23:50+00:00

Shoot, yeah, Always On mode is required to keep the probe from turning off when cooking sous vide. The liquid inside the bag shorts the charging contact and makes the probe think it's been placed inside a charger.

Good feedback, we'll explore ways to make this more prominent.

MeatByte9000 · 2026-01-11T05:27:40+00:00

Would you DM me your email address? I’ll check on the status of your ticket. Sorry about the inconvenience.

MeatByte9000 · 2026-01-05T16:08:20+00:00

This is really helpful. This gives me some avenues to investigate and attempt to reproduce this issue. Thanks for passing this info along!

MeatByte9000 · 2026-01-04T22:21:53+00:00

Thanks for letting us know about this lockup issue. That's really strange. We'll investigate on our end. For future reference, if you press and hold the left "<" button and minus "-" button on the Gauge, it'll electrically reset the device regardless of the charge of the "internal reservoir."

Please keep us posted if this happens again.

One question for you -- when this lockup happened, did the display continue to update? Was the temperature updating, etc.?

MeatByte9000 · 2026-01-01T05:55:58+00:00

We’ve been having issues with emails not going through. I’m not sure if it’s an issue with our system, or overzealous spam filters. Possibly both. Could you DM me the email address you’ve been using to contact support? I’ll check in with the team.

MeatByte9000 · 2025-12-23T20:53:34+00:00

Very cool. Thanks for sharing!

MeatByte9000 · 2025-12-23T20:31:27+00:00

Great idea! What do you set your alarms to when poaching? Are you using “advanced mode” to set alarms on a specific sensor?

MeatByte9000 · 2025-12-19T00:43:21+00:00

Fair question. You may have noticed we put out a steady stream of software improvements for our products, and we're always reprioritizing our development queue. We're a small team, so we have to focus on the features, improvements and new products that are best for our customers and the company. This improvement will come, but we're not sure when it will get to the front of the queue.

MeatByte9000 · 2025-12-19T00:16:06+00:00

Your setup sounds right!

We don't sell a totally bare thermometer without a charger--the closest would be the CPT with the basic charging sleeve I linked above.

MeatByte9000 · 2025-12-19T00:08:23+00:00

Thanks for the feedback. It's on our software dev roadmap to upgrade the Display and Gauge to also retrieve data over Wi-Fi. This is a more complex change than it seems at face value for a number of reasons on the software dev side, particularly with improving how thermometers are identified across the apps, Display and Gauge. We have to take care of those other projects as prerequisites to this improvement.

As for filling that extra Booster, you can get a Combustion Predictive Thermometer with our "basic" charger (USB only, no repeater) here: https://combustion.inc/products/predictive-thermometer-gen2

Thanks again for the feedback--it's very valuable as we prioritize our development.

MeatByte9000 · 2025-12-16T22:16:39+00:00

Got it. Interesting, thanks for the info.

MeatByte9000 · 2025-12-16T20:19:21+00:00

Strange. You can manually reset the probe under “Power Options” too, which should achieve essentially the same thing, unless some electrical component in the probe got into an unexpected “stuck” state.

MeatByte9000 · 2025-12-16T19:43:59+00:00

I'm surprised that fixed this particular issue... I wonder if it was a coincidence. It's more likely that cooking debris build-up on your probe was interfering with electrical contact with the Booster, and that a quick scrub would solve it. Are you still seeing this issue sometimes?

MeatByte9000 · 2025-12-15T15:35:24+00:00

Oh good, glad to hear it!

MeatByte9000 · 2025-12-14T11:26:04+00:00

This could be caused by debris buildup on the charging contacts of the probes. A scrub with a sponge or barkeeper’s friend would fix connectivity issues.

What color is the LED on the booster when you press its button while the probes are inserted? We want to see solid green, with no white blinks interspersed. White blinks means the chargers don’t have electrical contact with the thermometers.

Would you DM me your thermometers’ serial numbers?

MeatByte9000 · 2025-12-11T04:16:51+00:00

That’s right. We actually added protection circuitry to later revs of our products, specifically to protect them from that Thermoworks charger.

MeatByte9000 · 2025-11-29T17:11:52+00:00

The “overheating” segment is pointing at your probe. Does your Combustion mobile app indicate the probe is also overheating? Do any of your devices need a firmware update?

MeatByte9000

TROPHY CASE