In the implementation of NmtMaster.on_heatbeat, is it deliberate that the callbacks are called before the _state of the class is updated and waiters notified? The emcy.py implementation is opposite., where it process the data, updates the class state, notify waiters and calls the callbacks.

When adopting for async, these callbacks will be deferred for later execution. If it is expected that the callbacks run before the class state (like _state) is updated, I will need to adopt specially for that. Otherwise I propose changing the order in NmtMaster.on_heartbeat to mirror the order in EmcyConsumer.on_emcy.

@christiansandberg I see from git blame that this is your code. Your input would be much appreciated. Thanks.

edit:
The lock is held while the callbacks of on_heartbeat() is called, while on_emcy its not. Is that also of importance?