I have an R5 and I created a virtual button on EWELINK. I created two scenes linked to the virtual button to open and close all my shutters. I associated button 1 on the R5 with the virtual button: one for ON mode to open and the other for OFF mode. When I press the physical button on the R5, it activates the virtual button correctly, but the associated scene doesn’t execute. How can I fix this, please?
Your description with the virtual switch shows how easy it is to overcomplicate and twist the logic 
This element is indeed described as “Click below to simulate the actions of pressing a physical button” and it has three modes: single, double and long press. In practice, this means it can be used as a button simulator, but it does not work like a classic “tap to run” trigger. In eWeLink, automation requires assigning the executing devices, and beforehand there must be a scene that makes pressing a button on the R5 trigger an action in the virtual switch. This creates an extra layer: R5 → scene → virtual switch → another scene → devices. No wonder the final effect gets lost.
The simplest and most reliable solution is to create two Tap to run scenes:
- one assigned to the ON action on button 1 of the R5 (e.g. “Open shutters”),
- the other assigned to the OFF action on the same button (e.g. “Close shutters”).
This way, the R5 triggers the scenes directly, without the intermediary of the virtual switch. It works right away and in line with how Sonoff designed the R5 – as a scene trigger, not as a controller for virtual devices.
In summary: the virtual switch in eWeLink is more of a tool for testing or simulating a button, not for running “tap to run” scenes. The best approach is to simplify the configuration and assign the scenes directly to the R5. It always works as expected 
Thanks for the feedback. Actually, the purpose of the virtual button is to be able to trigger a scene with the R5, but also, if needed, to be able to do so on the phone using the app, since the R5 doesn’t have a physical button in eWeLink. Pressing button 1 on the R5 opens the shutters via one scene, and pressing button 3 closes them via another scene. I found a solution: to include the activation/deactivation of the virtual button within the scene’s logic.
Tap to Run works great from the phone screen, NSPanel and NSPanel Pro screens, and eWeLink Web. Choose the simpler solution. Try it out.
Your solution is inefficient and unnecessarily multiplies entities. It’s a bit like adding a second light switch that you have to activate before the first one can work. The virtual button becomes a redundant intermediary. Since the Tap to run scene already supports both the R5 and the app, there is no need to wrap it with an additional button state. This is redundancy that adds no value.
Yes, the “push to execute” function works, but remotely it’s impossible to know the status of the action. The virtual button only shows whether the shutters are closed or not; otherwise, you have to go into the individual devices.
I don’t understand or you’re missing the point.
Yes, the “push to execute” function works, but remotely it’s impossible to know the action’s status. The virtual button only shows the current state, on or off. Otherwise, you have to go into the different devices.