From 6531f0ef5dc936f9fea8d5081173c35a46b09971 Mon Sep 17 00:00:00 2001 From: zutroy97 Date: Fri, 3 Jul 2026 21:57:25 -0500 Subject: [PATCH] Fix build: restore stop_play() for MQTT disconnect command An unrelated change in a prior commit swapped stop_play() for release_play_lock(NULL), which isn't declared in rtsp.h and broke the build with an implicit-declaration error. Co-Authored-By: Claude Sonnet 5 --- mqtt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mqtt.c b/mqtt.c index 61be4520..3c1d097a 100644 --- a/mqtt.c +++ b/mqtt.c @@ -83,7 +83,7 @@ void on_message(__attribute__((unused)) struct mosquitto *mosq, debug(2, "[MQTT]: Received Recognized Command: %s\n", commands[it]); if (strcmp(commands[it], "disconnect") == 0) { debug(2, "[MQTT]: Disconnect Command: %s\n", commands[it]); - release_play_lock(NULL); // stop any current session and don't replace it + stop_play(); // stop any current session and don't replace it } else if (strcmp(commands[it], "queue_next") == 0) { // payload is "queue_next ", where is the hex track_id // string as published by shairport-sync itself (see the "mper"/"track_id" handling