I don't know If this will help you at all, but you can try give to the devices you require to connect to the router a static dhcp lease.
Yea, it really is weird. The devices are only 4 meters away from the router!
My config now stands at:
config wifi-iface option device 'radio1' option mode 'ap' option ssid 'The Internet Devices' option network 'lan' option encryption 'psk2+ccmp' option key 'xxxxxxxxxxxxxxxxxxxx' option dissasoc_low_ack '0' option distance '10'
But the problem persists!
Ahhhh haaaaa! Good idea!
However, I've done that and the problem is still there.
The devices themselves have a flash LED which means they are not connected to a network.
Are they still being disassociated every couple of minutes still in the System Log?
Unfortunately yes. Still the same.
You never answered my question. Both SSIDs I inquired about are on radio1.
I would try 20 MHz mode, especially if you keep legacy rates enabled.
Change to 100, ten is way too short; and has always failed in my testing.
Try adding this to the failing SSIDs:
# Will change multicast group rekey to 24 hours option wpa_group_rekey '86400'
Try disabling the other wifi interfaces for now just to test.
I tried to answer it, but perhaps I wasn't clear.
Originally I used one SSID ("The Internet") on both radio0 (5 GHz) and radio1 (2.4GHz).
My phone always connects to the 5 GHz interface.
The app for these smart devices requires that the phone be on 2.4 GHz wifi (which the smart devices require).
So I ended up adding an extra SSID ("The Internet Devices") on the 2.4 GHz radio1 just so I could connect my phone to it and therfore add the devices to it.
All other wifi interfaces have now been disabled.
I've made the suggested changes (many thanks!):
config wifi-iface option device 'radio1' option mode 'ap' option ssid 'The Internet Devices' option network 'lan' option encryption 'psk2+ccmp' option key 'xxxxxxxxxxxxxxxxxxxx' option dissasoc_low_ack '0' option distance '100' option wpa_group_rekey '86400'
But I'm still seeing the disassociated messages in the System Log, the device is still flashing to say it's not connected, and it's still missing the signal and other information in the tx/rx rate.
Just drop the distance setting alltogether, you're just shooting yourself into the foot by micro-managing this (changing the distance setting is only need for long range links, way above 100m).
How exactly do you input to these devices to connect to your WiFi initially (i.e. the SSID to connect to and the key)? I know you say there's an app that controls them, but how do you get them to initially connect, so they can use the app? Maybe go through that process again, clearing any old settings.
Also, the spaces in the SSID could be causing issues. Older devices that run older software/firmware do not seem to like SSID's with special characters in them.
option distance 'xx'
Should be under the "config wifi-device 'radio1'" section as well, not "config wifi-iface" in your /etc/config/wireless.
The mobile app is used to configure the networking on the device, so it can connect to the WiFi. The mobile app sends a UDP broadcast packet or a multicast packet containing the WiFi SSID, username and password. The device can receive the UDP packet, as long as the UDP organization form is known (not sure what that means!). After that the device (should) connect to the SSID.
Like I said the device works with the stock firmware (which is also OpenWrt). So there's some difference in the stock firmware.
I used the same SSID, username and password on both stock and my install of OpenWrt. I even tried an SSID with no spaces just to make sure.
If I configure the device in the stock firmware, then switch over to my install of OpenWrt (which has the same SSID, username and password), the device is listed under the associated stations, but missing the IP, signal, and rx/tx rate information (as shown in the screenshot above) and has frequent disassociated messages in the System Log.
- Is this the default Android/Apple WiFi manager?
- If not, can you uninstall the add-on app and use the default network manager?
I just have no clue how that works. It seems to me a little bit like the chicken and egg scenario. The mobile app needs to use the WLAN to send the connection info to these devices so they can connect. But how can it send it to them if they are not already connected to the WLAN? Are you sure there's not some step missing about connecting the phone or tablet with the app via USB or Bluetooth to these devices? Are they actively snooping the 2.4ghz band before receiving this information and the app sends some unencrypted packet out and they detect it? I'm kind of stumped on how this occurs.
My best advice at this point would be to generate a backup of your configuration for this build. Revert back to stock firmware (since it is OpenWRT) and get it working. Generate a backup of that when it's working. Extract the '/etc/config' folder from each of your backup tarballs. Go over specifically the 'wireless', 'dhcp', and 'network' files and compare each section, looking for significant changes between the working and non working backups.
No, it's the Smart Life app from Tuya: https://play.google.com/store/apps/details?id=com.tuya.smartlife&hl=en_GB
Some other links...
What is the difference between EZ distribution mode and AP distribution mode?
How to set the device to config mode ?
How to add device in App for Internet connection？(WiFi)
What is specification for the Wi-Fi name and password of the device connection?
I have no idea either!
There is definitely no missing steps. With the stock firmware it really is as simple as putting the device in config mode, running the mobile app, clicking the + button to add a new device, and then it finds it, and the device connects to the WiFi with the credentials given.
You know what... I think that's a great idea!
The WRT32X has dual partitions, so I can easily swap between the two with a simple reboot.
I'm not worried about the app, I'm saying its your issue!!! DELETE IT and use stock Android with stock OpenWrt!
I've fixed the problem by disabling WMM using
option wmm '0' - I don't know why this fixes the problem.
If anyone else stumbles upon this thread because they are having the same problem, the following configuration in /etc/config/wireless works for me:
config wifi-iface option device 'radio1' option mode 'ap' option network 'lan' option disassoc_low_ack '0' option ssid 'My SSID Name' option encryption 'psk2+ccmp' option key 'xxxxxxxxxxxxxxxx' option wpa_disable_eapol_key_retries '1' option wmm '0'
Interesting (your app may not properly negotiate things like power and QoS)...just recall that WMM must be enabled for 801.11n.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.