Control Hub Program & Manage network refuses connections

[corkranspPA]

Hi all -

Immediately after upgrading our Control Hub app from 5.2 to 5.3, we have become unable to connect to Program & Manage. The Control Hub SSID is visible and connectable, we can run Op Modes, change robot configurations, etc, we just can't connect to 192.168.43.1:8080 from laptops, the DS phone, or even from the Control Hub itself using an HDMI cable/KBAM.

The exact error depends on the browser you use, but always makes reference to the connection being "refused". In Chrome:

This site can’t be reached
192.168.43.1 refused to connect.
ERR_CONNECTION_REFUSED

I've attached a minute or two of RobotControllerLog.txt file - I backed up and erased the existing files, powered on the Control Hub and tried to connect on laptop and DS, then grabbed the logs. I saw a few lines referencing Program & Manage, but couldn't identify any answers from them:

11-15 16:30:08.995 1366 1628 V Robocol : received command: CMD_START_DS_PROGRAM_AND_MANAGE(10163)
11-15 16:30:09.002 1366 1627 I NetDiscover_ControlHubNameManager: Robot controller name: 7135-RC
11-15 16:30:09.022 1366 1627 V FtcEventLoop: sending p&m resp: {"appUpdateRequiresReboot":true,"deviceName":"7135-RC","ftcUserAgentCategory":"OTHER","isREVControlHub":true,"networkName":"7135-RC","passphrase":"Unavailable. Is WiFi on?","serverIsAlive":true,"serverUrl":"http://192.168.43.1:8080","supports5GhzAp":false,"supportsOtaUpdate":false,"timeServerStarted":"Dec 31, 7:44 PM","timeServerStartedMillis":2687298}
11-15 16:30:09.058 1366 1759 V Robocol : sending CMD_START_DS_PROGRAM_AND_MANAGE_RESP(278), attempt: 0
11-15 16:30:09.103 1366 1628 V Robocol : received command: CMD_INIT_OP_MODE(10170) $Stop$Robot$
11-15 16:30:09.108 1366 1636 I RobotCore: Attempting to switch to op mode $Stop$Robot$
11-15 16:30:09.138 1366 1759 V Robocol : sending CMD_NOTIFY_INIT_OP_MODE(288), attempt: 0

Let me know if anyone has encountered this before and/or if you have any solutions or workarounds. Thanks!

robotControllerLog11-15-20.txt

[NoahAndrews]

Thanks for making a clean log file. Your technique for that is very helpful, and should be replicated.

This is actually a known issue for the older Dragonboard-based Control Hub. Note that the Dragonboard version of the CH is not a part of the FTC Control Hub Pilot this year, and (I believe) is not legal for competition use (though you should ask on the official game Q&A forum).

That being said, I've been meaning to fix this issue anyway. Maybe I'll try to get it fixed soon.

[corkranspPA]

Thank you so much for that info; we had some suspicions along those lines and are already waiting for new hubs to arrive. I was climbing the walls over this, so it's a huge load off my mind knowing these new units should work correctly.

Thanks again!