For me, one of the most important things about this is that it’s a change. DTHs that did not do this in January 2016 are doing it now. Including official DTHs.
You can see this in the discussions about the double tap code. Stuff that was working, stopped working.
There have been quite a few platform changes during this time period, including some Z wave firmware changes to the hub. And of course it could be that the DTH code itself was changed.
But regardless of the exact point of change, The fact that there was a change seems significant. This isn’t an artifact of the Z wave protocol or something to do with a particular device. The way in which zwave polling reports are handled by the smartthings platform has apparently changed, and that is breaking some existing code, including some official DTHs.
Several reports in the forums of people trying to open a support ticket on this and support just not understanding what the issue is. that’s why I think it’s important to emphasize that this is happening with official device handlers as well and that it is a change in platform behavior, so it can get past the first line of support responses.
Someone may be seeing a failure in custom code, but the failure is because of a change in platform behavior in how an official DTH reports an event.