rick/LEDMatrix
1
0
Fork 0
mirror of https://github.com/ChuckBuilds/LEDMatrix.git synced 2026-10-13 10:36:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(mqtt-bridge): brightness changes apply live and touch nothing else

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Chuck
2026-09-17 09:05:21 -04:00
co-authored by Claude Opus 5
parent d284fdeb46
commit 556fb16dca
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
integrations/mqtt_bridge/README.md
+4 -2
View File
@@ -114,5 +114,7 @@ python3 integrations/mqtt_bridge/ledmatrix_mqtt_bridge.py --config integrations/
discovery itself. Discovery is lazy and normally happens because somebody discovery itself. Discovery is lazy and normally happens because somebody
opened the dashboard; without that endpoint a bridge that never does would opened the dashboard; without that endpoint a bridge that never does would
see an empty list. see an empty list.
- Brightness writes `display.hardware.brightness` through `/api/v3/config/main`. - Brightness writes `display.hardware.brightness` through `/api/v3/config/main`,
The display service picks it up on its next restart, not instantly. 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`).