enable/disable system services and settings via API

[proddy]

Triggered by #2168 two new commands were added in 3.7.1 to control the shower (/api/system/showeralert and /api/system/showertimer).

A more generic approach is to extend the new action command, moving this from /rest/ to a HTTP POST API /api/system so we can use a format like {"action":'enable|disable', param:'ntp|ap|syslog|showeralert...'}.`

This will remove 3 EMS-ESP Commands and free up some memory.

[proddy]

Request to extend this to turn LED on and off as well

#2194

[MichaelDvP]

If i understand right, the appoach with action is API only and can not used via console or mqtt.
I've made a alternative appoach withing the command structure. Please check and tell what do you think about it.
30fca2a

[proddy]

This is a good approach. My idea was to originally move action from /rest to /api and expose it as a new system command called service so it can be called via API, MQTT and the Console via call system action [n]. But this approach is also perfectly fine.

I would only keep things simple and have the cmd be:

showertimer
showeralert
led
analog
mqtt
ntp
ap
syslog
etc....

as this makes it easier for the end user.

and keep to on/off, so remove txmode. Changing that real-time can be dangerous.

[MichaelDvP]

I think the commands should always be the same as api read of the entity. E.g.
api/system/settings/hideled should show (there is a camelCase bug in my dev for writeable):

{
  "name": "hideLed",
  "circuit": "settings",
  "readable": true,
  "writeable": true,
  "visible": true,
  "value": false,
  "type": "boolean"
}

So the command also has to be api/system/settings/hideled with value.
Using different commands does not allow automatisation like thomas do it in his ioBroker adapter:

• reading the system/info
• reading system/<path>/<entity>
• create entities depending on readable/writeable settings

as this makes it easier for the end user.

ot sure, as i implemented the shower settings without prefix the user extected them as settings/showeralert and i have to explain why this is not normal scheme.

[proddy]

okay, that actually makes a lot of sense. What do you want me to do next, test?

[proddy]

The doc also needs to be updated.