Why is the deviceType needed in lockState or lockAction request for bridge api? There is a unique nuki id already in the request, shouldnt this be enough information for the bridge to decide which device the request is for? Now, every Api where support for openers is requested needs to be changed.
The alternative to deviceType (based on us wanting 100% backward compatibility for all existing integrations for the Smart Lock) would have been to use some kind of prefix for the opener ID, which would have caused a whole lot of other issues due to the changed length of this value.