šŸ‘Øā€šŸ’»ā€ć€Release Note怑eWeLink CUBE on iHost Version History

Screen recording link.
On the desktop, graphs are also drawn slowly.

Every graph we have drawn are with full data to avoid lag in switching month/day.
So the data retrieval will cause some time.

Hi SuiKa,

I’m trying to bypass the VPN, as the software team cannot solve this by themselves.

To do that, I need to know the domain (or IP) that eWelink app is connected. Your software team said they also don’t know, which is weird.

Could you please confirm with them? I guess they are not understanding what is happening.

Thanks!

Try this:

  1. Load the daily data;
  2. Draw the graph;
  3. Load the Week/Month/Year data in the background

The IP of your device in you LAN is determined by your router.
Try use some mdns app, like Mdns(android) or Discovery(ios).
And use ewelink as filter, you will see every sonoff devices in your LAN.
The result contains the data you need, like device id or LAN IP.

Thanks for the advice.
We’ll see if we can optimize it.

No, I mean the IP (or domain) of your eWelink servers.
My idea is to bypass the VPN only when the destination is your server. Everything else will be under the VPN or dropped.

For example:
If my device try to connect to your eWelink server: then the VPN will be bypassed.
If the device try to connect at any other destination: then the connection will be over the VPN or will be dropped.

Then server domain should do the job, right?

Yes, the server domain will do the job :+1:
I can set the router to bypass the VPN based on domain, but I don’t know the domain used by eWelink :blush:

There are too many domain. Can your VPN config domain with wildcard characters?
Just bypass every domain that ends with the following second-level domain:

  • .coolkit.cc
  • .coolkit.cn

Here are some full domain example for you:

After power outage and then power resumption add-on eWeLink Smart Home does not work, as the system requires to re-enter login and passwords and select country. This did not happen before. I noticed that it started with firmware 2.4.0 and continues on firmware 2.4.3. Is there any way to fix this?

I can’t, but I’ll raise a request feature for the company that makes the router.

Can you provide any more instructions on this please?

I already use Node Red to control my iHost devices but I’m out of my depth on this one.

I’ve part configured the http request node but I need more details instructions.

Otherwise can you help @massimo.berni or @ociepa.ekotox

I want to trigger a reboot of the iHost, via a button press or virtual switch.

It’s stated in the API doc

a. Restart Gateway

Allow authorized user to restart the gateway through this interface

  • URL:/open-api/v2/rest/hardware/reboot

  • Method:POST

  • Header:

    • Content-Type: application/json
    • Autorization: Bearer

Request Parameters: none
Successful data response: empty Object {}

Conditions : The request parameters are legal, and the user identity verification is passed.

Status Code: 200 OK

{
    "error": 0,
    "data": {},
    "message": "success"
  }

Domain of eWeLink are over hundreds.
But they all ends with two second-level domain I mentioned before.
So wildcard characters are the best option for you.

Can you provide the smart-home add-on log?
And the time of your power outage, as accurate as possible.

Please see DM

Hello Suika,
The web interface is no longer accessible.
The Ethernet layer works (DHCP assigns it an IP) but the OS no longer starts.
The address responds to ping…
The factory reset has no effect: nothing happens after 10s of pressing.
The ihost is dead, except to reprogram the ROM
Is this possible via a USB connection or flashing sdcard ?

Another IHOST that crashed. Is this a coincidence? :thinking: