Uninstall ewelink app and reinstall the latest version from the official source.
Before you start pairing, make sure your phone is connected to 2.4Ghz WiFi!
Reboot your device and follow the steps below…
I asked the OP about this earlier and he seems to be convinced that nothing like this is happening.
Sonoff devices usually need output via TCP 443, 80, 8080, UDP 53.
He has already done it several times according to his words.
Yes, but there is no access to the main router as far as I understand!
Strange mess… 
1 Like
Now that I think about it, I had seen a similar question somewhere, and at the end the person realized that he had confused one account with another.
1 Like
And the ISP may block the ewelink servers for some security reason. I had such a problem only with a website. They only blocked it from the mobile internet network of one of the providers. For a second I could see it and it said provider protection. I talked to them, they referred me to the hosting service, the hosting referred me to the internet provider and so on a circle… In the end it turned out that the internet provider was blocking it 
No wonder it’s the same here, only that he doesn’t see what happens after connecting.
The OP said something about several different ISPs he tested on, so…
Device shows up in router ARP table so it has a IP and has access to my network … it’s just connecting via a Access point
I understood that there are 4 networks, that is, 4 routers and one main router, and which of them does not have wireless internet and does not have access to it to see what is happening there. Or to be more precise, one router lets the internet to the other 4 routers. It has tested on an internal network not on different providers. That’s why I told him to go to the neighbor where there will already be a different ISP. He goes into some of these local routers and sees that the bridge is connected. But it could just be a mess! It would be clearer if there was a device to connect it without a bridge.
Might be good to find out what ewelink’s IP is and run a test. If the person is an administrator, he should handle the task of tracking Ewelink’s IP, but I don’t know what it is.
eWeLink uses the Amazon cloud, and which IP depend on the geo-location.
One of the many cdn…
*.compute.amazonaws.com *.elb.amazonaws.com *-dispd.coolkit.cc *-api.coolkit.cc *-disp.coolkit.cc
What IP will be returned by DNS is a matter of geolocation and the nearest node.
Does the bridge respond to ping?
yes, that’s what a person should understand.
But Morgan, I’m just thinking because there’s not much logic in what I’ve written. In the sense that once it has connected, the device should appear in the location and if there is no connection with the server, it should just be offline and not hidden.
I’m beginning to doubt that the person sees something else in the router.
You know… it’s hard for us to speculate what the OP’s situation is.
The first is a strange fixation on ARP. Yes, if the device appears at least once, a record will appear in the ARP table, but it does not mean that the device is still connected and the arp has a 4-hour time out.
Whether the device is actually still connected is checked on the access point itself. The fact that the device has successfully established a connection with the AP does not necessarily mean that it has correctly set network addresses.
Most sonoff devices need dhcp and if they don’t get the network settings they won’t be able to do anything but they can still show up as connected to wifi.
Many Sonoff devices can be pinged and respond to ICMP.
If the device has established and maintains a Wi-Fi connection to the AP and received data from DHCP, it should in many cases be able to respond to a ping. This can be done from this specific AP or from another machine that is in the same subnet.
It is also good to monitor the traffic going out to the Internet on the WAN port and see if the device is actually trying to establish communication, similarly to DNS queries.
I don’t know what the OP’s problem is. Potential causes need to be excluded individually.
Using typical ewelink logic and adding devices…
In the ewelink app you need to choose the adding method and it is best to already have 2.4Ghz WiFi connected on your phone.
The app should start searching for the device, if it detects it locally via Bluetooth, the app should recognize the device type, connect to it and configure it.
After a successful adding process, the device should connect to Wi-Fi and communicate with the cloud.
Then, a refreshed tab with devices and the new device usually appears in the app. But this information already comes from the cloud.
The OP suggested that the app does not detect the device for configuration at all. But this can’t be true, otherwise if it didn’t happen, the device wouldn’t have information about Wi-Fi and wouldn’t connect anywhere.
So if the adding/configuring process actually took place, now you need to determine whether the device cannot connect to the Internet and access the cloud or whether the phone with the app has any problem communicating with the cloud in order to receive updates.
In the case of the app, I have already suggested reinstalling the latest version, possibly clearing the data or removing permissions and logging out of the account. A pure app without information about devices will download them from the cloud.
So the OP needs to determine whether the Sonoff device is unable to connect to the cloud or whether his phone with the ewelink app has a problem.
If he has web ewelink, he should see the device there if it has actually connected to the cloud. In this case, it is a problem on the side of his phone with the app. If you don’t see the device, there is a problem with the sonoff device.
And you need to determine why the device does not have Internet connectivity. Repeating the mantra ARP, arp, arp… doesn’t change anything.
What IP address does the device get from the DHCP server?
Does the device respond to ping?
Does the device generate a connection on the WAN port?
Does the device have DNS configured correctly?
1 Like
Seems like you either have very little knowledge of networking or misunderstood what i said…I said I have a enterprise grade router that dosent offer wifi just LAN network and you need accesspoints to make the wifi network… I never said i dont have access to it. and I DID SAY many times now i’ve tried on 4 different networks … 4 accesspoints are not 4 routers … I can see my device on the accesspoints ARP table same as the router ARP table i just cannot connect directly to main router since NO enterprise router offers wifi because they dont have wifi antennas thats why we have wifi AP’s … this is no mess this is how every enterprise solution network is done …
Also i’ve got the HUB working by buying a 15€ router, setting it to same SSID and PW as the network where it would be, disabling all accesspoints, and connected to the 15€ router without a sweat, than turned off the bridge than threw away the 15€ router and powered on AP’s and because it’s same SSID and PW it all just works no … so i guess AP CLUSTER was probably fucking around with it or the 15€ modem has some old enought standard for the bridge to connect!
So anyways thank you all for the help, I’ve got it working now tih 15 devices 0 issues!
Also sorry for all the sudden long replies I’d suddenly take, it’s this forums new user limits…
I obviously didn’t understand you. Because I asked several times if you have any protection in the main router that does not have wireless internet. You didn’t answer this question anywhere and from there I thought you didn’t have access to the main router. Your case is very strange and that’s why I wanted to find out everything I could. Nowhere are you answering questions that can be seen very easily with a simple ping and route check on the device. In the end, I was convinced that the problem was with you and not with the bridge.
1 Like
This is why we should not believe what people write. He generally did not answer technical questions. A says that he is an administrator. He replied that he sees that the bridge is connected and that’s it. And here we started to guess.
1 Like