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

Merge audit16-core/docs into the September 16 core audit fixes

Browse Source 
# Conflicts:
#	CHANGELOG.md
#	integrations/mqtt_bridge/README.md
This commit is contained in:
Chuck
2026-09-17 09:18:34 -04:00
parent 567a0db21a 708b69a2eb
commit 32542a18b4
35 changed files with 1771 additions and 1413 deletions
Download Patch File Download Diff File Expand all files Collapse all files
integrations/mqtt_bridge/README.md
+7 -4
View File
@@ -114,7 +114,10 @@ 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`,
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`).
- Brightness writes `display.hardware.brightness` by posting
`{"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 (unless `LEDMATRIX_HOT_RELOAD=false`; while
a dim schedule is dimming the panel, the dim level wins until the dim period
ends).