Of course they wonât. Money talks. I canât recall ads, Iâll test on another account and see.
I seek to be able to control iHost in the EWeLink app, acknowledging that not every wants full cloud control, this should be an option to aide interoperability and was considered from the outset.
iHost is a local solution so it will never be in ewelink. For control it is CAST.
Thatâs where you are a little misguided - when originally announced, the early releases provided integration with EWeLink app
So Iâm smarter, itâs just questionable why it ended.
I remember this topic coming up in another thread before. The explanation from the official side at the time was that SONOFF iHost initially didnât have its own independent OTA update system, so it had to reuse the eWeLink cloud infrastructure. Thatâs why you had to add it through the eWeLink App.
However, aside from OTA updates, iHost itself doesnât actively connect to the eWeLink cloud. It was originally designed to run as a standalone local system without relying on the cloud.
Thatâs also why there were some odd design choices early on â for example, if you wanted to locally integrate eWeLink Wi-Fi devices, you had to install an additional add-on instead of having that capability built in from the start.
Once iHost later got its own independent OTA system that no longer relies on the eWeLink account/cloud infrastructure, those devices effectively stayed permanently âofflineâ in the eWeLink app.
Hello, I have a problem with connecting to wifi, if I connect with a cable everything is ok, if I create a hotspot on my phone everything is ok, if Iâm at home itâs ok but when Iâm in the office (itâs a private space, not a company office) I canât connect via wifi, I canât find a setting in the router that would limit it, does anyone have any type of what prevents the system from connecting?
CUBE is based on a local software system. If you want to access it remotely, you can enable the remote features here.
I guess I was misunderstood, but if I use the wifi connection in the workshop (office), the cube wonât even start
the virtual machine is not assigned an ip address and cannot start oscube. if I use a cable or another wifi everything is ok and I canât find a problem in the router settings
SkĂșs sa pozrieĆ„ Äi mĂĄm nastavenu sieĆ„ovĂș kartu v reĆŸime most.
I have it, see photo. the problem is only when I connect in the workshop. It works on a hotspot or other wifi, so the problem will be in the router settings
You can try changing the virtual network adapter type to see if that resolves the issue. For example, switch it to Intel PRO/1000 MT Server (82545EM) or Paravirtualized Network (virtio-net). If it still doesnât work, you can also try disabling Promiscuous Mode by setting it to Deny.




