![]() You can also use wildcards in the time setting like All,**:00 to run every hour. You can define triggers on specific days or all days using "All" for days indicator. Triggered every minute with day and time like: Mon,12:30 or Tue,14:45. Publish %sysname%/NTP,Updated time at: %systime% Triggered when the time is set by an update from NTP Triggered the first time (after boot) NTP is updating the unit Publish %sysname%/warning,Intruder alert! Triggered when (someone) has tried to login to a ESP unit with admin password enabled, but have failed to enter correct password Triggered when the ESP has changed to access point, will also trigger first time the unit connects to the wifi Triggered when the ESP has connected to wifi Triggered when the ESP has disconnected from the broker (the MQTT Import plugin uses a separate connection than the generic one) Publish %sysname%/status,MQTT Import is now operational Triggered when the ESP has connected to broker (the MQTT Import plugin uses a separate connection than the generic one) Triggered when the ESP has disconnected from the broker Triggered when the ESP has connected to broker Triggered just before the ESP goes to deep sleep You should not name your devices and value names so that the combination equals to any of the below listed system events! of the unit:Īs described already, each task can produced one or more events, one each for each measured value. Some special cases are these system triggers which is triggered upon boot/reboot/time/sleep etc. Where the "inequality function" is a simple check: The trigger can be an device value being changed:ĭeviceName# ValueName Operator (inequality function) Up to two AND/OR can be used per if statement, that means that you can test three float values and if the statement is true/false corresponding action will take place. On test do if =0 or =0 or =0Įndif endon on test2 do if =1 and =1 and =1Įndif endon on test3 do if =1 and =1 or =0 Depending on plug-ins in use this might lead to unpredictiable, unreliable behaviour, advice is not to exceed 3 levels of nesting.Īs of mega-201803. This possibilty of nesting events is also limited, due to its consumption of stack space (IRAM). An "event" can be called from a "trigger". ![]() Only simple if/else was possible in older versions, there was this workaround for the limitation of not being able to nest. If the "else" part is not needed it can be removed: Or multi-line (need to be closed with an "endon"):Īlso simple if. The Device needs to be "Switch Input" with the following settings:Īfter rebooting the ESP, the LED will start blinking 10 seconds on then 10 seconds off.Īlternatively the built in LED on many ESP8266 boards like the WEMOS D1 mini can be controlled using GPIO2. The example above shows an experiment with a LED, connected via a resistor of 1k to GPIO12 and to ground.Ī virtual switch needs to be created in the "Devices" section to allow the reading the state of the LED (on or off). Here you can start experimenting with Rules: To enable rules, go to Tools/Advanced and check the Rules checkbox.Īfter clicking Submit, you will find a new page added. Rules can be used to create very simple flows to control devices on your ESP. 4.14 One button, multiple actions using long pressĪlong with ESP Easy R108, a new feature was enabled, named Rules.4.13 Custom reports to Domoticz with own IDX.4.12 Report IP every 30 seconds using MQTT.4.11 Dew Point for temp/humidity sensors (BME280 for example).4.6 Starting/stopping repeating timers with events.
0 Comments
Leave a Reply. |