Fix was seemingly delayed because D3 team initially couldn't recreate the issue.
This was because freshly added HZ-KPCN instances use the newer definition.
They were provided with an old D3 Archive that had the previous HZ-KPCN definitions.
They are now working on having D3 upgrade the hardware definitions upon opening older systems.
In other words, in the meantime, if you don't want to roll back DevDB while waiting for a fix (I don't have ETA ATM)...
You can also just add new HZ-KPCNs, move over the programming, and delete the old instances.
Granted, viability of this workaround is probably dependent on qty of keypads & time commitment etc.
Dave H - Crestron True Blue Tech Support Engineer Since 2014