As a result of bumping zwave-js-server-python in core, we learned that the API outputs and inputs didn't map well to the zwave-js model. The primary change is that we've switched from camel case to snake for some of the provisioning APIs and need to account for that here. Interest...