There is a simple solution to this problem then.
throw this garbage out of the window.
There is no way in 2019 a device should only have one connection available…
this is utterly useless for a product like this.
this kind of of problems should not be solved at the end users level.
either make the choice to remove the API, or just make one that works.
and the fact that your V1 did not have this problem and your V2 has,
makes it the more not understandable.
And indeed I am better of using an other lock if this can not be fixed.