06-08-2024 07:08 PM
I was able to connect to the 2.5 channel a month ago on the same phone but now I am not.
I have tried a Samsung Fold and 3 different versions of Iphones and an Ipad
(I need to setup smart light bulbs which require a 2.5mhz channel)
Why I know it's working and the password is correct -
I was able to connect my garage door opener that I setup a month ago using the Samsung phone, which did connect to the 2.5 channel just fine then...
I just connected a Nintendo 3ds today.
I still have multiple devices connected to the 2.5 Channel
I've restarted phones and router... updated the router (router is not set to auto update so should still have been working as it did previously)
dissabled mac address filtering
turned on and off - Traffic Analyzer and Smart Connect (Smart Connect is currently off as well as IPv6)
This is the error in my router system log (note - error does not show up when traffic analyzer is enabled)
Jun 8 16:25:58 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind (*MAC Address*), status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jun 8 16:25:58 wlceventd: wlceventd_proc_event(508): eth7: Disassoc (*MAC Address*), status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 8 16:26:06 wlceventd: wlceventd_proc_event(527): eth7: Auth (*MAC Address*), status: Successful (0), rssi:0
Jun 8 16:26:06 wlceventd: wlceventd_proc_event(556): eth7: Assoc (*MAC Address*), status: Successful (0), rssi:0
Jun 8 16:26:07 kernel: (*MAC Address*) not mesh client, can't update it's ip
At this point I've exhausted various searches and settings and nearing a factory reset.
Please tell me there is something else I can do.
Solved! Go to Solution.
06-08-2024 09:07 PM
Yes ... I know it's 2.4 😖
I ... worked around my issue by renaming the 2.4 channel. Going off of the wireless diagnostics in the router, I seen that 1 of my 5ghz channels was using the same name as the 2.4 even though I was connecting to it under the name it was configured for. (Still not sure what is going on with that)
06-08-2024 09:07 PM
Yes ... I know it's 2.4 😖
I ... worked around my issue by renaming the 2.4 channel. Going off of the wireless diagnostics in the router, I seen that 1 of my 5ghz channels was using the same name as the 2.4 even though I was connecting to it under the name it was configured for. (Still not sure what is going on with that)
06-08-2024 11:20 PM
A lot of IoTs advise to have the set up phone on the same SSID/channel. For someone like me who SmartConnects them it means turning off 5 GHz (and 6 GHz) radio(s) on the router, then trying to set up the IoT while the (Samsung) phone (in your case) is connected to the same 2.4 GHz.
06-09-2024 09:11 AM
I didn't try turning off the 5ghz... but I did forget them so my phone only had the 2.4 option for auto connect. Same result I'm sure in the end, I am fairly certain my router was somehow confusing the 1st 5ghz with the 2.4.
The 2.4 was named Netgear, the 5Ghz ... maybe 5 years ago was or was not. Either way it has been named something else for quite some time. I've since renamed the 2.4 which resolved the issues, but both the 2.4 and 5 still show as Netgear in the site survey even though nothing is currently named that way. For the moment evey thing shows the correct name and the clients on the correct list ect, even when connecting via AIMesh node, in all the other tools within the router. So... something is definitely messed up in the router, maybe something in one of the two AIMesh nodes I have setup, I'll have to dig into that when I have more time.