From f1a1c0edc1a740ac4fae1df395b8e5eb1801f025 Mon Sep 17 00:00:00 2001 From: Floris Jan Date: Wed, 7 Oct 2020 08:43:15 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a3ef9e3..d0b639a 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ or if you want to for the development (beta) branch: The extension subscribes to all zone updates and pushes all info it gets from the Zone object found on https://roonlabs.github.io/node-roon-api-transport/Zone.html defined by the node-roon-api-transport service. It prepends the data with "roon/[zone-name]/...". -The MQTT topci for the 1 Line Now Playing information for a zone called Zone1 is: `roon/zone1/now_playing/one_line/line1`. +The MQTT topci for the 1 Line Now Playing information for a zone called Zone1 is: `roon/Zone1/now_playing/one_line/line1`. As the characters +, /, # and space are illegal MQTT topic characters, those will be replaced by -. So if the name of a zone is `Kitchen / Living Room` you should use the topic `Kitchen---Living-Room` when subscribing and/or publishing. The same logic applies to the `[output-name]` descibed below.