There’s a patent issue involved. lutron holds the patent on any lighting system that does instant update from the switch to the network controller. This applies to zigbee, zwave, and a couple of other protocols.
This is just a fact. some lighting device manufacturers have licensed the Lutron patent, like Cooper, and therefore they can do instant status updates to the hub.
Other lighting device manufacturers have two ways of getting around this. One has to do with Association groups, but it appears that this is not processed for update status by smartthings.
The other way is to have the hub query the device. That is what pollster does.
Here’s the thing: mesh networks like zwave and zigbee are intended for low traffic networks. Individual devices are pretty dumb, and often sleeping if they are battery operated. The network as a whole is very robust precisely because the hub doesn’t panic if it doesn’t hear from an individual device for a little while. Messages are allowed to bounce around the network and try alternate message routes.
In commercial networks, a typical rule of thumb for a mesh network is to limit polling to 5% of total traffic. However, for local processing in your own home, if you want to poll more often, that’s up to you. Because you are so dramatically increasing total traffic on your network, you do run the risk of lost or delayed messages, and also increase the risk that messages will arrive out of sequence. But again your choice.
When your system is dependent on cloud services, though, then all those polling requests create traffic for the cloud as well. So the cloud services provider may put limits on how often you can do Polling.
Phillips, for example, even though it’s local processing, limits polling from the huge bridge, and basically updates status about every 15 minutes. The assumption is that for human beings if they’re in the room, they can see whether the light is on or not. If they’re not in the room, The fact that the status panel is slightly out of sync with the actual physical lights probably doesn’t matter much.
If you have a use case which requires absolutely precise constant monitoring of an end device, then you probably should be using something other than a mesh network. Wi-Fi in a star network, Bluetooth as point-to-point are both good for this purpose.
For Zigbee lights, I would myself tend to follow the experts, in this case Phillips, and poll each device once every 15 minutes. But that’s just me.
Meanwell, regarding this particular switch, the double tap is used you need to join or leave a network. It’s treated differently by the device itself than a single tap. So it’s not surprising if you can’t do the same thing with a single tap.