Hub executes command but returns no (or wrong) response / acknowledgement – command appears to be silently ignored

[JuniorJacki]

Describe the bug

The hub physically executes almost every command correctly (motor turns, display changes, sound plays),
but randomly one command gets no response/acknowledgement from the hub.

Internally RemoteBrick waits for an ACK message from the hub after every command.
In these random cases:

• the hub does execute the command (you can see it)
• but no ACK (or a wrong/corrupted one) is sent back
• RemoteBrick therefore treats the command as failed or not done → next queued commands are blocked or discarded
• from the user’s point of view the command simply “does nothing” even though the hub actually did it