Hi,
I’m a advance user of ewelink.
I have almost 150 sonoff/ewelink devices running daily.
It happened before with one of my MiniR3 (the most used one) and now just happened with more two devices MiniR3: after a some quantity of cicles (switch ON / switch OFF) the device get blocked in OFF mode. No matter you give and order to switch ON, the device promptly is switched OFF.
The quantity of cicles is unknown but I would say a figure around 100 cicles.
The only way to make work normally again is manually reboot. So, manually reboot a sonoff device is cut the power line and reinstall the power line again… if your aren’t at home… not easy.
So, because I don’t believe in a cure for the situation I am asking for a friendly reboot thru software, I mean, an option to give a order to the device to reboot using ewelink app or webewelink.
Here are some questions that may help to see the whole picture.
Does the issue with devices getting stuck in the OFF state occur only with MiniR3 models, or have you observed similar behaviour with other Sonoff/eWeLink devices?
Are the MiniR3 devices used in specific conditions (e.g. high humidity, voltage
fluctuations) that might affect their performance?
Are the MiniR3 devices connected to high-power loads? If yes, what is their power draw and is it within the device’s specifications?
Does the issue occur regardless of how the device is controlled - manually, via the eWeLink app, or through automation?
Have you tried resetting the devices to factory settings? If so, did the issue reappear after some time?
Have you noticed any other unusual behaviours from the MiniR3 devices prior to them getting stuck in the OFF state?
Does the issue affect devices connected to the same Wi-Fi network, or have you seen it happen in other locations as well?
Does the problem occur more often with heavily-used devices (e.g. more daily
switching cycles)?
Have you noticed any difference in behaviour between different units of the MiniR3 (e.g. older vs newer devices)?
I’m very happy you put me all this questions, it’s for me sign of attention to my post content.
So,
only in MiniR3 type, no other.
I have other devices measuring the quality of my power line and I have no record of any faulty situation. All the MiniR3 in question are inside of my house and in the same compartment of the general electrical bord.
No, at all. None of the equipments I have connected to the MiniR3 have high loads. None of them arrive even to 5A! Up to today, This reported issue happened in four MiniR3 devices and the highier load in those four equipments is just 800w, so, 3.5A maximum.
All these MiniR3 in question are being controlled manually and thru automatized scenes. It already happened in both situations. I mean, I detected that the scene told to switch ON and promptly the MiniR3 turned switch OFF, the scene gave, again, the order to switch ON and the MiniR3, once more, immediatly come OFF. Other times, I manually gave the order to switch ON but the MiniR3 promptly came OFF. I tried one, two, three times mannually but always the same outcome, until I manually reboot them. However, in this specific four MiniR3 devices where the issue occured, all of them run the majority of their actions thru automatized scenes, but, repeating myself, not only automatized scenes, also mannual inputs.
Yes, I done it. Not at first and not in all of the four MiniR3 where this issues occurred. But in the MiniR3 with ID 1001439cc5 I reset it to factory setting when the issue came for second time but it didn’t work. it already happened more three times in the same device since then.
No, not at all. Everything works fine up to get stuck in OFF mode.
I have the same IP range for all my sonoff/ewelink devices. I have four access points, all connected to the main router thru wire. The issue already happened in devices linked to different acess points.
Yes, the issue happens in the most used devices. But it’s not just because in the same day you used it 10 times or, even, 20 times. By it self, this “hard-use” in a specific day never brought the problem alive. My suspicious is something related with cache memory or something similar. It’s not a daily issue. Not even a monthly issue. It’s just worrying because when it happens it only gets sorted after you cut the power and get the power in again, and, so far, you can only do it locally and mannualy, reason why I have asked if the “reboot” setting can be added to the firmware.
All my MiniR3 devices where bought, roughly, at the same time, so… hard to say.
It’s a wierd problem. Hard to understand wy it happens. For exemple, I have one MiniR3 always ON. It was ON almost 1 year long and only came OFF due to an global cut o power in the network. No issue came with it during that time, simply works fine.
To finish, and reapeating myself, this issue I’m reporting it’s, probablly, linked to the accumulated number of time that it switch ON/switch OFF, that’s my felling in the matter. But, because is hard to precise the reason, I have suggested to creat the option of gave the order to the device reboot using da APP.
Based on your description, this issue may be related to the device firmware. We recommend submitting a ticket to the SONOFF team through the following link: https://sonoff.tech/support/
They will be able to investigate further and provide assistance.
I noticed a similar problem with measuring sockets, but only with those that had a delayed shutdown set. The set time was ignored and the shutdown always occurred immediately, or rather in the shortest possible time. until the device was restarted.
