After sending out a GenericOnOffSet message to a node we are not able to receive updates from that node that are sent as VendorModelMessages.
We have a Lamp device that can also be locked from further interactions. To check if the node is locked we send a VendorModelMessageAcked to that node and from that point on we receive updates about changes in this lock behaviour.
If after sending that VendorModelMessageAcked we sent a command to that lamp with GenericOnOffSet the State in no.nordicsemi.android.mesh.transport.BaseMeshMessageHandler#getState contains a GenericOnOffSet message as mMeshMessage and the library discards all updates to the lock status of the device as unknown.
Is this the intended behaviour? Since the lock behaviour can be triggered through timers, automations and switches having the correct locking state send to the phone at each change is important for our users.
After sending out a GenericOnOffSet message to a node we are not able to receive updates from that node that are sent as VendorModelMessages.
We have a Lamp device that can also be locked from further interactions. To check if the node is locked we send a VendorModelMessageAcked to that node and from that point on we receive updates about changes in this lock behaviour.
If after sending that VendorModelMessageAcked we sent a command to that lamp with GenericOnOffSet the State in no.nordicsemi.android.mesh.transport.BaseMeshMessageHandler#getState contains a GenericOnOffSet message as mMeshMessage and the library discards all updates to the lock status of the device as unknown.
Is this the intended behaviour? Since the lock behaviour can be triggered through timers, automations and switches having the correct locking state send to the phone at each change is important for our users.