New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sensor verbindet sich nicht mit meinem Wlan #346
Comments
Two questions: Does your WLAN by any chance have a space in its SSID? Have you tried switching off 5Ghz on the AP temporarily to test? You can review WLAN errors via serial monitor. See end of this article https://github.com/opendata-stuttgart/meta/wiki/Firmware-einspielen |
Thanks for bringing up that article. No, there is no space in the wifi SSID. And yes, I tried swithing of 5Ghz with the same result. I looked at the log via serial monitor and this is how the output reads out: Any chance you can help me interpreting it? ---- Result from Webconfig ----
|
Could you please send the characters used in the wifi password? |
Sorry for the late response... Yes, my network is listed on the config page. My wifi password contains some letters, two numbers, "!" and "_". This weekend I will have time to do some more troubleshooting and will report afterwards. |
Ok so I renamed my two networks and changed the password but still was not able to connect. |
Have you checked your wifi router that there are no limitations (MAC filter, guest wifi settings, time limitations) for 'new' devices? |
hi again, |
You need a capture of the Wifi Messages to confirm, but I think it is most likely related to short guard Interval being enforced on the Router and the ESP lacking support for that. |
hello, I have the same exact problem with the same exact model TG3442DE |
As I said before.... What does the Wireshark capture say? |
The sensor only supports 2.4 GHz wifi. And the sensor seems to prefer 811.2n (my Fritz!Box is set to 811.2b+g+n). |
I have a similiar problem with a Vodafone EasyBox. I also tried to check with Wireshark and see a DHCP Discover package from the MAC address of the controller. It also shows up on the router but does not get an IP assigned. So I think it is mainly a DHCP issue. Would be great to have possibilities to set the IP instead of relying on DHCP for such cases. Not sure if it helps but I would hope. I added now a FritzBox to my Wifi and was able to connect through it but would for sure love to only need one access point (Vodafone EasyBox) |
Same problem here: |
Does the affected WLAN-accesspoint require some sort of "minimum basic-rate" which might be greater than 1 Megabits/s? Or has some special options like "power-saving" (Unscheduled Automatic Power Save Delivery, U-APSD)? Does it allow WPA1 and WPA2, or just one of these? |
It is possible (I can't verify) that the wifi access point needs to support at least 802.11n. is it possible that the users with issues here are trying to connect to an AP without such support? |
Google points to https://forum.vodafone.de/t5/Internet-Ger%C3%A4te/ESP8266-verbindet-sich-nicht-mit-TG3442DE/td-p/1974080 not sure if the answer given here is correct though (I can still connect if I turn off on my 802.11n capable router the 802.11n feature) |
@dirkmueller It's most likely this. Unfortunately the Vodafone issued routers are built for idiots and don't offer any kind of settings to the user. You can't even change the wifi channel nor the dhcp settings in there. So theres probably not much that users of that router can do (other than setting up an external wifi router for the ESPs) |
I think I was facing the same problem as you guys did, but now my esp8266 is working with my router:
the simple fix was: |
If this should work then the next firmware release should solve this. We are waiting for the last feedback for some changes. |
Hallo in die Runde,
ich habe mir einen Feinstaubdaten-Sensor gebaut und schaffe es einfach nicht, ihn mit meinem Wlan zu verbinden.
wenn ich mit dem Handy einen Hotspot erstelle und im Sensor die entsprechenden Login-Daten eingebe, verbindet das Gerät korrekt und die Messdaten sind unter https://www.madavi.de/sensor/graph.php?sensor=esp8266-3871409-sds011 einsehbar. Im Handy taucht er als "ESP_3B12B1" bei den verbundenen Geräten auf.
wenn ich in der Sensor-Konfiguration die Daten meines heimischen Wlans eingebe, erscheint der Sensor nicht mehr als Hotspot und im Router-Menü erscheint der Eintrag "unknown" bei den verbundenen Geräten. Allerdings erscheint er auch nach längerem Warten nicht unter https://www.madavi.de/sensor/graph.php. Auch unter dem Link http://feinstaubsensor-3871409.local/ kann ich nicht auf ihn zugreifen.
Ich habe ein 2,4Ghz und ein 5Ghz Netz mit selber SSID. Der Router ist ein Arris TG3442DE (Vodafone vermarktet ihn als Vodafone Docsis 3.1).
Könnt ihr mir helfen? Ich weiß nicht, wie ich das Problem weiter eingrenzen kann.
Danke und viele Grüße
Jakob
The text was updated successfully, but these errors were encountered: