docs examples

docs/commandExamples.md

@@ -27,6 +27,26 @@ This will create a new repeating events with 1 repeat count and 60 seconds delay
 
 
 
+This is another approach to sending GET for change. As you can see, it's using addEventHandler instead of addChangeHandler. This will fire with every change. The index 1 here is a channel index. The $CH1 macro in URL will get expended to current channel value, usually 1 or 0
+<br>```addEventHandler OnChannelChange 1 http://192.168.0.112/cm?cmnd=Power0%20$CH1```<br>
+
+
+
+This will execute console command when IR event is received. Keep in mind it's using addEventHandler2, which is like addEventHandler, but takes two arguments.
+<br>```addEventHandler2 IR_Samsung 0x707 0x61 led_enableAll 0```<br>
+
+
+
+This will turn on LED with 500 temperature 500, dimmer 100 at 8:00:00 every Sunday (0x01 is a bit flag for Sunday, bit 0 means sunday, bit 1 monday, etc etc), 234 here is unique ID of clock event so you can remove it later. You MUST START NTP driver for it to work.
+<br>```addClockEvent 8:00:00 0x01 234 backlog led_temperature 500; led_dimmer 100; led_enableAll 1;```<br>
+
+
+
+This will turn on POWER at 12:00:00 every Sunday and Monday (0x01 is a bit flag for Sunday, bit 0 means sunday, bit 1 monday, etc etc), 567 here is unique ID of clock event so you can remove it later. You MUST START NTP driver for it to work.
+<br>```addClockEvent 12:00:00 0x03 567 POWER ON```<br>
+
+
+
 This simple timer will toggle LED state every 5 seconds. -1 hear means infinite repeats. The ! stands for negation and $led_enableAll is a constant that you can read to get 0 or 1. It works like $CH11, $CH4 etc (any number) for accessing channel value
 <br>```addRepeatingEvent 5 -1 led_enableAll !$led_enableAll```<br>