- Description
- Getting started
- Blocks
- System blocks
- Actions Blocks
- Send to Blocks
- Date and Time blocks
- Convert blocks
- Trigger
- Timeouts
- Logic
- Loops
- Math
- Number value
- Arithmetical operations +-*/^
- Square root, Abs, -, ln, log10, e^, 10^
- sin, cos, tan, asin, acos, atan
- Math constants: pi, e, phi, sqrt(2), sqrt(1/2), infinity
- Is even, odd, prime, whole, positive, negative, divisibly by
- Modify variably by value plus or minus
- Round, floor, ceil value
- Operations on the list of values: sum, min, max, average, median, modes, deviation, random item
- Modulus
- Limit some value by min and max
- Random value from 0 to 1
- Random value between min and max
- Text
- Lists
- Colour
- Variables
- Functions
Blockly is a visual editor that allows users to write programs by adding blocks together. It is designed for people with no prior experience with computer programming.
Control state on change of some other state
This is the classical rule to switch something ON or OFF on other event.
Here the light will be switched on or off if the motion was detected or motion detector sends IDLE state.
First of all insert block "Triggers=>Event: if object". Select object ID to use this state as trigger for rule.
Add to trigger other block - "System=>Control" and select in dialog other state that must be controlled by event.
Insert into control block the "System=>Get value of state" block and select in dialog the "Motion" object to write the value of this state into "Light"*[]:
There is a special variable **value"" in trigger block. It is always defined there and you can use this variable for your need. It consist actual value of triggered state and you can create simpler rule by using "Variable=>item" block and renaming it into "value".
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="s7s**k+Cc_KjDnJW`(h~" x="12" y="63">
<field name="COMMENT">Switch light ON or OFF it motion detected or IDLE</field>
<next>
<block type="on_ext" id="#}:B(M-o5:/]k,_msr%y">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="o~6)!C0IVy{WD%Km(lkc">
<field name="oid">javascript.0.Motion</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="control" id="(ZqzhS_7*jGpk;`zJAZg">
<mutation delay_input="false"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">FALSE</field>
<value name="VALUE">
<block type="get_value" id="a-E@UcwER=knNljh@:M/">
<field name="ATTR">val</field>
<field name="OID">javascript.0.Motion</field>
</block>
</value>
</block>
</statement>
</block>
</next>
</block>
</xml>Switch light on by motion and switch off in 10 minutes if no motion detected.
If state "Motion" was updated with value true do:
- switch "Light" on
- start the delayed set in 10 minutes to switch "Light" off and clear all the delayed sets for this state
You can notice, that the flag "clear running" is set by last command. This clears any running timers for this state and the timer will be started anew.
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="s7s**k+Cc_KjDnJW`(h~" x="112" y="63">
<field name="COMMENT">Switch light ON and OFF in 10 minutes of IDLE</field>
<next>
<block type="on_ext" id="#}:B(M-o5:/]k,_msr%y">
<mutation items="1"></mutation>
<field name="CONDITION">true</field>
<field name="ACK_CONDITION">true</field>
<value name="OID0">
<shadow type="field_oid" id="o~6)!C0IVy{WD%Km(lkc">
<field name="oid">javascript.0.Motion</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="control" id="(ZqzhS_7*jGpk;`zJAZg">
<mutation delay_input="false"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">FALSE</field>
<value name="VALUE">
<block type="logic_boolean" id="%^ADwe*2l0tLw8Ga5F*Y">
<field name="BOOL">TRUE</field>
</block>
</value>
<next>
<block type="control" id="=]vmzp6j^V9:3?R?2Y,x">
<mutation delay_input="true"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">TRUE</field>
<field name="DELAY_MS">600000</field>
<field name="CLEAR_RUNNING">TRUE</field>
<value name="VALUE">
<block type="logic_boolean" id="!;DiIh,D]l1oN{D;skYl">
<field name="BOOL">FALSE</field>
</block>
</value>
</block>
</next>
</block>
</statement>
</block>
</next>
</block>
</xml>Send email if outside temperature is more than 25 grad Celsius.
Explanation:
First we must to define the variable to remember if the email yet sent for actual temperature alert or not and fill it with "false". Then we subscribe on changes of temperature. We can execute our rule periodically, but is is not so effective.
If temperature was changed we compare its value with 25 and check if the email yet sent or not. If email is not sent, we remember, that email sent and send the email. Of course email adapter must be installed and configured before.
If the temperature less than 23 grad, reset "emailSent" flag to send email by next temperature alert. We compare temperature with 23 to do not sent emails every time if temperature fluctuate about 25 grad.
To create the "if ... else if ..." block you must click on the gear icon and add required parts to "IF" block.
You can specify comment for every block by selecting "Add comment" in context menu. You can later open the comments by clicking on the question mark icon.
You can collapse some big blocks for better code presentation by selection in context menu "Collapse Block".
Sample to import:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="r53:ZiP]3DYe;Ly;@!v5" x="87" y="13">
<field name="COMMENT"> Send email if outside temperature is more than 25 grad Celsius.</field>
<next>
<block type="variables_set" id="oyEg!Z7~qid+!HYECD8C">
<field name="VAR">emailSent</field>
<value name="VALUE">
<block type="logic_boolean" id="gakxd?9T354S1#_(=)%K">
<field name="BOOL">FALSE</field>
</block>
</value>
<next>
<block type="on_ext" id="DR}w0I%EUL-FCI%`w5L4">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION">true</field>
<value name="OID0">
<shadow type="field_oid" id="}TdS?2Lg~Mt[0!o0iMG.">
<field name="oid">javascript.0.Outside_temperature</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="controls_if" id="rBBI(VLLLRnwd|ys59si">
<mutation elseif="1"></mutation>
<value name="IF0">
<block type="logic_operation" id="B5R%#,6F,xYI1gB!jjq|">
<field name="OP">AND</field>
<value name="A">
<block type="logic_compare" id="I=R,TaB*pge*l#j|[HZ0">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="wd1I0gzqle,y-:h@GF)v">
<field name="VAR">emailSent</field>
</block>
</value>
<value name="B">
<block type="logic_boolean" id="q5~/ZIb))r`w]/RaSXUu">
<field name="BOOL">FALSE</field>
</block>
</value>
</block>
</value>
</block>
</value>
<statement name="DO0">
<block type="variables_set" id="i):z[{@|*;4zOruzXH46">
<field name="VAR">emailSent</field>
<comment pinned="false" h="80" w="160">Remember, that email was sent</comment>
<value name="VALUE">
<block type="logic_boolean" id="56A@]MZKiuL(iuuj)MRI">
<field name="BOOL">FALSE</field>
</block>
</value>
<next>
<block type="email" id="3J#TXZ`oei_NMEL,_w8K">
<field name="INSTANCE"></field>
<field name="IS_HTML">FALSE</field>
<field name="LOG">log</field>
<value name="TO">
<shadow type="text" id="j*x?kanQQyGH/pN,r9B2">
<field name="TEXT">[email protected]</field>
</shadow>
</value>
<value name="TEXT">
<shadow type="text" id="QE(T_Z]{=o8~h~+vz!ZU">
<field name="TEXT">Temperature is over 25°C</field>
</shadow>
</value>
<value name="SUBJECT">
<shadow type="text" id="/_AxN7@=T|t@XW.^Fu1(">
<field name="TEXT">Temperature alert</field>
</shadow>
</value>
</block>
</next>
</block>
</statement>
<value name="IF1">
<block type="logic_compare" id="S?0|;{3V3!_rqUk]GJ4)">
<field name="OP">LT</field>
<value name="A">
<block type="variables_get" id="IJwq1,|y;l7ueg1mF{~x">
<field name="VAR">value</field>
</block>
</value>
<value name="B">
<block type="math_number" id="m(.v?M3ezTKz(kf5b9ZE">
<field name="NUM">23</field>
</block>
</value>
</block>
</value>
<statement name="DO1">
<block type="variables_set" id="M0{G}QBtF!FYrT,xWBnV">
<field name="VAR">emailSent</field>
<value name="VALUE">
<block type="logic_boolean" id="ti#H=_:;-XRC%CzR/+/0">
<field name="BOOL">FALSE</field>
</block>
</value>
</block>
</statement>
</block>
</statement>
</block>
</next>
</block>
</next>
</block>
</xml>
This block does nothing except prints line into the log. You can use it for debugging of your script.
Like this one:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="K|2AnJ|5})RoNZ1T%Hh#" x="38" y="13">
<field name="COMMENT">Print time into log every second</field>
<next>
<block type="timeouts_setinterval" id="LNsHTl,!r6eR8J9Yg,Xn">
<field name="NAME">interval</field>
<field name="INTERVAL">1000</field>
<statement name="STATEMENT">
<block type="debug" id=".oLS7P_oFU0%PWocRlYp">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="X^Z/.qUry9B5Rr#N`)Oy">
<field name="TEXT">test</field>
</shadow>
<block type="time_get" id="TPo6nim+=TBb-pnKMkRp">
<mutation format="false" language="false"></mutation>
<field name="OPTION">hh:mm:ss</field>
</block>
</value>
</block>
</statement>
</block>
</next>
</block>
</xml>You can define 4 different levels of severity for message:
- debug (the debug level of javascript adapter must be enabled)
- info (default, at least info log level must be set in javascript instance settings)
- warning
- error - will be always displayed. Other severity levels can be ignored if severity of logging in javascirpt adapter is higher.
Comment your code to understand it later better.
It does nothing, just a comment.
You can write the state with two different meanings:
- to control something and send command to end hardware (this block)
- to update some state to just inform about e.g. new temperature (next block)
Typical usage of block:
The object ID must be selected from dialog and the value must be defined too. Depends on the type of state the value can be string, number or boolean.
You can read the explanation here.
This block writes command into state (ack=false). Additionally, the delay can be specified. If delay is not 0, the state will be set not immediately but after defined in milliseconds period of time.
You can stop all running delayed sets by issuing of control command.
E.g. in following schema the state "Light" will be controlled only once (in 2 seconds):
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="K|2AnJ|5})RoNZ1T%Hh#" x="38" y="13">
<field name="COMMENT">Will be executed only once</field>
<next>
<block type="control" id="IWceY@BFn9/Y?Ez^b(_-">
<mutation delay_input="true"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">TRUE</field>
<field name="DELAY_MS">1000</field>
<field name="CLEAR_RUNNING">FALSE</field>
<value name="VALUE">
<block type="logic_boolean" id="I/LUv5/AknHr#[{{qd-@">
<field name="BOOL">TRUE</field>
</block>
</value>
<next>
<block type="control" id=".Ih(K(P)SFApUP0)/K7,">
<mutation delay_input="true"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">TRUE</field>
<field name="DELAY_MS">2000</field>
<field name="CLEAR_RUNNING">TRUE</field>
<value name="VALUE">
<block type="logic_boolean" id="B?)bgD[JZoNL;enJQ4M.">
<field name="BOOL">TRUE</field>
</block>
</value>
</block>
</next>
</block>
</next>
</block>
</xml>But in this schema the state "Light" will be controlled twice (in 1 second and in 2 seconds):
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="K|2AnJ|5})RoNZ1T%Hh#" x="38" y="13">
<field name="COMMENT">Will be executed twice</field>
<next>
<block type="control" id="IWceY@BFn9/Y?Ez^b(_-">
<mutation delay_input="true"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">TRUE</field>
<field name="DELAY_MS">1000</field>
<field name="CLEAR_RUNNING">FALSE</field>
<value name="VALUE">
<block type="logic_boolean" id="I/LUv5/AknHr#[{{qd-@">
<field name="BOOL">TRUE</field>
</block>
</value>
<next>
<block type="control" id=".Ih(K(P)SFApUP0)/K7,">
<mutation delay_input="true"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">TRUE</field>
<field name="DELAY_MS">2000</field>
<field name="CLEAR_RUNNING">FALSE</field>
<value name="VALUE">
<block type="logic_boolean" id="B?)bgD[JZoNL;enJQ4M.">
<field name="BOOL">FALSE</field>
</block>
</value>
</block>
</next>
</block>
</next>
</block>
</xml>
This block is similar to control block, but it toggles the value. From true to false and vice versa.
This block is similar to control block, but it is only updates the value. No command to control the hardware will be sent.
Typical usage example:
This block simply binds two states with each other.
You can achieve the same with these blocks:
You can select if the value will be forwarded only if source state was changed or always when the state is just updated.
<block xmlns="http://www.w3.org/1999/xhtml" type="on_ext" id="w/@=5/5!D;8wn4DZ;jzG" x="287.99999999999943" y="37.999999999999716">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="tQBL3[;V1luVO[`h2ONM">
<field name="oid">javascript.0.Motion</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="control" id="w=sN]yxb)5Jv!,YK[C5%">
<mutation delay_input="false"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">FALSE</field>
<value name="VALUE">
<block type="variables_get" id="6`1|t;T%_h^|ES+nd~/?">
<field name="VAR">value</field>
</block>
</value>
</block>
</statement>
</block>
Universal write block that can do the same as "Update state" and "Control state" together.
But in compare with them you can define Object ID and delay with other blocks to make your script more universal.
There are two types of variables that can be created in scripts:
- local variables
- global variables or states.
Global states are visible in all scripts, but local are visible only in this current script.
Global states can be used in vis, mobile and all other logic or visualisation modules, can be logged into db or whatever.
This block creates global state and if the state yet exist, the command will be ignored. You can safely call this block by every start of the script.
Typical usage example:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="dBV.{0z/{Fr@RB+10H5i" x="38" y="13">
<field name="COMMENT">Create state and subscribe on it changes</field>
<next>
<block type="create" id="D%[{T~!b9^V#Z.7bI+3y">
<field name="NAME">myState</field>
<statement name="STATEMENT">
<block type="on_ext" id="H@F~z_,FpvXo8BptmAtL">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="hn{OMH9y7AP_dns;KO6*">
<field name="oid">javascript.0.myState</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="debug" id="DjP1pU?v=))`V;styIRR">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="de?mCXefl4v#XrO])~7y">
<field name="TEXT">test</field>
</shadow>
<block type="text_join" id="^33}.]#ov(vUAEEn8Hdp">
<mutation items="2"></mutation>
<value name="ADD0">
<block type="text" id="_-p%CZq4%)v1EYvh)lf@">
<field name="TEXT">Value of my state is </field>
</block>
</value>
<value name="ADD1">
<block type="variables_get" id="6r!TtpfrfQ@5Nf[4#[6l">
<field name="VAR">value</field>
</block>
</value>
</block>
</value>
</block>
</statement>
</block>
</statement>
</block>
</next>
</block>
</xml>You can start to use the new created state first in the block itself.
Following code will report an error by the first execution, because subscribe for "myState" cannot find object:
Although no warning will be printed by the second execution, because the state yet exists.
You can use this block to get the value of state. Additionally, to value you can get following attributes:
- Value
- Acknowledge - command = false or update = true
- Timestamp in ms from 1970.1.1 (It has type "Date object")
- Last change of value in ms from 1970.1.1 (It has type "Date object")
- Quality
- Source - instance name, that wrote last value, like "system.adapter.javascript.0"
Example to print time of the last value change:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="GVW732OFexZ9HP[q]B3," x="38" y="13">
<field name="COMMENT">Print time of last change for myState</field>
<next>
<block type="debug" id="t,GmgLjo]1d0{xT+@Yns">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="w{UF-|ashrP4e*jl~{9_">
<field name="TEXT">test</field>
</shadow>
<block type="text_join" id="i~L{r:B9oU}.ANc.AV8F">
<mutation items="2"></mutation>
<value name="ADD0">
<block type="text" id="r5=i|qvrII+NCAQ~t{p5">
<field name="TEXT">Last change of myState was at</field>
</block>
</value>
<value name="ADD1">
<block type="convert_from_date" id="?cGS1/CwThX!tTDMVSoj">
<mutation format="false" language="false"></mutation>
<field name="OPTION">hh:mm:ss</field>
<value name="VALUE">
<block type="get_value" id="k+#N2u^rx)u%Z9lA`Yps">
<field name="ATTR">lc</field>
<field name="OID">javascript.0.myState</field>
</block>
</value>
</block>
</value>
</block>
</value>
</block>
</next>
</block>
</xml>
It is just a help block to comfortable select the object ID for trigger block.
By clicking on Object ID value the select ID dialog will be opened.
Typical usage:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="GVW732OFexZ9HP[q]B3," x="38" y="13">
<field name="COMMENT">Typical usage of Object ID selector</field>
<next>
<block type="on_ext" id="D+1_tP(lF!R]wy?R#|~A">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="rpg#*-DXMVqzexE8-^Xc">
<field name="oid">default</field>
</shadow>
<block type="field_oid" id="YYTRKxeC@l3WE~OJx4ei">
<field name="oid">javascript.0.myState</field>
</block>
</value>
<statement name="STATEMENT">
<block type="debug" id="{;_x6LATJ,b^leE,xgz9">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="-)V}_9Cxt2kj:]36y,7#">
<field name="TEXT">Changed</field>
</shadow>
</value>
</block>
</statement>
</block>
</next>
</block>
</xml>
Executes defined command on system. Like someone has written this command in SSH console.
The command will be executed with permissions of user under which the iobroker was started.
If no outputs are required, they can be ignored:
If parsing of outputs must be done:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="GVW732OFexZ9HP[q]B3," x="313" y="38">
<field name="COMMENT">Execute some system command</field>
<next>
<block type="exec" id="hGkHs.IkmiTa{jR^@-}S">
<mutation with_statement="true"></mutation>
<field name="WITH_STATEMENT">TRUE</field>
<field name="LOG"></field>
<value name="COMMAND">
<shadow type="text" id=":KG#hyuPRhQJWFSk)6Yo">
<field name="TEXT">ls /opt/</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="debug" id="ELv(y5V4[hZ,F8,]D51x">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="J[o*Fylexfu41}smph).">
<field name="TEXT">result</field>
</shadow>
<block type="variables_get" id="gWo7Y^,QI=PqL(Q;7D=^">
<field name="VAR">result</field>
</block>
</value>
</block>
</statement>
</block>
</next>
</block>
</xml>By analysing of outputs 3 special variables will be created:
- result, consists normal output to the console (e.g. for "ls /opt" it consists "iobroker nodejs")
- error object if command cannot be executed by javascript module
- stderr, error output of executed program
Additionally if the log level is not "none", the same command will be sent to log.
Calls URL and give back the result.
Example:
By analysing of outputs 3 special variables will be created:
- result, consists body of the requested page
- error, error description
- response (only for experts), special object and has type of http.IncomingMessage
If no outputs are required, they can be ignored. Just unset "with results" option.
This block is used to send message to telegram client via telegram adapter.
Of course the telegram adapter must be installed and configured.
To send message to some specific instance, you should select the installed adapter instance (Normally telegram.0), elsewise message will be sent to all existing instances.
Property message is mandatory and exactly this text will be sent to client.
Username ID is optional and this is ID from telegram (Unique identifier for user or bot).
Additionally, if the log level is not "none", the same message will be sent to log.
This block is used to send text to sayit instance to pronounce this text.
Of course the sayit adapter must be installed and configured.
To send message to some specific instance, you should select the installed adapter instance (Normally sayit.0), elsewise message will be sent to all existing instances.
Property message is mandatory and exactly this text will be pronounced.
You must check the language property. This will be used for text2speech engine.
Volume is optional (normally from 0 to 100).
Additionally, if the log level is not "none", the same message will be sent to log.
This block is used to send text to pushover client. You can read about pushover driver here.
Of course the pushover adapter must be installed and configured.
To send message to some specific instance, you should select the installed adapter instance (Normally pushover.0), elsewise message will be sent to all existing instances.
Property message is mandatory and exactly this text will be sent to client.
All other properties are optional, and you can read bout them here:
- device ID - your user's device name to send the message directly to that device, rather than all the user's devices (multiple devices may be separated by a comma)
- title - your message's title, otherwise your app's name is used
- URL - a supplementary URL to show with your message
- URL title - a title for your supplementary URL, otherwise just the URL is shown
- priority - send as -2 to generate no notification/alert, -1 to always send as a quiet notification, 1 to display as high-priority and bypass the user's quiet hours, or 2 to also require confirmation from the user
- time in ms - a Unix timestamp of your message's date and time to display to the user, rather than the time your message is received by our API
- sound - the name of one of the sounds supported by device clients to override the user's default sound choice
Additionally, if the log level is not "none", the same message will be sent to log.
This block is used to send text as email.
Of course the email adapter must be installed, configured and tested.
To send message to some specific instance, you should select the installed adapter instance (Normally email.0), elsewise message will be sent to all existing instances.
Property text is mandatory and exactly this text will be sent to client.
Of course the destination (to) must be filled with valid email address.
You can attach up to files (normally images) to email. To use images in the text, you must change format to HTML (check "Send as HTML" option) and text could look like:
<p>Embedded image 1: <img src='cid:file1'/></p>
<p>Embedded image 2: <img src='cid:file2'/></p>
You can refer to files as <img src='cid:file1'/>. "file1" and "file2" are reserved IDs and cannot be changed.
"file name" must consist full path to image on disk.
<block xmlns="http://www.w3.org/1999/xhtml" type="email" id="VeysPTJXFh^.CW1t(s@Q" x="563" y="63">
<field name="INSTANCE"></field>
<field name="IS_HTML">FALSE</field>
<field name="LOG"></field>
<value name="TO">
<shadow type="text" id=".6+6Rp^N7JHiNkP/.^09">
<field name="TEXT"></field>
</shadow>
<block type="text" id="NC6==~4g|OB^`xZ:|Rlx">
<field name="TEXT">[email protected]</field>
</block>
</value>
<value name="TEXT">
<shadow type="text" id="jaGOyI%O4wl(.s.wo(Y`">
<field name="TEXT"></field>
</shadow>
<block type="text" id=")--+u-+rdoAyWpi9I87+">
<field name="TEXT"><p>Embedded image 1: <img src='cid:file1'/></p></field>
</block>
</value>
<value name="SUBJECT">
<shadow type="text" id="|49=rPOCP]hwFD[HX@_I">
<field name="TEXT">From Sweet Home</field>
</shadow>
</value>
<value name="FILE_1">
<block type="text" id="tlb_Kuh5?JvPTQr)A{}4">
<field name="TEXT">/opt/video/imageCam.png</field>
</block>
</value>
</block>Additionally, if the log level is not "none", the same message will be sent to log.
This is just a help block to send internal system message (sendTo) to any adapter.
Of course, you can use custom function block to do anything crazy, and to send messages too.
You can define your own parameters for sendTo command:
Read more here about "sendTo".
Example how to send SQL query to sql adapter:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="GVW732OFexZ9HP[q]B3," x="163" y="13">
<field name="COMMENT">Send query to SQL adapter</field>
<next>
<block type="sendto_custom" id="84lYloO4o+RvLszPVHZ5">
<mutation items="" with_statement="true"></mutation>
<field name="INSTANCE">sql.0</field>
<field name="COMMAND">query</field>
<field name="WITH_STATEMENT">TRUE</field>
<field name="LOG">log</field>
<value name="ARG0">
<shadow type="text" id=")faamoSD,nGPXawY4|(Z">
<field name="TEXT">SELECT * FROM datapoints</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="debug" id="Q#UJl]^_g/VHzM*G/a:f">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="#!NJS43!0z@}z:6~_,9(">
<field name="TEXT">test</field>
</shadow>
<block type="procedures_callcustomreturn" id="0E2fmQQduf4)-({z(om|">
<mutation name="JSON.stringify">
<arg name="obj"></arg>
</mutation>
<value name="ARG0">
<block type="variables_get" id=",^2E2eT#598hI^TvABD9">
<field name="VAR">result</field>
</block>
</value>
</block>
</value>
</block>
</statement>
</block>
</next>
</block>
<block type="procedures_defcustomreturn" id="lm*.n3kQXll8o9X^*m,k" x="163" y="263">
<mutation statements="false">
<arg name="obj"></arg>
</mutation>
<field name="NAME">JSON.stringify</field>
<field name="SCRIPT">cmV0dXJuIEpTT04uc3RyaW5naWZ5KG9iaik7</field>
<comment pinned="false" h="80" w="160">Describe this function...</comment>
</block>
</xml>If you use only one parameter with empty name, so no structure will be created, like here:
var obj, result;
/**
* Describe this function...
*/
function JSON_stringify(obj) {
return JSON.stringify(obj);
}
// Send query to SQL adapter
sendTo("sql.0", "query", 'SELECT * FROM datapoints', function (result) {
console.log((JSON_stringify(result)));
});
console.log("sql.0: " + "");Or how to request history from SQL adapter:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="GVW732OFexZ9HP[q]B3," x="263" y="13">
<field name="COMMENT">Get history from SQL adapter</field>
<next>
<block type="variables_set" id="J;8I^fN*4YQ1+jPI3FS#">
<field name="VAR">end</field>
<value name="VALUE">
<block type="time_get" id="kZFFxa-2%7/:=IHU|}eB">
<mutation format="false" language="false"></mutation>
<field name="OPTION">object</field>
</block>
</value>
<next>
<block type="sendto_custom" id="84lYloO4o+RvLszPVHZ5">
<mutation items="id,options" with_statement="true"></mutation>
<field name="INSTANCE">sql.0</field>
<field name="COMMAND">getHistory</field>
<field name="WITH_STATEMENT">TRUE</field>
<field name="LOG"></field>
<value name="ARG0">
<shadow type="text" id=")faamoSD,nGPXawY4|(Z">
<field name="TEXT">system.adapter.admin.0.memRss</field>
</shadow>
</value>
<value name="ARG1">
<shadow type="text" id="/nmT=qDw;S`#*tXN=C6n">
<field name="TEXT">{start: end - 3600000, end: end, aggregate: "minmax"}</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="debug" id="Q#UJl]^_g/VHzM*G/a:f">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="#!NJS43!0z@}z:6~_,9(">
<field name="TEXT">test</field>
</shadow>
<block type="procedures_callcustomreturn" id="0E2fmQQduf4)-({z(om|">
<mutation name="JSON.stringify">
<arg name="obj"></arg>
</mutation>
<value name="ARG0">
<block type="variables_get" id=",^2E2eT#598hI^TvABD9">
<field name="VAR">result</field>
</block>
</value>
</block>
</value>
</block>
</statement>
</block>
</next>
</block>
</next>
</block>
<block type="procedures_defcustomreturn" id="lm*.n3kQXll8o9X^*m,k" x="263" y="313">
<mutation statements="false">
<arg name="obj"></arg>
</mutation>
<field name="NAME">JSON.stringify</field>
<field name="SCRIPT">cmV0dXJuIEpTT04uc3RyaW5naWZ5KG9iaik7</field>
<comment pinned="false" h="80" w="160">JSON.stringify object</comment>
</block>
</xml>Generated javascript code:
var obj, end, result;
/**
* JSON.stringify object
*/
function JSON_stringify(obj) {
return JSON.stringify(obj);
}
// Get history from SQL adapter
end = (new Date().getTime());
sendTo("sql.0", "getHistory", {
"id": 'system.adapter.admin.0.memRss',
"options": {start: end - 3600000, end: end, aggregate: "minmax"}
}, function (result) {
console.log((JSON_stringify(result)));
});If you start value with { it will be interpreted as JSON string. Use double quotes in string.
With this block you can send message to other script and this message could be processed by Event - receive message block.
If used operator "between" or "not between", the block looks like this:
You can specify a time, which must be compared. Block expects the time as "Date object".
There are following compare modes:
-
less than, check if actual time less than specified time.
-
equal to or less than
-
greater than
-
equal to or greater than
-
equal to
-
between, check if the time between some day times.
- E.g. if time must be between 12:00 and 20:00. It will be checked if actual time grater or equal than 12:00 and less than 20:00. 20:00 will return false.
- or for instance between 21:00 and 8:00. In the last case it will be checked if time greater or equal to 21:00 or less than 8:00.
-
not between, if the time is not in the given period of the daytime. If the time less than start and greater or equal to end. (if start time is greater than end time, it will be checked if the time greater or equal than end and smaller than start)
Following time formats are valid:
- YYYY-MM-DD hh:mm:ss
- YYYY-MM-DD hh:mm
- hh:mm:ss
- hh:mm
This block is used to compare the day time with actual time. It has the same logic as Time comparision, but limits cannot be a blocks, and it compares only actual time. (for compatibility with old versions)
Returns the actual time in some specified format.
Following formats are supported:
- milliseconds - returns only milliseconds of current second from 0 to 999 (not epoch milliseconds). To get epoch milliseconds use "Date object";
- seconds - returns only seconds of current minute from 0 to 59,
- seconds in day - returns number of seconds from start of the day (0 to 24 * 3600 - 1),
- minutes - returns minutes of current hour from 0 to 59,
- minutes in day - returns number of minutes from the day start (0 to 24 * 60 - 1),
- hours - returns hours of current day from 0 to 23,
- day of month - get day of month from 1 to 31,
- month as number - get month as number from 1 to 12,
- month as text - get month as text. Language must be specified.
- month as short text - get month as text: Jan, Feb, Mar, Apr, May, June, July, Aug, Sept, Oct, Nov, Dec. Language must be specified.
- short year - Year from 0 to 99, e.g for 2016 the result will be 16.
- full year - Full year: 2016
- week day text - Get day of week as text.
- short week day - Get day of week as short text: Su, Mo, Tu, We, Th, Fr, Sa.
- week day as number - Day of week as number from 1 (monday) to 7 (sunday).
- custom format - You can specify your own format.
- Date object - Returns date and time as number of milliseconds from start of epoch (1970.1.1 00:00:00.000Z GMT). This is always GMT.
- yyyy.mm.dd - 2016.09.14
- yyyy/mm/dd - 2016/09/14
- yy.mm.dd - 16.09.14
- yy/mm/dd - 16/09/14
- dd.mm.yyyy - 14.09.2016
- dd/mm/yyyy - 14/09/2016
- dd.mm.yy - 14.09.16
- dd/mm/yy - 14/09/16
- mm/dd/yyyy - 09/14/2016
- mm/dd/yy - 09/14/16
- dd.mm. - 14.09.
- dd/mm - 14/09
- mm.dd - 09.14
- mm/dd - 09/14
- hh:mm - 12:00
- hh:mm:ss - 12:00:00
- hh:mm:ss.sss - 12:00:00.000
Returns the time in current day of some specific astrological event.
The attribute "offset" is the offset in minutes. It can be negative too, to define time before astro event.
Following values can be used as attribute in astro-function:
- sunrise: sunrise (top edge of the sun appears on the horizon)
- sunriseEnd: sunrise ends (bottom edge of the sun touches the horizon)
- goldenHourEnd: morning golden hour (soft light, best time for photography) ends
- solarNoon: solar noon (sun is in the highest position)
- goldenHour: evening golden hour starts
- sunsetStart: sunset starts (bottom edge of the sun touches the horizon)
- sunset: sunset (sun disappears below the horizon, evening civil twilight starts)
- dusk: dusk (evening nautical twilight starts)
- nauticalDusk: nautical dusk (evening astronomical twilight starts)
- night: night starts (dark enough for astronomical observations)
- nightEnd: night ends (morning astronomical twilight starts)
- nauticalDawn: nautical dawn (morning nautical twilight starts)
- dawn: dawn (morning nautical twilight ends, morning civil twilight starts)
- nadir: nadir (the darkest moment of the night, sun is in the lowest position)
The return value has type "Date Object", what is just the number of milliseconds from 1970.01.01.
Note: to use "astro"-function the "latitude" and "longitude" must be defined in javascript adapter settings.
Sometimes it is required to convert value into other type. Following blocks allow converting value into specific types.
Convert value to number (float).
Convert value to boolean (true or false).
Convert value to string.
Get type of value. Type can be: boolean, number, string, object.
Convert value to "Date object". Read here, what the "Date object" is.
Convert "Date object" into string. It has the same format options as Get actual time im specific format.
Convert JSON string into javascript object. If an error occurs, the empty object will be returned. (only for experts)
Convert Javascript object to JSON string. If prettify option is selected the result string looks like:
{
"a": 1,
"b": 2
}
if not:
{"a": 1, "b": 2}
Convert Javascript object by JSONata expression. You can read more about it here: https://jsonata.org/
Example payload:
{"example": [{"value": 4},{"value": 7},{"value": 13}]}
Result:
[{"value": 4},{"value": 7},{"value": 13}]
24
4
13
This block executes some action if state of given objects changed or updated. This is the main block to build interactions between different states and accordingly systems.
With this block you can bind different states together or send message or email on value change.
Typical usage of block:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="]L0d;6j+=OH*[4n{C7v^" x="112" y="13">
<field name="COMMENT">Switch light on if motion detected</field>
<next>
<block type="on_ext" id="QYVeQlu|#2hwniNg)=z8">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="Xe6D#r|nf9SEK`.oAuS0">
<field name="oid">javascript.0.Motion</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="control" id="J(HiEvnNKw2B%V1~WXsX">
<mutation delay_input="false"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">FALSE</field>
<value name="VALUE">
<block type="logic_boolean" id="o;j8lE#h.XE,0:0_LcW{">
<field name="BOOL">TRUE</field>
</block>
</value>
</block>
</statement>
</block>
</next>
</block>
</xml>You can define as many ObjectIDs as you want via extension dialog:
If only one object ID is used so special variables are available in the statement block:
- value - actual value of state
- oldValue - old value of state
<block xmlns="http://www.w3.org/1999/xhtml" type="on_ext" id="QYVeQlu|#2hwniNg)=z8" x="38" y="39">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="Xe6D#r|nf9SEK`.oAuS0">
<field name="oid">javascript.0.Motion</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="debug" id="jT6fif_FI9ua|,rL[Ra1">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="}=qIm)a0)};f+J/JRgy^">
<field name="TEXT">test</field>
</shadow>
<block type="text_join" id="wjgpY(Whewaqy0d8NVx%">
<mutation items="4"></mutation>
<value name="ADD0">
<block type="text" id="M?[Xy1(Fu36A;b#=4~[t">
<field name="TEXT">Actual value is</field>
</block>
</value>
<value name="ADD1">
<block type="variables_get" id="W)*G#(JDzuVpV^1P|[2m">
<field name="VAR">value</field>
</block>
</value>
<value name="ADD2">
<block type="text" id="7TW;voPvdc#c4e/SWCjZ">
<field name="TEXT">Old value was</field>
</block>
</value>
<value name="ADD3">
<block type="variables_get" id="s`6)4s:}%L#f]pu4E[vK">
<field name="VAR">oldValue</field>
</block>
</value>
</block>
</value>
</block>
</statement>
</block>elsewise if more than one object ID is used for trigger, you can access value and old value via Trigger info.
This is the same block as "Trigger on states change", but with no possibility to use multiple object IDs for triggering (for versions compatibility).
Get information about value, timestamp or ID of the state, that triggered the trigger.
This block can be used only inside of "Trigger on states change" or "Trigger on state change" blocks.
Following information can be accessed:
- object ID - ID of state, that fired the trigger
- name - name of state from common.name
- description - description of state from common.desc
- channel ID - ID of channel to which belongs the state. If not channel there, it will be null
- channel name - name of channel to which belongs the state. If not channel there, it will be null
- device ID - ID of device to which belongs the state. If not channel there, it will be null
- device name - name of device to which belongs the state. If not channel there, it will be null
- state value - actual value of fired state
- state timestamp - actual timestamp as Date object
- state quality - actual quality code of value
- origin of value - name of instance that cause the change
- is command or update - is it command (ack=false) or update (ack=true)
- last change of state - timestamp of last change of this value
- previous value - previous value of this state, before the trigger fired
- previous timestamp - previous timestamp of this state, before the trigger fired
- previous quality - previous quality of this state, before the trigger fired
- previous origin - previous origin of this state, before the trigger fired
- previous command or update - previous type of this value, before the trigger fired
- previous last change - previous "last changed value" of this state, before the trigger fired
Typical usage:
<block xmlns="http://www.w3.org/1999/xhtml" type="on_ext" id="QYVeQlu|#2hwniNg)=z8" x="113" y="238">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="Xe6D#r|nf9SEK`.oAuS0">
<field name="oid">javascript.0.Motion</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="debug" id="jT6fif_FI9ua|,rL[Ra1">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="}=qIm)a0)};f+J/JRgy^">
<field name="TEXT">test</field>
</shadow>
<block type="text_join" id="wjgpY(Whewaqy0d8NVx%">
<mutation items="4"></mutation>
<value name="ADD0">
<block type="text" id="M?[Xy1(Fu36A;b#=4~[t">
<field name="TEXT">Actual value is</field>
</block>
</value>
<value name="ADD1">
<block type="on_source" id="_q8v0HD`c[7e76O{@4Tq">
<field name="ATTR">state.val</field>
</block>
</value>
<value name="ADD2">
<block type="text" id="7TW;voPvdc#c4e/SWCjZ">
<field name="TEXT">Old value was</field>
</block>
</value>
<value name="ADD3">
<block type="on_source" id="D`gpXSShKRQuy:jyMK}6">
<field name="ATTR">oldState.val</field>
</block>
</value>
</block>
</value>
</block>
</statement>
</block>
This is second main block for automation after "Trigger on states change". This block lets execute some actions periodically.
The definition of schedule rule will be done in very well documented CRON format. With extension, that seconds can be defined too. If seconds should be used they must be defined as very first parameter of CRON rule and rule will have 6 parts.
Generally CRON rule consist of 5 or 6 parts:
- seconds rules (optional)
- minutes rules
- hours rules
- day of month rules
- month's rules
- and day of week rules.
For every part following formats are allowed:
- * - fire every (second, minute, hour, ...)
- X (e.g. 5) - fire only in this second, minute, hour...
- from-to (e.g. 1-9) - fire only in this interval
- */X (e.g. */5) - fire every X seconds, minutes... In case of "*/5" for hours the trigger will fire on 0, 5, 10, 15 and on 20 hours.
- numbers and intervals can be combined by comma (e.g 1,3,4-6). Do not make spaces between numbers, because space is delimiter for rule's parts.
*/10 * * * 6,7 - fire every 10 minutes on saturday and sunday.
*/30 * * * * * - fire every 30 seconds.
┌───────────── min (0 - 59)
│ ┌────────────── hour (0 - 23)
│ │ ┌─────────────── day of month (1 - 31)
│ │ │ ┌──────────────── month (1 - 12)
│ │ │ │ ┌───────────────── day of week (0 - 6) (0 to 6 are Sunday to Saturday; 7 is also Sunday)
│ │ │ │ │
│ │ │ │ │
│ │ │ │ │
* * * * * schedule
or if seconds used:
┌───────────── seconds (0 - 59)
│ ┌───────────── min (0 - 59)
│ │ ┌────────────── hour (0 - 23)
│ │ │ ┌─────────────── day of month (1 - 31)
│ │ │ │ ┌──────────────── month (1 - 12)
│ │ │ │ │ ┌───────────────── day of week (0 - 6) (0 to 6 are Sunday to Saturday; 7 is also Sunday)
│ │ │ │ │ │
│ │ │ │ │ │
│ │ │ │ │ │
* * * * * * schedule
But there is a good help for you to build such a rules. By clicking on rule the CRON dialog will be opened, and you can specify by mouse your rule.
Execute some action on astrological event. Following events are possible:
- sunrise: sunrise (top edge of the sun appears on the horizon)
- sunriseEnd: sunrise ends (bottom edge of the sun touches the horizon)
- goldenHourEnd: morning golden hour (soft light, best time for photography) ends
- solarNoon: solar noon (sun is in the highest position)
- goldenHour: evening golden hour starts
- sunsetStart: sunset starts (bottom edge of the sun touches the horizon)
- sunset: sunset (sun disappears below the horizon, evening civil twilight starts)
- dusk: dusk (evening nautical twilight starts)
- nauticalDusk: nautical dusk (evening astronomical twilight starts)
- night: night starts (dark enough for astronomical observations)
- nightEnd: night ends (morning astronomical twilight starts)
- nauticalDawn: nautical dawn (morning nautical twilight starts)
- dawn: dawn (morning nautical twilight ends, morning civil twilight starts)
- nadir: nadir (the darkest moment of the night, sun is in the lowest position)
Note: to use "astro"-function the "latitude" and "longitude" must be defined in javascript adapter settings.
Additionally, you can set the offset in minutes to astrological event, e.g. to fire the trigger 1 hour before down:
As you can see the offset can be negative too to specify time before astrological events.
This block is the same as Schedule, but with possibility to set CRON rule by string and with possibility to stop the schedule.
You can specify unique name of this schedule block and then later to clear it with Clear schedule.
Here is an example of configurable alarm clock:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="QWp.l96v1;-4{x)j5K5y" x="38" y="13">
<field name="COMMENT">Configurable alarm. Set time as: hh:mm</field>
<next>
<block type="create" id="5*XX`C;PgnU(q#Nk~D,o">
<field name="NAME">alarmTime</field>
<statement name="STATEMENT">
<block type="on_ext" id="ot:9oFMh.(c)sxkufTxA">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="qV#=^mz,%qxL#}VsA)3C">
<field name="oid">javascript.0.alarmTime</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="schedule_clear" id="ukGIQYyTpip_9!1H_xnN">
<field name="NAME">alarm</field>
<next>
<block type="schedule_create" id=")^!A|k+`1=[pFp(S-*sw">
<field name="NAME">alarm</field>
<value name="SCHEDULE">
<shadow type="field_cron" id="uSka7fK[T7j0m_4!4+fO">
<field name="CRON">* * * * *</field>
</shadow>
<block type="procedures_callcustomreturn" id=")E!Ljg1z9iQ3)Nb#CX~n">
<mutation name="time to CRON">
<arg name="time"></arg>
</mutation>
<value name="ARG0">
<block type="on_source" id="qs+k30Lnd1V(BSNs{}P!">
<field name="ATTR">state.val</field>
</block>
</value>
</block>
</value>
<statement name="STATEMENT">
<block type="debug" id="7arB5vcx^ci2Un#}TLKh">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="N;`AY!p#T_do@vP_OQr9">
<field name="TEXT">Wake up!</field>
</shadow>
</value>
</block>
</statement>
</block>
</next>
</block>
</statement>
</block>
</statement>
</block>
</next>
</block>
<block type="procedures_defcustomreturn" id="_*_L4XpCr!7eLsYWS(R(" x="38" y="337">
<mutation statements="false">
<arg name="time"></arg>
</mutation>
<field name="NAME">time to CRON</field>
<field name="SCRIPT">dmFyIHBhcnRzID0gdGltZS5zcGxpdCgnOicpOwovLyBpZiBpdCBpcyBDUk9OCmlmIChwYXJ0cy5sZW5ndGggPT09IDEpIHJldHVybiB0aW1lOwpyZXR1cm4gcGFydHNbMV0gKyAnICcgKyBwYXJ0c1swXSArICcgKiAqIConOw==</field>
<comment pinned="false" h="80" w="160">Describe this function...</comment>
</block>
</xml>
With this function block you can clear named schedule. If you define named one more time without clearing it, the old one will still active.
See an example in Named schedule
Create CRON rule from dialog. This block can be connected with Named schedule.
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id="]aB;GhQJvYrr~:H4Ft9l" x="63" y="38">
<field name="COMMENT">Every 0th minute every hour</field>
<next>
<block type="schedule_create" id="?}upFtiA@CE_Gd)SmDo|">
<field name="NAME">schedule</field>
<value name="SCHEDULE">
<shadow type="field_cron" id="1Ag|noK^~u]GFEW/(lb)">
<field name="CRON">* * * * *</field>
</shadow>
<block type="field_cron" id="phjg#B~@BJTO9i[HmZ4O">
<field name="CRON">0 * * * *</field>
</block>
</value>
<statement name="STATEMENT">
<block type="debug" id="Lv[a}BtvBDO-2Lt,s+z4">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="evxnn0R1(AC^Y_U`oT_a">
<field name="TEXT">It is exactly</field>
</shadow>
<block type="text_join" id="6!2uB_db8.g}63I{^e}#">
<mutation items="3"></mutation>
<value name="ADD0">
<block type="text" id="HH((bCdxr?A5)8Svuo6(">
<field name="TEXT">It is exactly </field>
</block>
</value>
<value name="ADD1">
<block type="time_get" id="7{BBfF0jmKD[qX,y6voK">
<mutation format="false" language="false"></mutation>
<field name="OPTION">h</field>
</block>
</value>
<value name="ADD2">
<block type="text" id="edML0zJ2V9kN}5/DLdS5">
<field name="TEXT"> o'clock</field>
</block>
</value>
</block>
</value>
</block>
</statement>
</block>
</next>
</block>
</xml>
Combine CRON rule from different parts.
You can display rule as block or as line:
With additional parameter "with seconds" you can specify seconds for CRON rule too
This block can be used (like CRON dialog) only with Named schedule block.
You can subscribe on file updates and execute some action. E.g. here the content of `vis´ will be printed out every time the project updated:
<xml xmlns="https://developers.google.com/blockly/xml">
<variables>
<variable id="@-v}))=J7?dr9n$tR,=j">data</variable>
</variables>
<block type="onFile" id="4`C)*,R0DVN@nRaM@/[N" x="188" y="37">
<field name="WITH_FILE">TRUE</field>
<value name="OID">
<shadow type="field_oid_meta" id="K^Qc~2T8{V+K017=]c^d">
<field name="oid">vis.0</field>
</shadow>
</value>
<value name="FILE">
<shadow type="text" id="A7UXrl-.!o]Oi9g[eBxr">
<field name="TEXT">main/*</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="debug" id="fl3BZ)}mE7qw[`W*ZUx}">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="se+gg@!ryr*!AO~Bx3uX">
<field name="TEXT">test</field>
</shadow>
<block type="variables_get" id="E{)LJvx~EH~shD%3!);w">
<field name="VAR" id="@-v}))=J7?dr9n$tR,=j">data</field>
</block>
</value>
</block>
</statement>
</block>
</xml>
Important: this functionality is only available with [email protected] or newer.
With this block you can unsubscribe from events by file update.
Important: this functionality is only available with [email protected] or newer.
With this block you can subscribe on inter-scripts events and execute some action.
With this simple block you can pause the execution of blocks.
Take care if pause is used in some bundle, it will pause all blocks in this script which are positioned lower block with pause:
Generated code:
console.log('"Independent" block'); // Will not be delayed
console.log('Before pause');
await wait(5000);
console.log('After pause');
Log output:
15:48:21.807 info javascript.0 (7304) script.js.Skript_1: "Independent" block
15:48:21.807 info javascript.0 (7304) script.js.Skript_1: Before pause
15:48:21.807 info javascript.0 (7304) script.js.Skript_1: registered 0 subscriptions and 0 schedules
15:48:26.810 info javascript.0 (7304) script.js.Skript_1: After pause
Generated code:
console.log('Before pause');
await wait(5000);
console.log('After pause');
console.log('"Independent" block'); // Will be delayed by for 5 seconds
Output:
15:52:03.289 info javascript.0 (7304) script.js.Skript_1: Before pause
15:52:03.290 info javascript.0 (7304) script.js.Skript_1: registered 0 subscriptions and 0 schedules
15:52:08.296 info javascript.0 (7304) script.js.Skript_1: After pause
15:52:08.297 info javascript.0 (7304) script.js.Skript_1: "Independent" block
With this block you can execute other blocks delayed by some time specified in milliseconds. if you know Javascript it is the same function as setTimeout.
There is no "pause" in blockly, but you can use this block to simulate pause. If you place all blocks, that must be executed after the pause you will achieve the same effect as with pause.
Every delayed execution can have unique name. It can be canceled by other block. Clear delayed execution
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="debug" id=":6GZ!E*FHy@vPKKl{`hV" x="487" y="163">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="LV!-dx[I(8bAu(_kcG.U">
<field name="TEXT">Make a pause 5 seconds</field>
</shadow>
</value>
<next>
<block type="timeouts_settimeout" id="~?BW3eBK_t:TzNk}x9l3">
<field name="NAME">timeout</field>
<field name="DELAY">5000</field>
<statement name="STATEMENT">
<block type="debug" id="glbs:mQxsDfEieLaru!0">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="_7T9e{FEJTWcpLl*BltU">
<field name="TEXT">After pause</field>
</shadow>
</value>
</block>
</statement>
</block>
</next>
</block>
</xml>
This block is used to cancel running delay by name. Typical usage is simulation of motion detection scenario. By first motion the light should go on and after the last motion after 30 seconds the light should go off.
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="on_ext" id="+nZ`H6mh/;g(e3u,t;wJ" x="163" y="12">
<mutation items="1"></mutation>
<field name="CONDITION">ne</field>
<field name="ACK_CONDITION"></field>
<value name="OID0">
<shadow type="field_oid" id="{mRcPH:!k^_5q-hwg1q%">
<field name="oid">node-red.0.javascript.0.Motion</field>
</shadow>
</value>
<statement name="STATEMENT">
<block type="controls_if" id="]lX4.m?HnwXigM.6wY/D">
<value name="IF0">
<block type="logic_compare" id="s0DHFun9e*,c3AawmP_~">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="g}IH`Bx0T(mkht8~{Ul0">
<field name="VAR">value</field>
</block>
</value>
<value name="B">
<block type="logic_boolean" id="Meek9{gS-NOR?|(fgbVg">
<field name="BOOL">TRUE</field>
</block>
</value>
</block>
</value>
<statement name="DO0">
<block type="debug" id=":6GZ!E*FHy@vPKKl{`hV">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="LV!-dx[I(8bAu(_kcG.U">
<field name="TEXT">Motion detected</field>
</shadow>
</value>
<next>
<block type="comment" id="6_T-s#wApgZhu0+4uEk}">
<field name="COMMENT">Switch light ON</field>
<next>
<block type="control" id="fxgT@s0r?[`LJIsqR~M_">
<mutation delay_input="false"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">FALSE</field>
<value name="VALUE">
<block type="logic_boolean" id="0mgo#`N%Zm{MTELxw%~0">
<field name="BOOL">TRUE</field>
</block>
</value>
<next>
<block type="comment" id="rZ^o06`}^uFftKj2oYvE">
<field name="COMMENT">Stop timer, even if it not running</field>
<next>
<block type="timeouts_cleartimeout" id="#H#~HxipC8_-/{%,2R1P">
<field name="NAME">lightOff</field>
<next>
<block type="timeouts_settimeout" id="~?BW3eBK_t:TzNk}x9l3">
<field name="NAME">lightOff</field>
<field name="DELAY">5000</field>
<statement name="STATEMENT">
<block type="debug" id="glbs:mQxsDfEieLaru!0">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="_7T9e{FEJTWcpLl*BltU">
<field name="TEXT">Light OFF</field>
</shadow>
</value>
<next>
<block type="control" id="McdOD=k4)MlO42RVgB~r">
<mutation delay_input="false"></mutation>
<field name="OID">javascript.0.Light</field>
<field name="WITH_DELAY">FALSE</field>
<value name="VALUE">
<block type="logic_boolean" id="XLHrXB)/|dqGlh,nXl^[">
<field name="BOOL">FALSE</field>
</block>
</value>
</block>
</next>
</block>
</statement>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</statement>
</block>
</statement>
</block>
</xml>
This block allows you to execute some action periodically. Of course there is a CRON block, but CRON block has the smallest interval one second. This block can execute actions in milliseconds periods.
If you set the interval too small (under 100ms) it can be, that intervals will be bigger.
Similar to timeout block you can set unique interval name too.
An additional feature is to set the interval by using a variable, just replace the "ms" with a predefined variable:
With the help of this block you can cancel periodically execution of interval block by its name.
To use this block you should understand basic programming rules: how to use variables.
With this block you can write into global (visible everywhere in this script) variable and use it to store some values. If variable does not exist, it will be declared automatically.
This block can create new variable or use existing one.
This code:
<block xmlns="http://www.w3.org/1999/xhtml" type="variables_set" id="ch{H@omhfzI(QA{syxAG" x="212.99999999999977" y="37.99999999999994">
<field name="VAR">item</field>
<value name="VALUE">
<block type="math_number" id="SbmD7,uR:hMW!(P%IZRc">
<field name="NUM">0</field>
</block>
</value>
</block>does only this:
var item;
item = 0;
This block gets the value of variable. You can create a new one or use existing one.
There is one exception with trigger blocks Trigger on states change and Trigger on state change. Inside these blocks variable "value" yet exist, but anyway to read their values you must rename variable into value and then use it.
With this block you can combine some repeat sequences into function and then use this function everywhere in current blockly.
Here is an example of function that just prints into log current time.
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id=";LE@QUg[hpGG!Ed6(?Hf" x="463" y="88">
<field name="COMMENT">Print current time</field>
</block>
<block type="procedures_defnoreturn" id="zz#oL]VPR)s}NMK9htHa" x="463" y="113">
<field name="NAME">printTime</field>
<comment pinned="false" h="80" w="160">Describe this function...</comment>
<statement name="STACK">
<block type="debug" id="ak(`[aJB-AH@Hvc;B,[D">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="aGuA=^(ge/)=lXes9f]?">
<field name="TEXT">test</field>
</shadow>
<block type="time_get" id="M}z9(p(melE7BbTGqczO">
<mutation format="false" language="false"></mutation>
<field name="OPTION">hh:mm:ss.sss</field>
</block>
</value>
</block>
</statement>
</block>
</xml>After the function created, you can use this function like this:
<block xmlns="http://www.w3.org/1999/xhtml" type="timeouts_setinterval" id="hp;?}l3uStXhm+a2s!9t" x="62.99999999999943" y="112.99999999999994">
<field name="NAME">interval</field>
<field name="INTERVAL">1000</field>
<statement name="STATEMENT">
<block type="procedures_callnoreturn" id="(/)MPv+z_|516CuG%[XD">
<mutation name="printTime"></mutation>
</block>
</statement>
</block>You can find this new function in the blocks menu:
Additionally, you can specify arguments for the function too via configuration dialog. You can edit the names of arguments in hte same dialog.
Here is an example of function that prints the sum of first argument and the second one:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="comment" id=";LE@QUg[hpGG!Ed6(?Hf" x="463" y="88">
<field name="COMMENT">Print sum of a and b</field>
</block>
<block type="procedures_defnoreturn" id="zz#oL]VPR)s}NMK9htHa" x="463" y="113">
<mutation>
<arg name="a"></arg>
<arg name="b"></arg>
</mutation>
<field name="NAME">printSum</field>
<comment pinned="false" h="80" w="160">Describe this function...</comment>
<statement name="STACK">
<block type="debug" id="ak(`[aJB-AH@Hvc;B,[D">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="aGuA=^(ge/)=lXes9f]?">
<field name="TEXT">test</field>
</shadow>
<block type="math_arithmetic" id="qUGc!b+U]:yE!I+3I+Lp">
<field name="OP">ADD</field>
<value name="A">
<shadow type="math_number" id="OqjQ{@*pgO,~Xd(ef)9~">
<field name="NUM">1</field>
</shadow>
<block type="variables_get" id="]dC)!=A3{(5?9hJ:1gET">
<field name="VAR">a</field>
</block>
</value>
<value name="B">
<shadow type="math_number" id="aDp|:rn#.wve0]WKi(D[">
<field name="NUM">1</field>
</shadow>
<block type="variables_get" id="5];ao,?ce{;GJ;OOW~S4">
<field name="VAR">b</field>
</block>
</value>
</block>
</value>
</block>
</statement>
</block>
</xml>You can find the arguments in the variables' menu:
And use this function like this:
<block xmlns="http://www.w3.org/1999/xhtml" type="procedures_callnoreturn" id="(-G|y+Y7AC]w2CTQGjYC" x="138" y="188">
<mutation name="printSum">
<arg name="a"></arg>
<arg name="b"></arg>
</mutation>
<value name="ARG0">
<block type="math_number" id="!.UT=[{Xkz-*wlPh)sYn">
<field name="NUM">5</field>
</block>
</value>
<value name="ARG1">
<block type="math_number" id="EMhKM9Cn#;DjMZ#Ko%EN">
<field name="NUM">6</field>
</block>
</value>
</block>
This block is the same, but it can return result of the function, that can be used later in blocks.
<block xmlns="http://www.w3.org/1999/xhtml" type="procedures_defreturn" id="4)|}1YzV}e6YUvVV^sY{" x="413" y="138">
<mutation statements="false">
<arg name="a"></arg>
<arg name="b"></arg>
</mutation>
<field name="NAME">do something</field>
<comment pinned="false" h="80" w="160">Return sum of a and b</comment>
<value name="RETURN">
<block type="math_arithmetic" id="qUGc!b+U]:yE!I+3I+Lp">
<field name="OP">ADD</field>
<value name="A">
<shadow type="math_number" id="OqjQ{@*pgO,~Xd(ef)9~">
<field name="NUM">1</field>
</shadow>
<block type="variables_get" id="]dC)!=A3{(5?9hJ:1gET">
<field name="VAR">a</field>
</block>
</value>
<value name="B">
<shadow type="math_number" id="aDp|:rn#.wve0]WKi(D[">
<field name="NUM">1</field>
</shadow>
<block type="variables_get" id="5];ao,?ce{;GJ;OOW~S4">
<field name="VAR">b</field>
</block>
</value>
</block>
</value>
</block>Usage is similar with other function blocks:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="debug" id="zgr7b0g)}uMe1ySGYL7X" x="163" y="137">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="q-]m1ptAzK4Rq20wWRBq">
<field name="TEXT">test</field>
</shadow>
<block type="procedures_callreturn" id="0RX?V1j|FZHK@*Lw3W-g">
<mutation name="sum">
<arg name="a"></arg>
<arg name="b"></arg>
</mutation>
<value name="ARG0">
<block type="math_number" id="Xd52^_Qp83=ah2RTWzSU">
<field name="NUM">5</field>
</block>
</value>
<value name="ARG1">
<block type="math_number" id="-M9A9EhrgJSRc*4(X^[;">
<field name="NUM">6</field>
</block>
</value>
</block>
</value>
</block>
<block type="procedures_defreturn" id="4)|}1YzV}e6YUvVV^sY{" x="413" y="138">
<mutation statements="false">
<arg name="a"></arg>
<arg name="b"></arg>
</mutation>
<field name="NAME">sum</field>
<comment pinned="false" h="80" w="160">Return sum of a and b</comment>
<value name="RETURN">
<block type="math_arithmetic" id="qUGc!b+U]:yE!I+3I+Lp">
<field name="OP">ADD</field>
<value name="A">
<shadow type="math_number" id="OqjQ{@*pgO,~Xd(ef)9~">
<field name="NUM">1</field>
</shadow>
<block type="variables_get" id="]dC)!=A3{(5?9hJ:1gET">
<field name="VAR">a</field>
</block>
</value>
<value name="B">
<shadow type="math_number" id="aDp|:rn#.wve0]WKi(D[">
<field name="NUM">1</field>
</shadow>
<block type="variables_get" id="5];ao,?ce{;GJ;OOW~S4">
<field name="VAR">b</field>
</block>
</value>
</block>
</value>
</block>
</xml>For all functions you can add comment or description.
In the return block you can use special return element:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="debug" id="zgr7b0g)}uMe1ySGYL7X" x="63" y="12">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="q-]m1ptAzK4Rq20wWRBq">
<field name="TEXT">test</field>
</shadow>
<block type="procedures_callreturn" id="0RX?V1j|FZHK@*Lw3W-g">
<mutation name="numberToDay">
<arg name="day"></arg>
</mutation>
<value name="ARG0">
<block type="math_number" id="Xd52^_Qp83=ah2RTWzSU">
<field name="NUM">5</field>
</block>
</value>
</block>
</value>
</block>
<block type="debug" id="@i@bdG^90dp,cJ#W*[nB" x="12" y="188">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="8:/`}T!:6Wz.d/;)jpHl">
<field name="TEXT">test</field>
</shadow>
<block type="procedures_callreturn" id="hvzS!O_Q=FlccQR@*%tk">
<mutation name="numberToDay">
<arg name="day"></arg>
</mutation>
<value name="ARG0">
<block type="time_get" id=":A,Ba,yrW_QgiX*cs9zh">
<mutation format="false" language="false"></mutation>
<field name="OPTION">wd</field>
</block>
</value>
</block>
</value>
</block>
<block type="procedures_defreturn" id="4)|}1YzV}e6YUvVV^sY{" x="588" y="163">
<mutation>
<arg name="day"></arg>
</mutation>
<field name="NAME">numberToDay</field>
<comment pinned="false" h="80" w="160">Return sum of a and b</comment>
<statement name="STACK">
<block type="procedures_ifreturn" id="/qJjm#cr-naS}joAL0eT">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="cbxuAYxF,ptMi.`E/nB.">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="`mWQWp).?qDuD=)NX2dA">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="s,20+9X6bB/2nL{v?g:/">
<field name="NUM">0</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="iI)V7P`3YP]{-S-7HcO1">
<field name="TEXT">Sunday</field>
</block>
</value>
<next>
<block type="procedures_ifreturn" id="3=FBSCS{jzu[}2L5Spi[">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="V[;S84AH5cf93^5/[AN^">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id=";ShgVu*+:nn9WSzbm[fA">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="jY?Wj8lC1-~SiIHa*I)0">
<field name="NUM">1</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="=aVg_FatldZUUsS(8G`;">
<field name="TEXT">Monday</field>
</block>
</value>
<next>
<block type="procedures_ifreturn" id="(g_VE2e?U^J-nhk,bP|0">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="M;B+SSw[Mc.iu;fUjvcV">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="yT{.UQ)qXY8-@2XzpxQo">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="Q-JC5_JZ=i{[+~:^|BpU">
<field name="NUM">2</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="9`665+j*i_?3BCZWODGt">
<field name="TEXT">Tuesday</field>
</block>
</value>
<next>
<block type="procedures_ifreturn" id="{+9IT6E:N-a+Y.cFNMsw">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="B}D{JSK|}=bk|-|D#/_h">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="s{Zxm|sBbEGA1#~Tv3EE">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="f!3KoyGu4bWpxdaJY`JI">
<field name="NUM">3</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="yS4pn;Fdg9JT[MjvPu,4">
<field name="TEXT">Wednesday</field>
</block>
</value>
<next>
<block type="procedures_ifreturn" id="g*VMz;jyw4,@;Qb*/8TN">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="(^azMqi{:`?S.tJ@y7-m">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="P*CAI!ug.Xl*BM2v/kpb">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="YN@VzF~X=BOcWm+P]c3i">
<field name="NUM">4</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="H`yzv!j_GjSw|@f7Gap8">
<field name="TEXT">Thursday</field>
</block>
</value>
<next>
<block type="procedures_ifreturn" id=")htNPjBWw1J/gp-Y5#Kg">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="nFZ;s`3ij0v|.wQqw`AB">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="Q^3OKKD]aGa0/qxWf%*g">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="#brnWNXj0_dx[JwHjgh0">
<field name="NUM">5</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="Y1-{3UJxFrpq{uJp6DkB">
<field name="TEXT">Friday</field>
</block>
</value>
<next>
<block type="procedures_ifreturn" id="K2~CLXTJ5b=T+=/6%m=~">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="Cjh^D.y[m3YQn},sC1(0">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="|uXT]6-.XcdAG-6HtffC">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="N@!AqGy7OCz9:zhv@f?K">
<field name="NUM">6</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="omKlSmgS{[5T:v{9(j}?">
<field name="TEXT">Saturday</field>
</block>
</value>
<next>
<block type="procedures_ifreturn" id=".XFx#9RZIGl!joSiMNyq">
<mutation value="1"></mutation>
<value name="CONDITION">
<block type="logic_compare" id="aqkbbBOzUTv/%JlX)V}S">
<field name="OP">EQ</field>
<value name="A">
<block type="variables_get" id="qrl+C-GvBF7QzLz8?@:u">
<field name="VAR">day</field>
</block>
</value>
<value name="B">
<block type="math_number" id="_[;I?)){=vm_jnSYHumL">
<field name="NUM">7</field>
</block>
</value>
</block>
</value>
<value name="VALUE">
<block type="text" id="MCTQyN!}ig#3~)B[r#q[">
<field name="TEXT">Sunday</field>
</block>
</value>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</next>
</block>
</statement>
<value name="RETURN">
<block type="text" id="revjgT`{%j^1mn*-SJ1a">
<field name="TEXT">Invalid day</field>
</block>
</value>
</block>
</xml>
See usage of this block in Create function from blocks with return value.
This block can be used only there and serves to return value in the middle of the function.
Sometimes existing blocks are not suitable to solve specific problem. With this block you can create your own block as a function, that can accept parameters and do some action. To write such a function you must know javascript. You can use inside all functions, that were created for pure scripting.
To write the code you must click the '...' at the ond the block and the editor dialog will be opened.
Otherwise the usage of this block is similar with standard function blocks, like Create function from blocks with return value or Create function from blocks with no return value.
This custom function block can return values. To return result from function write
return 'your result';
Like here:
<xml xmlns="http://www.w3.org/1999/xhtml">
<block type="procedures_defcustomreturn" id="mG^pXm=MO7vPl!c^/.Px" x="163" y="63">
<mutation statements="false">
<arg name="a"></arg>
<arg name="b"></arg>
</mutation>
<field name="NAME">sum</field>
<field name="SCRIPT">cmV0dXJuIGEgKyBiOw==</field>
<comment pinned="false" h="80" w="160">Summarise a and b</comment>
</block>
<block type="debug" id="U6pI-lE0VS#G):ELrQ(0" x="163" y="138">
<field name="Severity">log</field>
<value name="TEXT">
<shadow type="text" id="PBg^5*vuC?Isr)]pqx/u">
<field name="TEXT">test</field>
</shadow>
<block type="procedures_callcustomreturn" id="XuhUUF65jRZGB#YE(GTC">
<mutation name="sum">
<arg name="a"></arg>
<arg name="b"></arg>
</mutation>
<value name="ARG0">
<block type="math_number" id="h_[^zH{ILtnHrsxY0j~z">
<field name="NUM">5</field>
</block>
</value>
<value name="ARG1">
<block type="math_number" id="iIoph|b.?suX;)R=d|),">
<field name="NUM">6</field>
</block>
</value>
</block>
</value>
</block>
</xml>
For every created function in the menu appears additional block with the name of this function.
You can use it like normal blocks in you scripts.