From: Mike Brady <4265913+mikebrady@users.noreply.github.com>
Date: Mon, 7 Feb 2022 12:57:22 +0000 (+0000)
Subject: Update RELEASENOTES-DEVELOPMENT.md
X-Git-Tag: 4.1-rc1~24^2~284
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bd55f1e42683556426f51e7a5ad2d98ec6b9d0e5;p=thirdparty%2Fshairport-sync.git

Update RELEASENOTES-DEVELOPMENT.md
---

diff --git a/RELEASENOTES-DEVELOPMENT.md b/RELEASENOTES-DEVELOPMENT.md
index 4d2e79b7..90cbefbd 100644
--- a/RELEASENOTES-DEVELOPMENT.md
+++ b/RELEASENOTES-DEVELOPMENT.md
@@ -1,3 +1,9 @@
+Version-4.1-dev-191-ge07c202b
+====
+#### Enhancement
+* This enhancement relates to MQTT with empty payloads. Many MQTT brokers and clients treat messages with empty payloads in a special way. For instance, [MQTT Explorer](http://mqtt-explorer.com) hides messages with empty payloads and [Node-RED](https://nodered.org) seems to use them to release and garbage-collect data received previously.
+Many Shairport Sync messages contain no extra data and so would naturally have empty payloads. This is causing problems -- see [#1425](https://github.com/mikebrady/shairport-sync/issues/1425) and [#1375](https://github.com/mikebrady/shairport-sync/issues/1375). To avoid these problems, a short "dummy" payload consisting of the character string "--" is now added to MQTT messages that contain no extra data. This can be changed with a new MQTT option in the configuration file: `empty_payload_substitute`. Thanks to [DOCaCola](https://github.com/DOCaCola) and [UMB8998](https://github.com/UMB8998) for reporting on this.
+
 Version-4.1-dev-188-gf135d857
 ====
 #### Bugfixes