Meshtastic Web serial setup stalls on Heltec V3 in Chrome

A Heltec V3 can look healthy in Meshtastic Web and still fail at the finish line. In GitHub issue #1060, ALMASSARO reported that on Windows 11 with Chrome, the serial port showed up in Device Manager and the software appeared connected, but the timer never stopped and configuration never completed.

The failure was specific enough to matter. The report involved Serial over USB, with the node reached through meshtastic.local, and the console threw TypeError: Cannot read properties of undefined, reading num. That points away from a dead radio, a bad cable, or a missing COM port and toward a front-end bug in the browser client itself. The setup gets far enough to look alive, then stalls before the node can finish onboarding or move on to normal messaging work.

That distinction is the whole story here. Meshtastic Web is built to run directly in the browser, with a hosted version at client.meshtastic.org and a self-hosting option. The official docs recommend Chromium-based browsers such as Google Chrome or Microsoft Edge for the best experience, but they also note that Serial over USB has the least platform support because it relies on the Web Serial API. In other words, this is exactly the path where a browser-side regression can leave users staring at a connection that never quite becomes usable.

The pattern is not new. A September 12, 2025 report, issue #846, described Windows 11 setups in Chrome, Brave, and Edge where the Meshtastic page showed a spinning loading circle that never cleared. In that thread, a Meshtastic collaborator said the problem was always caused by multiple simultaneous connections to the same mesh device and told users to disconnect other devices and close browser tabs. An even earlier April 2024 issue, #186, described another case where the client connected but stayed on Loading and never exposed channels or configuration tabs.

For anyone trying to bring up a Heltec V3 right now, the practical read is blunt: if Chrome shows a port, the UI acts connected, and the timer never clears, treat it as a Meshtastic Web failure first, not a miswired radio. Keep the session down to one browser tab and one active connection, and if the browser still hangs at the same point, the browser is the part that stalled, not the hardware.