search

meshtastic / web

Meshtastic Web Client
https://client.meshtastic.org
GNU General Public License v3.0
204 stars 85 forks source link

[Bug]: Nothing happens after clicking ‘Connect’ on the device-served website #124

Open dm5tt opened 10 months ago

dm5tt commented 10 months ago

Category

Other

Hardware

T-Beam V1.1

Tested with 433 and 868 variant

Firmware Version

v2.2.0.9f6584b

Description

I just Web-flashed the latest 2.2.0.9f6584b Alpha onto my T-Beam (433 and 868MHz variant). After pressing the ‘Connect’ button on the website served by the device nothing happens.

A full device erase was done. Also cleaning out all browser caches. Browser logs (Developer mode) showing no error/warning. Tested with Firefox and Chrome.

Last known working version was V2.1.21 or V2.1.20.

Just tested the Android App against the IP - connects without problems.

Is there some known issue?

Thank you!

Relevant log output

No response

geeksville commented 10 months ago

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/nothing-happens-after-clicking-connect-on-the-device-served-website-2-2-0-9f6584b-alpha-t-beam/8005/3

dm5tt commented 10 months ago

I bisect'ed this twice and always ended up here:

1012167c893d5ced7540b59acea8a0bff654bf34 is the first bad commit
commit 1012167c893d5ced7540b59acea8a0bff654bf34
Author: Sacha Weatherstone <sachaw100@hotmail.com>
Date:   Sun Jul 9 14:14:49 2023 +1000

    Second round of formatting
ajmcquilkin commented 10 months ago

Just to clarify, does this issue happen on one connection method specifically? I'm on protos v2.0.0 alpha and I'm seeing this when trying to connect to a TBeam over USB Serial. Looks like it could be an issue with the JS library.

image

dm5tt commented 10 months ago

I only tested using the IP.

On the forum this issue was confirmed.

One person suggested a workaround: Marking the IP-Field then hitting enter. Works for me.

rcarteraz commented 10 months ago

I only tested using the IP.

On the forum this issues now way confirmed this.

One person suggested a workaround: Marking the IP-Field then hitting enter. Works for me.

I can confirm this as well.

daniel-hofer commented 10 months ago

I only tested using the IP. On the forum this issues now way confirmed this. One person suggested a workaround: Marking the IP-Field then hitting enter. Works for me.

I can confirm this as well.

I can confirm this too, the workaround did it for me.