I have an iHost RV1126 - 4G RAM that I only use at night.
In the morning the iHost is automatically turned off (the power is turned off) and at night it is turned on.
Randomly, after a day or 1 week the iHost requires login to the eWelink account.
Until I log in, the sonof devices added to the CUBE do not accept any commands or scenes.
iHost is not connected to the internet.
What is the reason why it logs out?
What is the reason why it does not work until I log in, given that normally you only need to access the eWeLink account to import devices from the account?
How can I fix this problem?
I’d say that’s standard practice for security reasons—like preventing unauthorized access—since you’re shutting down the iHost every day and turning it back on much later; I imagine you’re doing this using a smart plug!
I still don’t quite get the reason for turning the iHost off and on, though, given that the power consumption is minimal!
I’d also say that isn’t exactly healthy for the device itself!
If you just want to run it to pick up Wi-Fi devices and export them over the network, you’re better off using a Raspberry Pi with the container and the eWeLink plugin!
Thanks for the answer!
Unfortunately, what you say about security doesn’t really make sense because if it were an intentional preventive measure, then the logout phenomenon would happen daily and not just from time to time.
Mine logs out if it stays turned off for a long time and is then turned back on! I’m not exactly sure what causes it! However, I never really notice it because I don’t use any Wi-Fi features, and the automations and Zigbee devices keep working correctly! I really couldn’t say for sure!
Someone mentioned it might be a security feature, but I honestly don’t know! Sometimes it could be related to the active session window saved in the browser cookie or something like that!
But just out of curiosity, why do you turn off your iHost?
As I said before, iHost is only used at night.
During the day, it is turned off due to the fact that the scenes saved on iHost conflict with those in the cloud (eWeLink).
Your next question is probably why I don’t set the scenes to be executable only while iHost is running.
The answer is simple, because this way I have a plan B for situations where problems arise with the cloud or the internet connection.
Unfortunately for me, iHost is not a reliable device in terms of operation because there have been several cases in which due to a failed update or simply due to the wrong update designed by the developer, I had to reset the device to factory settings and I had to recreate the numerous scenes I had.
Another important reason why iHost is not a reliable device for me is related to the fact that all devices that are recently launched have been incompatible with iHost for far too long, which is why they simply could not be used.
Honestly, I’m extremely curious about why it disconnects from the eWeLink account and nothing works until I log in again.
Be careful, we’re talking about a device designed for offline stand-alone operation.
Why do you turn the iHost off every morning and power it on again every evening? Is it a normal shutdown, or is the power simply cut off? I got lost in your explanations.
It’s funny, but for me, it’s the opposite: all the released devices work well, and I’ve never had issues with updates. I have at least ten iHosts running in various locations, and they are all rock-solid and working correctly. However, as I mentioned, I don’t use Wi-Fi for anything—only Zigbee and some Matter devices.
However, the iHost doesn’t require an eWeLink account unless you’re using Wi-Fi Sonoff devices—like the Sonoff POW R3, etc.—that rely entirely on the cloud for login validation. Sometimes, logging in on multiple different devices can cause the session on the iHost to drop, which is needed to synchronize cloud- and Wi-Fi-based eWeLink devices.
You say that iHost does not require an eWeLink account only if you also use wifi devices.
Perfectly correct but I can’t really imagine a reason why I should use anything other than a banal ZBBridge Pro, Ultra hub or at most an NS Panel PRO for zigbee devices, and if you have an iHost I think it is absolutely normal to also have wifi devices.
This is not even the problem.
The problem is that iHost is unstable and you can’t rely on it and you have to wait months until it becomes compatible with new devices, because in fact it is not new devices that are not compatible with iHost but iHost is not compatible with new video devices.