From 556fb16dca25c03891161b86161c43786ae97da3 Mon Sep 17 00:00:00 2001 From: Chuck <33324927+ChuckBuilds@users.noreply.github.com> Date: Thu, 17 Sep 2026 09:05:21 -0400 Subject: [PATCH] docs(mqtt-bridge): brightness changes apply live and touch nothing else The display service's hot reload applies a saved brightness within a few seconds, and /config/main no longer resets other display settings on a brightness-only JSON body. Co-Authored-By: Claude Opus 5 --- integrations/mqtt_bridge/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/integrations/mqtt_bridge/README.md b/integrations/mqtt_bridge/README.md index 29d31b04..d3b66980 100644 --- a/integrations/mqtt_bridge/README.md +++ b/integrations/mqtt_bridge/README.md @@ -114,5 +114,7 @@ python3 integrations/mqtt_bridge/ledmatrix_mqtt_bridge.py --config integrations/ discovery itself. Discovery is lazy and normally happens because somebody opened the dashboard; without that endpoint a bridge that never does would see an empty list. -- Brightness writes `display.hardware.brightness` through `/api/v3/config/main`. - The display service picks it up on its next restart, not instantly. +- Brightness writes `display.hardware.brightness` through `/api/v3/config/main`, + and changes nothing else. The running display service notices the saved + config within a few seconds and applies the new brightness without a + restart (unless `LEDMATRIX_HOT_RELOAD=false`).