Firmware, PMD, Message Customization.

[nk25719]

Feature Request: Message Customization API
Is your feature request related to a problem? Please describe.
I'm always frustrated when I have to hardcode emergency or status messages (like “a4Urgent Support Now.”) into the firmware, which requires recompiling and re-uploading even for minor changes.

Describe the solution you'd like
I’d like to be able to update predefined message strings (e.g., S1, S2, S3, S4) directly from the web interface via a /messages API endpoint. This allows on-the-fly reconfiguration of messages without modifying firmware.

Describe alternatives you've considered

Hardcoding message strings and recompiling firmware each time (time-consuming, error-prone).
Reading messages from LittleFS at boot (still requires manually editing files).
Using MQTT to push new messages (not reliable without a UI to manage it).

[nk25719]

Completed the Message Customization Feature
1- Web Server Route Added
In setupAPIHandlers() of WebServerManager.cpp, a new POST route /messages was registered.

2- JSON Payload Parsing
When a client sends a POST request with fields S1, S2, S3, S4, the server:

• Uses ArduinoJson to deserialize the body.
• Assigns the values to global messageS1, messageS2, etc. variables.

3- Runtime Update
The new messages take effect immediately — no reboot or recompile needed.

4- Persistence (Optional)
Currently messages are not persisted in LittleFS, but the structure allows adding that easily later by writing to a messages.json file.

5- Client Ready
This route is now frontend-ready. A UI can easily POST the JSON object and customize messages on the fly.