I guess it can be a nice feature to disable or suppress events. Not many requests have been for it. ... only by some ppl migrating from Tasmota ;) NO !!! .... normally I use python / micropython ... But i found this method/possibility very help- and powerful ... a kind of "Master-Device" ...

thanks for all of this stuff.... BUT... ;-): in Tasmote it is very fine to generate a kind of blocks of events (rule1 / rule2/ ...) - and by deactivating such a block all events written in it are disabled - or - activating/enable. In my case I would have separated "DataCalculation" and &qu...

Thanks .... so all rules sets are finally one big programm-area... this is a big difference to Tasmota ... BUT EspEasy a a very nice stuff ... much to huge for my old brain ... THANKS A LOT !!! AND: with <TaskDisable> and <TaskEnable> my project works fine .. THIS is the final code....(if somebody e...

what is the reason formultible "rules set x" ?
Is there any difference in handling the code within different Rules Sets?
Thanks - stepfl

Have you tried the VL53L1X? That has a range up to 4 meter, where the VL53L0X has a max range of 2 meter ... Yes I did and I 'll use it .... but - in this case (dimesion of the "Platine") I'll prefere the LX53L0X... and the moving Average with enough points ist slowlier but is good enough...

this project should measure the Level of Oil in the Tank. The LX... works very fine in the rang up to 1m then it starts to jump around. => moving average ... The HeatingController (Heizungssteuerung) has not so many possibilities to enter the Oillevel-Data - the best way is to send PulseCodes ... bu...

probably you could be so nice and check the other part .... calulation of a moving average... the Reason: the Data of VL53L0X ( 100mmm ... 1600mm) jump a lot and I didn't want to wait too long for the first usable Data... VAR#10: actual runnicng counter of MWs in the sum of MWs (VAR#1) VAR#2: actual...

my first trial of ... : actual i use GPIO2 becaus of the LED :_) to change easily the TimeValues i use: VAR#7:Time of Start-/StopSequencePulse (actual 2000ms), VAR#6: Time of DataSequencePulse (actual 200ms) / VAR#5: defines START / DATA / STOP VAR#4: Value to be send // Output: PulseSequenz of VAR#...

thanks a lot .... YES - i know ... to use delay is not a good idea ... and checking the GPIO too... this was the result of my "don't know how to..." looptimerset_ms seems to be the solution - a easy one too ... I'll try it this evening ... thanks a lot! AND .... the stuff of how it works w...

sorry - I'm very new with EspEasy - up to now I was using Tasmota or Micropython. BUT - EspEasy seems to be very interesting for my project(s)! NOW I've to connect ESP to a special Controller which has only a kind of PulseCounter as entry. So I try to generate/convert the measured Value to a pulsese...