I found a simple workaround, although I'm not sure if it's the best solution. One of the events that can be triggered by the Websocket server is on_pong. Furthermore, if you set silence_max when creating the Websocket server, it periodically pings all clients, waiting for a pong response. This pong can then be used to trigger a message to all clients.