added message, mention scheduler name is optional

docs/Commands.md

@@ -125,6 +125,7 @@ The URL path is `http://<hostname>/api/system/<endpoint>`
 | `commands` | GET | lists the available system commands | no | |
 | `allvalues` | GET | lists all connect devices and sensors and their entity values | no | |
 | `send` | POST | send telegram to the EMS bus | yes | `"XX XX...XX"` |
+| `message` | POST | send a message to the log and MQTT | yes | `".."` |
 | `publish` | POST | MQTT publish all values, and optional HA-configuration or specific for a device | no | `[ha] \| [device]` |
 | `watch` | POST | watch incoming telegrams | no | `<on \|off \| raw \| <type-id(hex)>` |
 

docs/Configuring.md

@@ -147,6 +147,8 @@ The Customization page shows all registered entities and allows to exclude comma
 
 Use the scheduler to call commands at specific intervals. This is useful for example to set the hot water temperature to a higher value in the morning and evening, or do a system restart each week (by using `system/restart` in the Command field).
 
+When creating a scheduler entry, the `name` is optional but it's useful to assign a name and then you can control it via a command (enable/disable) and see the status in the MQTT topic `scheduler_data`.
+
 ![Web](_media/screenshot/web_scheduler.png)
 
 The scheduler can also be used to periodically set values based on another entity value, or even a user-defined custom entity (variable). For example to set the flow temperature of the boiler every minute based on a user managed entity which is controlled externally (e.g. in Home Assistant) it would look like:
@@ -170,6 +172,7 @@ Pay attention to the following rules:
   also for boolean values check if you have to use `0/1`, `off/on`, `OFF/ON`, or `false/true`
 - strings containing special characters have to be written in quotations, e.g. `boiler/pumpmode == "delta-P2"`, to avoid a calculation error on delta minus P2,
   other strings can be written with or without quotations
+- all strings are converted to lowercase
 - commands followed by a divider (`/`) have to be set in parenthesis e.g. `(boiler/seltemp)/2`
 - condition command is only executed on a change of the condition from `false` to `true`. If the condition stays true, the command is not repeated
 - command value can also be a formula

docs/Special-Functions.md

@@ -50,7 +50,7 @@ The EMS-ESP Scheduler can be used to permanently maintain the remote thermostat'
 - `Timer` to `00:00` for triggering as soon as EMS-ESP powers on
 - `Command` is `thermostat/hc1/remotetemp` for heating circuit 1 (or `thermostat/hc1/remotehum` for an RC100H)
 - `Value` is the optimal room temperature for your home, or a command (see below)
-- `Name` can be anything you like
+- `Name` is optional. By giving it a name it can be set remotely as a command and the activation state is published in an MQTT topic.
 
 If you have an external Dallas temperature sensor attached to the EMS-ESP you can set the `value` to this value by using `temperaturesensor/<dallas_id_or_name>` as the `value`.