Currently, when the backend server detects that it has lost its connection to the MCU or frontend, it logs a warning that the I/O endpoint was lost. However, it will need to play an audio alarm, and it will also need to record this in the event log. For this issue, we will consider playing of audio alarms from the backend as out-of-scope (to be handled in a separate issue); all we need is generation of an alarm in the event log. We'll also need to create a future issue for the firmware to create an alarm when the backend is lost/unresponsive (i.e. it has not received a new message from the backend within some timeout).
Currently, when the backend server detects that it has lost its connection to the MCU or frontend, it logs a warning that the I/O endpoint was lost. However, it will need to play an audio alarm, and it will also need to record this in the event log. For this issue, we will consider playing of audio alarms from the backend as out-of-scope (to be handled in a separate issue); all we need is generation of an alarm in the event log. We'll also need to create a future issue for the firmware to create an alarm when the backend is lost/unresponsive (i.e. it has not received a new message from the backend within some timeout).