I have a question regarding the iHost. After some time, the device control stops working. This means that devices can no longer be switched on or off, and routines are no longer executed. However, it is still possible to log in to the iHost and perform a reboot.
This issue occurs sometimes after just 2 days, sometimes only after 4 days.
I have already checked several possible causes. At first, I thought it might be related to the Docker installation of Node-Red, so I uninstalled Node-Red – but the problem persisted.
Currently, I am only running two Docker containers: ewelink-smart and Node-Red for a few virtual devices. Additionally, I am using Alexa via Matter.
My questions are:
Are there any other users experiencing the same issue?
Could it possibly be related to the device itself? I own one of the first versions (RV1109 DDR4 2G), which I imported from China in March 2023.
Since there is currently no option in the web app to schedule a reboot, and I would prefer not to tinker with the system using a cronjob, I am considering using a smart plug to power the iHost off and on at specific times.
Could this cause any problems, since the iHost would be abruptly powered off and restarted?
Has anyone experienced something similar or found a workaround?
I think I have the same original model as you. I do not see this. Does this failure effect the devices connected to Zigbee and the devices connected to wifi?
My thinking is the modem/router for free from my ISP used to assign IP (V4) addresses locally every 72 hours. My guess is that the iHost (which I don’t think has an option in it to assign an IP address) is asking for a new IP address etc. and something is going wrong. Are you able to login to the web interface of the iHost after it goes wrong? If not try assigning it a static address in your main router and seeing if you can ping that address when it goes wrong.
Currently, I have 35 Zigbee devices, as well as an NsPanel and a Sonoff M5-IC connected via the eWeLink Smart Home app, both running over Wi-Fi. I will test whether the issues also occur with these two Wi-Fi devices, as I haven’t checked that yet.
Regarding the internet: I have a static IP address provided by my ISP, and the iHost address is also configured statically. When the problem occurs, I can still access the iHost and even reboot it. Both the web interface and the Cast Dashboard work normally. However, when trying to control a device, I get the error message “Failed to control.”
The issue shouldn’t be related to LAN or Wi-Fi, since the control runs through the Zigbee adapter with the respective protocol.
This problem only started after updating to version 2.6.0. Since then, the error “Configured Zigbee adapter is missing..” sometimes appears, but disappears again shortly after
I am currently running version 2.7.0. I’ve seen this error mentioned several times in the forum.
I would actually like to buy a new device with 4 GB RAM, but the import fees to Brazil are currently just too high … +92% import tax. You end up buying one device for yourself and another for the government
I think that is the firmware version I am using (latest I think) and I never get that error. I think we have the same device but maybe we have different PCB designs. Have you contacted support and asked them to have a look at the iHost logs?
Maybe you can get a Zigbee Dongle and stick it in the USB port. My guess, from how import taxes work here, is that there is a threshold below which it is ignored. I haven’t tried it but Zigbee2MQTT has a docker image that is ARM 32bit. You could then use Node Red to extract information at the MQTT stage (I do this but have Zigbee2MQTT elsewhere) and link a virtual device.
