Scene auto-disable: Scenes in eWeLink (automations) are designed to act when all their trigger conditions are met, and then they essentially “wait” for those conditions again. So, they don’t remain “enabled” in the conventional sense. They trigger, execute, and become dormant until needed again.
Inching time over one hour: You can actually set up inching-like behavior through a delayed action in a scene, giving you much more flexibility, and the delay can be almost unlimited.
Multiple sensors per RF Bridge in one scene: A very reasonable request. Streamlining scenes by allowing shared triggers would certainly reduce clutter.
DST auto-adjust: Fortunately, this issue is largely resolved in newer firmware versions, which now handle daylight saving time automatically.
Device online/offline as trigger: Definitely a handy feature being able to react when a device goes offline can make automation more resilient.
WPA3 support: This depends heavily on hardware. WPA3 requires support for 802.11w (Management Frame Protection), and many older devices simply don’t have the chip-level capability to support it, even with a firmware update.
IR bridge and weather-based scenes: Totally agree! Adding native weather triggers and improved IR integration would make the ecosystem more powerful and reduce reliance on third-party services like IFTTT.
All in all, some requests are technically challenging or already covered in different ways but the direction you’re pushing toward makes a lot of sense. Count me in for voting on the good ones!