Zwave dimmers which use the central scene commandset can capture a double or even triple tap at the device, which removes the problems of cloud latency.
In the US, the new homeseer line can do this and there are a number of community members using it.
In 2017, GE introduced a new line of zwave switches (model numbers beginning with 14 instead of 12) some of which can also do this, but they are just starting to come to market.
In the UK, Devolo makes a device that can do this also.
So it’s doable, but right now only with zwave.
I know I’m a minority opinion in the following, but I think SmartThings should just colorcode devices in the app on the basis of protocol, green for Z wave and red for zigbee and orange for Wi-Fi or whatever. Then colorcode various options and utilities. I think people will figure it out very quickly, and it’s easy for support to work with. I don’t see any reason to pretend that these protocols don’t have significant differences, because they do.
Trying to pretend that everything is exactly the same under the abstraction layer is what leads to People not knowing that they need to update the address tables after they add new repeater devices. Or for that matter, not knowing that different devices repeat for different protocols.
I think you can still have a mass-market friendly user platform without disguising the fact that you’re supporting multiple protocols.
