Hi, I have an idea that I’d like to bring to the eWelink team.
In a smart home environment, it is common to have devices (e.g., switches) that are activated by smart scenes to turn on/off a signal LED.
In this case, the device powering the signal LED should only be controlled by a smart scene, not manually by the user.
To achieve this, it would suffice to add an option to the device settings that enables control only by a smart scene.
What do you think about introducing this feature in a future software release?
Why would there be a need for this?
I think that when a warning light comes on in a smart scene, it shouldn’t be switched off manually because you might accidentally turn off an important warning before removing the cause. I suggest giving users the ability to enable or disable this feature according to their specific needs.
1 Like
Very niche feature. Could be, although I personally don’t feel the need for it.
This can currently be achieved by proper device segregation and a little attention on the user’s side.
1 Like
such a function belongs to higher automation and certainly has its value, perhaps it could be if a premium plan for a higher level than it is now was introduced
1 Like
SONOFF devices and eWelink platform must evolve to meet professional standards.
I work in the field of automation and robotics every day, so I know how far Sonoff and Ewelink would have to go. There are a lot of little things that make things professional and they are not cheap at all. I just expressed the opinion that a higher subscription plan could be created than the current one, which would pay for the development of such a feature.
Perhaps. Except that the eWeLink platform is not a professional platform. It is designed for home use. So what standards are you referring to?
1 Like
Even devices designed for home use deserve professional treatment. In short, building automation is not a game but something serious.
Oh, absolutely—thrilling, exhilarating, edge-of-your-seat excitement! Well… maybe not for everyone. But hey, that doesn’t change the fact that eWeLink, despite its very serious demeanor, isn’t exactly the textbook definition of a professional platform. It’s got the suit and tie, but maybe forgot the briefcase 
1 Like
Thank you for your creative contribution!
From what I understand about how these systems work, it might not be technically feasible. The thing is, the device doesn’t actually know who is controlling it — whether it’s a scene, manual tap, or API call. It just receives the command, executes it, and then reports the new state back to the cloud. So there’s no real way for the device to block certain types of control in real time.
You’re right about the current FW. However, I don’t think it would be difficult to modify the FW to introduce this feature.
1 Like
The problem could be solved only by locking the device in the control application, without modifying the firmware, the device lock icon in the settings and the control graphic in the application would be gray or with a lock symbol and would not be marked, of course, this would not limit the control in scenes because it would only be about turning off the touch button of the graphic in the application. In fact, it would only become a control light.
2 Likes
I find your suggestion very useful and simple to implement the required feature.
1 Like
When you opt for the external power, nei mini r4 has the “detach relay” option in practice where the relay remains independent of the electrical switch. In this way you can command the ewelink alone
that’s something else the purpose of the thread is blocking from the application by the user, not by the scene and not by the real hw contact
1 Like
exactly!
Ah, thanks for clarifying — now I see that you’re talking about disabling manual control in the app (UI level), not actually blocking hardware or scenes. That makes sense! I’ll pass this suggestion along to our product team so they can evaluate further.Thx for the idea!
1 Like
Thanks a lot for your kind support