Client 62 means that you should ensure that the wretched CONNECT app is not active in your smart mobile device.
I advise that you dump the Pods. They will always give you grief because they cannot work without the wretched CONNECT app.
Hi @JoeL4,
Thank you for your post and welcome to our community forums. We're here to help.
I'm so sorry to hear you're having some trouble with your Hub 4's Wi-Fi service along with connecting it to the Connect App. Is this ongoing today? If so, have you tried removing and then reinstalling the app? Can you also confirm if your wired connection is also impacted at all?
Thanks,
Zach - Forum Team
New around here? To find out more about the Community Forums, take a look at our FAQs!
This can't be difficult to fix. It requires the COONEXT app, a Hub 4, a deep dive on CONNECT app code (with diagnostic traps turned on) until they've solved it. It gets more challenging if the firmware needs to be amended but I would have thought that mitigating code could be put into the wretched CONNECT app.
Zach's suggestion isn't gonna work. I know you'll try it because he's asked for it - but I'm sure your hopes aren't high. It might improve if they give you a Hub 5 instead of the Hub 4 - but that Hub has its current share of problems too, none-the-least with DHCP operations.
If you're not using VM's stupid Pods, then it's best to delete the wretched CONNECT app so that it cannot screw your router up. Power Reboot the Hub and you should have access to the Hub's GUI. You can control everything from there. The fancier features of the wretched CONNECT app can be ignored - as they are by the tens of thousand who are wise the wretchedness of that app. Good idea, crap delivery by VM and even crappier support because this has been going on for months.
If you do have Pods, send them back to VM as not fit for purpose because of the wretched CONNECT app. Seriously. Installing your own mesh WiFi system, free from the stupid ties that VM impose with their stupid Pods may cost you a bit of dosh. But you won't look back in regret over such a wise move.
Me? What do I use with my Hub 4? Modem mode, may own router and mesh. It minimises use of anything VM have produced and simply enjoys the excellent broadband circuit performance.
My whatsit's a kipper if anyone reasonable disagrees with me.
@pineman wrote:'My whatsit's a kipper if anyone reasonable disagrees with me.'
Not disagreeing with you but removal of VM Connect and a Power Reboot made no difference and certainly didn't give me access to the Hub GUI like I used to get with the Hub3.
As you rightly say it's been an issue for a long time but not all of the 'Forum Team' seem to be aware.
That's disappointing. When I put my Hub 4 into router mode a few weeks ago to try out what I have been advising, I installed the wretched CONNECT app and sure as eggs, the Hub 4 GUI was inaccessible. I removed the wretched CONNECT app from my iPhone, rebooted the Hub 4 and voila, GUI was available. Of course, then straight back to modem mode.
