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

docs(mqtt): brightness saves apply via hot reload and leave other settings alone

Browse Source 
The bridge README said brightness is applied on the display's next
restart; the display controller's config hot reload applies it within
seconds. It also now states that the bridge's partial JSON save changes
only brightness (the /config/main merge fix in this change set).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Chuck
2026-09-17 09:06:33 -04:00
co-authored by Claude Opus 5
parent 945d1997aa
commit 2e031ea740
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
integrations/mqtt_bridge/README.md
+6 -2
View File
@@ -114,5 +114,9 @@ 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` by posting
The display service picks it up on its next restart, not instantly. `{"brightness": N}` to `/api/v3/config/main`. A JSON save changes only the
keys it sends, so the other display settings are left as they were. The
display service's config hot reload notices the change within a few seconds
and applies it without a restart (while a dim schedule is dimming the panel,
the dim level wins until the dim period ends).