Hi @nayelyz
I think this the issue, discussed here
Just to recap, the requirement to re-emit events for each capability doesn’t seem the best way to handle refresh. Please let me elaborate why.
- Refresh normally sends read attribute request to the device and updates the capability when response is received.
a. Some devices (especially Tuya) do not support that for all capabilities
b. Some devices might not response fast enough
c. Sleepy devices will not respond in most cases - For virtual devices this would mean sending a lot of unnecessary messages
- As @TAustin mentioned, re-emitting events might unnecessary trigger routines
Please take those points into consideration.
Thanks