# Possible bug ? Mopidy stops sending events via Websocket

**URL:** <https://discourse.mopidy.com/t/possible-bug-mopidy-stops-sending-events-via-websocket/5566>\
**Category:** Misc\
**Created:** [September 26, 2022, 7:43pm UTC](https://discourse.mopidy.com/t/possible-bug-mopidy-stops-sending-events-via-websocket/5566 "2022-09-26T19:43:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gregorv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/gregorv/32/2296_2.png) [@gregorv](https://discourse.mopidy.com/u/gregorv)\
**Post date:** [September 26, 2022, 7:43pm UTC](https://discourse.mopidy.com/t/possible-bug-mopidy-stops-sending-events-via-websocket/5566/1 "2022-09-26T19:43:43Z")

</div>

May be, I found an issue. At least in my environment mopidy stops sending events via WebSocket API when the tracklist is cleared (e.g. via ‘core.tracklist.clear’), while a track is beeing played.  
Mopidy stops sending event to all connected http-clients.  
This happens without a notice to the client - the very last event is a play stop message. The connection is still established. A reconnect does not solve the problem  
To fix this a restart of mopidy is requird. Once running again the clients can automatically reconnect.  
OK, it is not normal handling to clear a track while playing this track, but at least that shoud be metioned in the documentation. It has an impact on all connected http-clients.  
My environment: Raspi 4B, 1G, RaspiOS 64 Bit Bullseye light, Mopidy 3.1.1 interestingly a client still can send JSON-RPC commands ( I use a different connection) and receive results after it stopped to send events.

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/system/32/1_2.png) [@system](https://discourse.mopidy.com/u/system)\
**Post date:** [March 28, 2023, 7:44am UTC](https://discourse.mopidy.com/t/possible-bug-mopidy-stops-sending-events-via-websocket/5566/2 "2023-03-28T07:44:24Z")

</div>

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.