I have a dozen sonoffs (basic, dual, 4ch, pow, bridge) and all of them working with my unifi APs (1 AC-Pro and 1 AC-lite). Wifi is set to use WPA2 only (personal) and encryption “auto”. Hope it helps…
That’s hopeful.
Could you check the hw version of the basics?
Are they r1 or r2?
Hi,
The sonoff basics are all the R1 type. Most of then using tasmota 5.14.
Any basic R1 on default ewelink fw?
nope. All tasmotas… They usually go out of the box directly to the FTDI programmer.
What was the solution? the problem was the ewelink fw?
My r1 tasmotas work aswell.
I don’t have a solution yet, still looking.
4 basics R1 irregardless of fw and one B1 r2 on latest firmware, refuse to connect.
I need to have my old router on too
And yes, i could ftlash tasmota, i could flash ESPhome but i really want to get to the bottom of this
Any Sonoff forums with ideas?
Sonoff forums are kind of a clusterfuck, unfortunately. They do have similar issues but didnt find nothing useful.
Unifi forums are more civilized but no luck there either unfortunately.
try tasmota foruns :-).
Could try, but i dont think they will bother as it’s clearly an eWeLink issue (or a ubiquiti issue)
hm… I think I got it wrong. You said R1 with tasmota works or not? Or there are some that work and some that not?
Yeah, just noticed i accidentally makred it as solved, scratch that
So, i rewrote my 1st post to be more clear like this:
- Sonoff Basic R1 (Any eWeLink sw version) do not connect to any Unifi AP
- Sonoff B1 lamp on latest FW, does not connect to Unify
- Sonoff Basic R1 flashed with tasmota connects OK with no issues
- Sonoff Basic R2 connects OK on any eWeLink sw version
- Sonoff 4ch Pro R2 connects OK with no problem.
To be honest, on #3, there are some issues in the sense that when i have both AP’s up (my unifi and my tp-link), they will only see and connect on the tp-link. But that’s another issue
Are the basic, broadcast(transmitted) & beacon rates for 2.4 the sane on both type of APs?
Some Wi-Fi devices will not connect unless the lower rates are offered in basic and/or beacon…
I work with an enterprise system so am not as familiar with the home systems.
On the other hand, i have no idea how to check what you just said
Are you referring to this:
Just found it here, will try it out.
Dammit, got so excited, unfortunately no luck
After so much trouble i have found the solution. Turns out it was entirely a sonoff issue.
- Remove sonoffs R1 from eWelink app
- Make a new SSID on a working AP (the tp-link in my case), new SSID name.
- Push the button to pair them with the new SSID (AP compatibility mode might be necessary)
- After the pairing is done, update to lastest sonoff FW if available.
- Remove from eWelink app again
- And re-pair with the original SSID on the unifi AP i wanted to use.
- i want to say proffit… but i already lost a week trying to troubleshoot this
I only know one person irl who works with home automation and he happened to have the solution…
God bless him
Did the trick for me to.
I had an 10 year old ZyXel WiFi router lying around. I turned off the Unifi (walked out of range) and gave the ZyXel the UniFi SSID, The Sonoff then connected properly. I also upgraded.
Then connection to Unifi was easy as the SSID was still OK. So I turned off the ZyXel and turned on Unify again.
I’m Still having one (of three) RF Bridge 433 not connecting, But I need only 2, so that’s something for later. Now it’s time to upgrade to HA over the air (https://www.youtube.com/results?search_query=sonoff+ota+tasmota)
That was not exactly my case.
What essentially fixed them for me was to connect them to an entirely different SSID and then revert them back to the one I use.
Try it with your bridge. Either change the unifi ssid or assign a new one to the zyxel, pair the bridge and then delete it and go re-pair with the unifi.
Just for the proof of concept
Having the SSID name differently avoids all your devices trying to connect to that old router, so YES it’s better to have a different SSID.
For those without such an old wifi:
I remember also removing the SSID from my phone, my son created a personal hotspot on his phone with the normal SSID name and we kept that phone right next to the sonoff. That stopped the sonoff blinking and it connected to the hotspot.
I used wifiman to check for the wifi channels (this unifi app is available for iPhone and Android phones).
Be aware: your hotspot can only handle a couple of connected devices, so having the hotspot named differently will avoid your whole house trying to connect to the hotspot and occupying all allowed connections. You can see the number of connections to the hotspot.
After much trial and error, this is what worked for me to connect to the unifi Access Points:
I created 2 additional wifi SSIDs, named STA_SSID1 and STA_SSID2
One is the IoT network, with its own VLAN (30) and the other is for NoT devices on another VLAN.
Then I programmed/flashed the Sonoffs via serial with Tasmota.
Immediately after finishing the flashing, I quit the programming tool and used Termite (the serial connection) for communication with the terminal. Baudrate 115200 and one enter shows some information.
I defined the SSIDs Using the backlog command:
Backlog ssid2 STA_SSID2 password2 STA_PASS2; ssid1 STA_SSID1; password1 STA_PASS1; hostname sonoffPOW166
backlog IpAddress1 0.0.0.0; IPAddress2 0.0.0.0; IPAddress3 0.0.0.0; ipaddress4 0.0.0.0
Then I observed the Sonoff connecting and what IP address it gets.
Via the web interface I programmed other specifics:
using Google Chrome I typed in the web address
In the unify controller I fixed the IP address to the one it received (or the one I wanted) and forced a reconnect to get this done (sometimes you need to do this multiple times)
Furthermore I configured the VLANs as explained very nicely in a youtube video (forgot to record the link)
I configured other tasmota details with (see tasmota wiki -https://github.com/hassio-addons/addon-tasmoadmin/blob/1f428c3d24296390b8d2c2f57fec2d2d72f372aa/README.md)
e.g.:
backlog IpAddress1 0.0.0.0; IPAddress2 0.0.0.0; IPAddress3 0.0.0.0; ipaddress4 0.0.0.0
backlog mqtthost hassio; mqttuser <deleted>; mqttpassword <deleted>
Backlog topic sonoffPOW166; setoption53 1; setoption19 1; SensorRetain on; PowerRetain on; SwitchRetain on
Backlog Timezone 99; TIMEDST 0,0,3,1,2,+120; TIMESTD 0,0,10,1,3,+120;ntpserver1 nl.pool.ntp.org
This works for me, but I am still having issues connecting to the mqtt broker because of the VLANs