System does not connect to local WIFI

1

Hi there,
looks like I am too stupid to bring the system into local WIFI (called “chanti” here).

What can I see:

  • System always ends in access point mode.
  • system interface is always in english, even if german is selected

What did I try:

  • I flashed with airRohr-firmware-flasher-0.3.2-Windows_amd64 and 0.3.4 as well.
  • used different binaries for flashing in en and de (in my case).
  • tried different WIFI networks. all support 5 GHz and 2,4 GHz, SSID and password are correct
  • played with distance to WIFI router…
  • used putty to get logs!
Restart.
▒▒airRohr: NRZ-2020-133/EN
mounting FS...
opened config file...
parsed json...
output debug text to displays...
Connecting to chanti
........................................
output debug text to displays...
Starting WiFiManager
AP ID:
Password:
scan for wifi networks...
AP Password is:
Starting Webserver... (IP unset)

So it looks like system tries to connect to WIFI but somehow fails. I can’t see the reason. (even increasing debug level to values bigger 3 does not extend info)

Can some please provide a hint what I can do?

Thanks in advance,

Danny

2

Update:

  • Removing sensor connections (temperature and particle) does not change behaviour (I did not expect but at least it was a try)
  • giving a WIFI password known as wrong does not lead to any change in putty logs…
  • create guest network @ 2,4 GHz (named GST) without any access restriction or password. selected this network in user interface of NodeMCU but the result is the same

Restart.
▒▒airRohr: NRZ-2020-133/DE
mounting FS...
opened config file...
parsed json...
output debug text to displays...
Connecting to GST
........................................
output debug text to displays...
Starting WiFiManager
AP ID:
Password:
scan for wifi networks...
AP Password is:
Starting Webserver... (IP unset)
3

after leaving system alone for some minutes sensors seems to work but still no connection to WIFI

PM10 (sec.) : 1.10
PM2.5 (sec.): 0.80
/R SDS011
R/ SDS011
PM10 (sec.) : 1.30
PM2.5 (sec.): 0.80
/R SDS011
R/ SDS011
PM10 (sec.) : 1.20
PM2.5 (sec.): 0.80
/R SDS011
R/ SDS011
PM10 (sec.) : 1.20
PM2.5 (sec.): 0.80
/R SDS011
R/ SDS011
PM10 (sec.) : 1.10
PM2.5 (sec.): 0.80
/R SDS011
R/ SDS011
PM10 (sec.) : 1.10
PM2.5 (sec.): 0.80
/R SDS011
PM10:  1.15
PM2.5: 0.80
----
## Sending to sensor.community - SDS011
R/ BME280
Temperature (°C): 22.55
Pressure (hPa): 94083.50
Humidity (%): 43.24
----
/R BME280
## Sending to sensor.community - BME280
## Sending to madavi.de:
Time for Sending (ms): 0
Connection lost, reconnecting
...............
4

Did you try to persist? Like 4-5 attempts in a row.

1 Like
5

I let it run the whole night with several resets in between. Since there was no success I reflashed system with airRohr-firmware-flasher-0.3.4-Windows_amd64_BETA used latest_de.bin → airRohr: NRZ-2020-133/DE

Additionally I activated guest network @ 2,4 GHz for a while to “stabilize” (even if this would not make any difference in my understanding)

Fortunately I am a step further now:

airRohr: NRZ-2020-133/DE
mounting FS...
opened config file...
parsed json...
output debug text to displays...
Connecting to GST
....SNTP synced: Thu Mar  9 19:02:45 2023

twoStageOTAUpdate
output debug text to displays...
.
WiFi connected, IP is: 192.168.1.126

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Exception (28):
epc1=0x4000bdc8 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000

>>>stack>>>

ctx: cont
sp: 3ffffd30 end: 3fffffc0 offset: 0190
3ffffec0:  00000003 00000000 3ffef4b0 3fffff10
3ffffed0:  3fffff48 00000050 3fffff10 3ffef27f
3ffffee0:  3ffe8939 3ffe8934 3ffef4b0 40218194
3ffffef0:  3ffe892b 3ffe8930 3ffef4b0 4020ab58
3fffff00:  00000040 00000000 feefeffe feefeffe
3fffff10:  70747400 000d0000 80201b44 402013cc
3fffff20:  feefeffe feefeffe feefeffe feefeffe
3fffff30:  feefeffe feefeffe feefeffe feefeffe
3fffff40:  feefeffe feefeffe 00706300 7e01a8c0
3fffff50:  80efeffe 00000000 00000000 feefeffe
3fffff60:  feefeffe feefeffe feefeffe feefeffe
3fffff70:  feefeffe 01004544 feef010d feefeffe
3fffff80:  3ffeea31 feefeffe feefeffe feefeffe
3fffff90:  feefeffe feefeffe feefeffe 3ffef6a8
3fffffa0:  3fffdad0 00000000 3ffef668 40223240
3fffffb0:  feefeffe feefeffe 3ffe8690 401006c9
<<<stack<<<

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Now I need to figure out what causes this exception...
6

Is it a Wifi 6 access point? If yes, what happens If you only use use a b/g/n mode?

1 Like
7

In fact it is. So I went into cellar, there a wifi router with older standard is available. I configured it to “mixed 802.11 g/n”. Unfortunately this change did not lead to any improvement! :frowning:

8

can you ping the ip address of the router?

1 Like
9

from where? local PC or NodeMCU?

10

Hi @Danny
You wrote “…giving a WIFI password known as wrong does not lead to any change in putty logs…”. I know it sounds stupid, but you might have put in a wrong password all the time. Maybe a change on the router? Just double check. I had this kind of situations, when I was 100% sure about a password and tried everything, before checking the password on the router again.

Comment #5 would support that thought. You’ve tried a new guest access point and that worked, right? At least it synced SNTP and says WiFi connected, IP is: 192.168.1.126. Is the WiFi problem solved?

11

As I even do not trust myself I copy-pasted it into Notepad++ from webinterface of router… :slight_smile:

The issue is solved since I changed the WIFI (the one in cellar is using a different WIFI router). I still can’t access WIFI with my newer WIFI 6 router. This does not hurt me since the sensor is working now but from a technical perspective this is not satifying :slight_smile:

BR,
Danny