I was going to add this to one of the many WiFi threads, but this isn’t an issue, so much as a logic gap that I’m hoping someone can explain.
The newest iteration of the app has allowed me to connect my mobile to my APC again. Yay?! Maybe. If nothing else it will let me sneak a peek at progress from a remote location. And that is where the logic gap comes in…
Now, to set up the APC to communicate via WiFi one’s mobile device and the APC need to be registered on the same 2.4 gHz WiFi network. That makes sense. All good.
Once the connection is established one can then go a-minstrel-o and look in on the APC from any location where one has a WiFi connection. Any WiFi network connection to the net. I’ve been told it’s any location with mobile phone coverage, but that has not been my experience.
But, upon returning back to home base one suddenly needs to be back on the same 2.4 gHz WiFi network again to communicate with the APC. This is what doesn’t make logical sense to me. If I can communicate with the APC via any available network while I am away from home, then I should be able to communicate with the APC while my phone is attached to the 5.0 gHz network at home surely.
What am I missing here?
I don’t have a Wi-Fi model so I can’t check this myself. What is telling you that you need to be on the same 2.4 GHz network as the APC post-setup? The app itself?
Experience. My phone can’t see the APC until I manually move it from the 5.0 GHz to the 2.4 GHz. Mind you, everything that I’ve seen written anywhere states that the two devices have to be on the same network, but I always figured that was only for initial setup.
The only reason that the APC has to be on the same 2.4GHz network is that’s how it learns your network during setup. After that, no, it doesn’t matter what data path you take.
The reason being is that, once the APC has that connection, it connects back to the Anova cloud from your home internet. Thereby, anywhere that you are that you have a data path to the internet (cellular or wifi) you should be able to communicate with your APC with the app.
The app isn’t the most robust when you change from one wifi frequency to another - so if you’re going to do that, I’d close the app first (you don’t need to rediscover your APC, just restart the app).
If you can’t connect to the APC when your phone is on 5GHz - can you connect to it just over cellular?
The APC can’t do 5GHz at all - it doesn’t have a 5GHz wifi radio.
That’s what I would’ve expected, but I can’t connect to the Anova unless I move my phone back to the 2.4 GHz network. Nor have I been able to every communicate with it while on a mobile network. And yes, I have mobile data switched on on my phone.
Hmm. So, either there’s something messed up in your Anova cloud connection (on their side) or there’s something in your router that’s not allowing the connection to Anova.
The last time you setup wifi, was it easy? (just because I’m going to suggest that you reset the APC back to factory settings and do the setup again to see if that fixes it).
You could always contact support and see what they’re seeing in the infrastructure as well.
I’ve had WiFi oddities since day 1. Just look through forum history for WiFi fun. Connects but dumps during cook etc etc. Not able to see the Anova from outside the network.
Have recently upgraded my internet connection and with that had to get a new modem. I set the 2.4 GHz network up identical to the old one to make my life easier. Had been unable to get the Anova to connect at all until the update before last. With the phone connected to the 2.4 GHz network it at least saw the Anova for the first time in ages… then went into the blinking on and off routine.
The newest version of the app seems to be stable. But I haven’t done much poking around yet.
I might uninstall it and see if a clean install clears the problem of having to be on the 2.4 GHz network.