RF Bridge fails to connect to wifi

[Peter Goderie]

Today I flashed a Sonoff RF-Bridge with tasmota.bin  v8.3.1, using tasmotizer.

It came up as access point and I uploaded my default config file as I do usual with all new tasmota devices.

After that it does not connect to the network and does not show up as access point either.

The serial log shows repeatedly:

00:08:52 WIF: Connecting to AP1 PeeGee-Wifi1 in mode 11N as tmNewDevice...

00:09:04 WIF: Connect failed with AP timeout

I tried erasing+reflashing several times and tried configuring via tasmotiser and web interface. All with the same result.

Anybody any idea what is going wrong and/or how to solve this ?

[Phil]

reflash imho,  otherwise if you use something like the arduino ide serial monitor you may be able to send the ap setting commands via serial, (never managed to get putty to input tho..)

not expected behaviour even if you made a typo when providing credentials you shold be able to start the AP and it should automatically offer it up on a wifi connect failure too iirc??  

[Peter Goderie]

I tried reflashing already several times.

I'm sure that the configured credentials are OK. When, deliberately, entering the wrong credentials the AP comes up. With the right credentials continuous "Connect failed with AP timeout" and no AP.

[Phil]

Most Odd initial success in hosting the AP for wifi credential input indicates wifi works OK i have had the occasional no wifi device.. 

You did switch back the serial line to talk to the rf chip too? I doubt this is relevant but may introduce side effects?

Mind just wandering now..

possible network limitations??  is your network dhcp server or wifi at its client limit ?  some older kit designed pre iot will limit domestic equipment to serving 20 or so clients, 

an old isp supplied router can often be set up as an alternative ap to test for coms h/w or system conflicts..rare but if dismissed without checking, well you can guarantee will be your issue.. 

[Peter Goderie]

Yes I did turn the switch back to the ON position.

Network limitations not likely, currently just 24 devices on an ASUS RT-AC88U router, and other additional devices (laptop, tablet etc.) still connect OK.

But I just discovered a strange thing: The rf bridge connects to my guest network (via an old ubee router) without problem (though in this case I obviously have no connection to my mqtt server since it's on another network.).
So it seems to have to do with the router(-settings), though other tasmota devices (a.o. shelly1, 4ch pro, sonoff mini,...) have no problem connecting to the ASUS router at all (though the 4ch pro seems to take quite a long time to connect).

[Phil]

Me i would install a 2ndary AP into the net and use that while the initial conflict between the bridge and asus router sits on the back burner (or someone else solves it),  

perhaps a githib issue could be raised with a detailed log of the wifi handshaking failing  the connection refused message isnt the reason turn up logging to the max and see if any more info is revealed..