Iāve only had the ihost since January 3rd.
Defective hardware?
Success of the 2.4.2 update not real?
Critical error on the 2.4.2 update?
Technical support responds but delays the return to the after-sales serviceā¦
The ihost crashed by itself!
It would have been better if there was a double bios, like on professional devices.
Iām tiredā¦ Iāll migrate to Home Assistant
Sorry to see you go. Weāre looking forward to your return when CUBE meets your needs.
I managed to add *.coolkit.cc and *.coolkit.cn to bypass the VPN.
Google is not by-passing the VPN, as expected:
coolkit.cc is by-passed, as expected:
The wildcard is working, because also eu-apia.coolkit.cc is by-passed, but after certain hops, itās resulting in Time Out (even without the VPN). I tried also 50 hops, with no success.
But I still have the same problemā¦ All smart light switches Sonoff TX Series keep changing the status between online and offline, every 30 seconds.
Their wifi LED starts flashing (2 quick flashes - indicating it lost server connection) every 30 seconds, changing the status between online/offline on eWelink app.
Is there any other domain that I need to by-pass?
Hello ociepa.ekotox,
Curiously, the Amazon France stock of ihost 4GB sold by Sonoff passed into the hands of amazon warahouse at the beginning of last week. Sold off ālike newā.
So I decided to order one, while the return procedure (legal warranty) or the refund was done.
And if this stock is a defective series, I would have returned it within 30 days. there were 4 left.
The order was cancelled by amazon in less than 18 hours. There are no more items available
Exchanges on the open ticket are very slow and tedious.
This policy is beginning to raise serious questions. Amazon Prime does not provide any after-sales service. Unable to contact sonoff via Amazon. I have never encountered such opacity!
The ihost had to replace an Enky box to fully manage my devices on an http accessible platform. If I donāt get any support. I would have been better off betting on a jedoom box
If these domain bypass is not working for you, might be something else causing the problem.
Can you confirm when the device starts acting weird? Is it after you upgrade the firmware of your Sonoff TX Smart Light Switch?
Furthermore, can you try open a hotspot with your phone and re-pair your device with the hotspot.
If the problem persist, then is the device itself has some problem, and if everything works fine, then it might be the problem of your network setting.
As soon as the VPN is enabled, they started acting weird.
By-passing *.coolkit.cc and *.coolkit.cn doesnāt help
Disabling the VPN fix the issue.
It seems there is another domain missing.
Iāll throw them away and replace them by ZigBee Smart Switches to have a better control about what they are doing.
Maybe there is a solution by setting up a virtual network or another network/subnet reserved only for IoT and internet access without VPN?
In addition, it would avoid barriers on device updates
They are in a subnet only for IoT
I updated all firmwares some days ago, from 3.7.6 to version 3.8.0 with no problem.
The summary is:
Bypassing the VPN based on domains: they keep losing connection to eWelink servers every 30 seconds.
Bypassing the VPN based on devices: they work perfectly.
Disabling the VPN: they work perfectly.
There is no problem on others IoT devices, like Ring Intercoms, Google Nest Thermostats, dishwasher.
My Sonoff mainly uses subdomains in coolkit.cc, at least recently from what I see in the DNS server logs.
In practice, all servers of the entire eWeLink infrastructure are on AWS, which means that in practice they connect to *.compute.amazonaws.com, but if you run the entire AWS via VPN, there will also be a lot of other traffic going there, not just eWeLink.
If you have the technical possibility on the router side, observe whether Sonoff maintains a TCP 443 connection to *.compute.amazonaws.com, if the session is broken, this may be the reason for the offline/online you are observing.
Also consider where devices receive responses from DNS. Because theoretically desynchronization can occur for the AWS geo cloud at different exits if the VPN is terminated somewhere extremely different than your ISP.
To be sure, make sure that Sonoff receives domain name resolutions from DNS for the VPN end location.
It shouldnāt matter, but if your Sonoff connects somewhere far away to another part of the cloud and the DNS resolutions point to a different zone, then maybe some strange phenomenon is happening. Because some clouds position traffic based on DNS to their closest CDN.
If you have a separate DHCP for these IOTs, advertise the specific DNS that is used in VPN traffic and also push this traffic through the tunnel.
I am not an expert.
But according to your details, the problem seems to come from the incoming traffic and not from the outgoing traffic.
Exactly, but according to the support, when the LED flashes twice, itās because it lost connection with the server.
And the smart light switch should be a client, not a server, so I canāt imagine why it shouldāve an incoming connection.
In order to receive incoming traffic, an outgoing connection must first be established, otherwise incoming traffic will not be able to pass through.
A TCP connection must be established and this session must be open all the time, otherwise the two-way connection will be broken.
Perhaps the router or VPN provider closes inactive connections after 30 seconds. In this case, the sensor reconnects after losing the link to the server.
NAT/Firewall/VPNā¦ it is possible that it closes the session that does not generate traffic, because there are usually no large transmissions there.
Are you sure you are not losing wifi connection between the router and the sensors?
100% sure they are connected to the router all the time.
The domains *.coolkit.cc and *.coolkit.cn are bypassed. They are not going through the VPN as you can see here
new problem
The hosts are getting worse every time.. now alas they are just problems.
now even the cast section doesnāt work anymore, guys we are not really, Iām losing hope.
I checked on my ihost. It works fine. When I press save, the console window closes automatically and the changes are saved.
Update your IHost. You have a red dot on settings button
