I am using eWelink with about 36 compatible devices. Most of them are WIFI, some of them are zigbee. So I got the Sonoff zigbee bridge pro. A lot of my devices can work in LAN mode but not all. I got advice from eWelink help that if I want all devices to work only in LAN, that I should look for iHost.
Since I intend to buy iHost, I would like to know if I will have to reconnect all the devices to iHost one by one, or if there is some other procedure for the devices to be connected to iHost. The iHost user manual only describe how to add new devices, not how to connect to devices already on the LAN.
Maybe someone will think the question is silly, but before I buy, I’m interested in how much work I have to do, especially since there are a couple of devices that are in a hard-to-reach place. Thank you very much for the answers.
Setting up this system can be quite involved, so it’s important to plan accordingly.
Please note that only WiFi devices operate in Local Area Network (LAN) mode. Zigbee devices, by design, operate locally and do not require cloud connectivity. However, they do need a coordinator, such as an iHost, to function properly. All devices, both WiFi and Zigbee, must be connected to the iHost if you want local control.
When setting this up, keep in mind that WiFi devices will not be visible in the eWeLink cloud because the iHost acts as the local server. To manage these devices through your App, you will need to use a dedicated add-on.
Of course you meant zigbee devices.
Zigbee devices added to ihost will not be visible in ewelink cloud.
WiFi devices must first be added to the eWeLink app (cloud) and then used for the eWelink smart home add-on in ihost.
Now I am a little confused. If I must add devices to eWelink app (this I have now) than why iHost? Can you explain it to me in common sense? I don’t want to be dependent from cloud but still I want to have control (overwiev) from anywhere
It’s because iHosts are local servers and are not capable of controlling WiFi devices. At least for the time being. So if you’re satisfied with your current configuration and know nothing about the perks of going local, it seems like you feel using an iHost is as useful as a hare with a wristwatch!
it’s a bit complicated. hard to say what will be best for you. if you only want to use ewelink and ihost app then you can’t do that.
if you want your scenes to be executed locally then ihost can do it. not everything can be set directly in ihost but you can use node-red plugin. but you have to remove all automations from ewelink cloud.
but not all wifi devices work in LAN mode and will be visible in ihost in the ewelink smart home add-on.
to have full local control you need zigbee devices added to ihost. but here comes the problem. zigbee devices will not be visible in ewelink app.
you can get around this problem, but you have to give up the ewelink app and switch to the smartthings app and invest in additional devices. Matter hub smartthings station.
ihost as matter Bridge will transfer zigbee and wifi devices to the matter smartthings station hub. but not all devices are supported by matter yet (e.g. leak sensor SNZB-05P does not work).
so here you have to consider whether you need it now and want to invest in new devices
maybe in 12 or 24 months it will become easy once matter 1.4 or newer is implemented.
Maybe someday nspanel pro will work stably as matter Hub. You will be able to return to the ewelink application then. But it won’t be soon.
