Just a few thoughts without any emotions…I would really appreciate a clear and honest answer.
From what I understand Nuki says there is no real difference between 1.0 and 2.0 Versions of the Bridge, and therefore the hppt 503 effect is the same with both locks and was always there, am I right?
I tested the behaviour with a Nuki 1.0 Combo and a Nuki 2.0 Combo - both with latest FW for the lock and bridge.
What I found out - 503 errors occurs on both version, that’s right. But one big difference is that the http api of the 1.0 bridge does not crash whe you are penetrating the api with lockaction commands. (which only means I send a curl lockaction → lock, wait untl the lock has finished the action and send an new curl action to unlock, and again a few times). During the callback you get the 503 error when you send new action commands as long as the callback is finished. After finishing callback It executes the command again.
With the 2.0 Combo the bridge does not work as stable when penetrating it. The callback lasts a litle bit longer and sometimes the api does not react anymore and even the bridge reboots.
So from my point of view there is defenitly a difference.
So my question is: Can you confirm the described beahviour and because you are already working on a new FW to fix this problem for quite a long time will this new version be at least as stable as the Bridge 1.0?
Just to be clear: This is a lock - so it has to be 100% reliable. If it’s not nobody can trust it and it’s useless.