This is rather a feature request than a bug. When you send a lockAction you 1) know that you sent one and 2) already get a commandResponse and 3) all related state changes. Sending an additional lockEvent would be one more update with something that you already know as sender. But this should be discussed in the MQTT API section and not here.