iHost eWeLink Cube ver 2.5.2
eWeLink Smart Home Add On
Add-on ID: cb63d895fcdb96e8096f2daa24db775adea3fef0cdd5a88a3aca7d5c0b7aa58a
Created: 2025-06-18 16:29:46
There seems to be what we consider to be a serious flaw/bug regarding the ON/OFF iHost displayed condition of Wi-Fi devices when they are toggled by the hardware switch on the device or from the eWeLink app.
Wi-Fi devices toggled from their iHost pane will show the changed status as will the eWeLink App. However if the device is toggled from the eWeLink App the device will physically change state OFF>ON or ON>OFF but the new state will not be displayed in iHost, furthermore any iHost scenes that rely on a Wi-Fi device change of condition to trigger- will not run. This flaw/bug also applies to the mechanical switch on the Wi-Fi device- press to toggle it and the eWeLink App will show the new ON/OFF state, but iHost won’t.
Further tests have revealed that say a Sonoff Basic Wi-Fi Switch is configured to be ‘ON’ when powered up: If the iHost Home Screen pane for the device is showing as ‘OFF’ then after the Wi-Fi device has powered up and the relay is ON the iHost Pane does not change from OFF to ON.
In summary it would appear that the only time the iHost pane for the Wi-Fi device shows its correct ON or OFF condition is when it is switched by iHost.
This Flaw/ Bug seems to have manifested itself since the latest version of eWeLink Smart Home. We have reported the issue to Sonoff via iHost Feedback under ticket 246179.
1 Like
I had a similar situation and the issue was that after each update you need to login again into the sonoff addon.
Or logoff and login again.
Maybe you have a similar issue 
Thanks- I did try logging out and logging back in but it did not resolve the issue. As I have scenes that rely on being triggered by the Power Up status of certain Wi-Fi switches I will replace them with the ZB Mini R2.
Sorry it didn’t work 
Just to be sure, when you mention logging in/out are you referring to the ewelink smart home addon in docker right?
Yes that’s correct the iHost Docker eWeLink Smart Home application and also at the routers I’ve forwarded port 8321 directly to the iHost IP address. Re-Boot of iHost doesn’t resolve the issue. I’m convinced that there is a bug in the latest version of the eWeLink Smart Home.
I can’t believe this- as I was writing my reply to your message I tried yet another iHost re-boot and now the issue has resolved itself. I will closely monitor the situation to see how reliable it is. Maybe Sonoff should consider including a re-boot schedule in iHost. Thanks for your assistance with this issue.
glad that in some obsure way it worked 
So just to update for this particular problem: the iHost re-boot only resolved the issue for a very short time. So factory reset the iHost. replaced the TF memory card and restored the system from a back-up which seems to have solved the problem. I’ve not been able to format the TF memory card that came out and in another iHost is shows as ‘no tf card’ so looks like it was actually a hardware fault rather than a bug. This sort of thing shows the importance of regularly backing up your iHost.