Michel2/ESPEasy
1
0
Fork 0
mirror of https://github.com/letscontrolit/ESPEasy.git synced 2026-07-28 04:07:47 +00:00
Code Issues Releases Activity

Added documentation for [PLUGIN#MCP#PINRANGE#x-y]

Browse Source 
Added documentation for [PLUGIN#MCP#PINRANGE#x-y] and [PLUGIN#PCF#PINRANGE#x-y]
This commit is contained in:
Plebs
2021-02-14 20:04:52 +01:00
parent 77bdb0b5db
commit c7d8300860
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/source/Rules/Rules.rst
+10
View File
@@ -474,6 +474,16 @@ You must not use the task names ``Plugin``, ``var`` ``int`` as these have specia
``Plugin`` can be used in a so called ``PLUGIN_REQUEST``, for example:
``[Plugin#GPIO#Pinstate#N]`` to get the pin state of a GPIO pin.
``[Plugin#MCP#Pinstate#N]`` to get the pin state of a MCP pin.
``[Plugin#PCF#Pinstate#N]`` to get the pin state of a PCF pin.
For expanders you can use also the following:
``[Plugin#MPC#PinRange#x-y]`` to get the pin state of a range of MCP pins from x o y.
``[Plugin#PCF#PinRange#x-y]`` to get the pin state of a range of PCF pins from x o y.
``Var`` and ``int`` are used for internal variables.
The variables set with the ``Let`` command will be available in rules
as ``var#N`` or ``int#N`` where ``N`` is 1..16.