My first hiccup using MAK Grills Mobile. Any other MGM users seen this?
Night before last I was grilling some salmon, running a simple program, monitoring it on my iPad. I had Probe 1 alarm set for 130 degrees.
Everything was looking great, probe temp was going up about a degree every couple minutes on display. Then it stopped at 128 degrees and didn't move. Timers were still running. No indication of connection loss. I stepped outside after an anxious several minutes and my Pellet Boss said Probe 1 = 140 (I validated this with Thermapen). iPad still said 128. WIFI signal 100%. Refresh of webpage caused no change to displayed temp.
Pulled the salmon with no harm done, but Ugh, what happened? This could spell doom for some poor piece of meat if I'm not paying attention...
In short, nothing wrong with probe or Pellet Boss. Connection was seemingly never lost. Program was still running, but probe data was not updating even with webpage refresh. No indication that anything was amiss.
All I can think of is that the probe data was either delayed getting to my iPad and would have eventually shown up correctly, or it was just dropped altogether. Perhaps an understanding of the path the probe data has to take will explain this, i.e. does it go like this (simplified, obviously):
grill -> router -> internet -> makgrillsmobile -> internet -> router -> iPad?
If so, then our poor probe data is at the mercy of Skynet, so to speak, and could get randomly delayed/dropped for any number of reasons on it's way to or from MGM. For longer cooks this may not be an issue, of course, as there is more margin for error. But, does this mean I gotta avoid MAK grills mobile on shorter cooks?
BTW, the salmon was still delicious like everything else I've made on the magic MAK.
Paul
Night before last I was grilling some salmon, running a simple program, monitoring it on my iPad. I had Probe 1 alarm set for 130 degrees.
Everything was looking great, probe temp was going up about a degree every couple minutes on display. Then it stopped at 128 degrees and didn't move. Timers were still running. No indication of connection loss. I stepped outside after an anxious several minutes and my Pellet Boss said Probe 1 = 140 (I validated this with Thermapen). iPad still said 128. WIFI signal 100%. Refresh of webpage caused no change to displayed temp.
Pulled the salmon with no harm done, but Ugh, what happened? This could spell doom for some poor piece of meat if I'm not paying attention...
In short, nothing wrong with probe or Pellet Boss. Connection was seemingly never lost. Program was still running, but probe data was not updating even with webpage refresh. No indication that anything was amiss.
All I can think of is that the probe data was either delayed getting to my iPad and would have eventually shown up correctly, or it was just dropped altogether. Perhaps an understanding of the path the probe data has to take will explain this, i.e. does it go like this (simplified, obviously):
grill -> router -> internet -> makgrillsmobile -> internet -> router -> iPad?
If so, then our poor probe data is at the mercy of Skynet, so to speak, and could get randomly delayed/dropped for any number of reasons on it's way to or from MGM. For longer cooks this may not be an issue, of course, as there is more margin for error. But, does this mean I gotta avoid MAK grills mobile on shorter cooks?
BTW, the salmon was still delicious like everything else I've made on the magic MAK.
Paul
