Agreed. We’ll have a look at TLS / MQTTS once the basic setup works.
Yes. From implementation point of view it does not make much difference, but we won’t implement both. So it is either JSON or separate topics. And which version to choose depends pretty much on your feedback here in the group (i.e. which ones are easier to integrate into the platform with which everyone over here works).
We’ll remove it completely. The ringactionTimestamp should be sufficient.
First beta will be Smart Lock 3.0 Pro only. It might make it later on into the bridge, so it would be wise if the specification takes that into consideration and also theoratically would work with the bridge.
Only the SL3P has an IP stack and holds a direct connection to a server. All other Nuki devices are indirectly connected via the bridge. So a server connected state for any other device would just mirror the connection state of the bridge. But yes, it might make sense to add this too for the other products.
If you want to execute a specific lock Action you need to use the lockAction topic. unlock / lock are specifically designed to be used with the simple lock action which will automatically decide if unlock or unlatch is called based on the door handle setting.
As written above, you can contribute to the API specification. Unfortunately the SL3P and Bridge use completely different technologies, therefore none of the code can be reused and we need to start somewhere.