Just a pointer to help you write rules. In the latest firmware builds (last 2 weeks I guess) I added a page on Tools => System Variables. These show all system variables and their current output. That may be useful for debugging. Hi, thank you. I was using that but while I have managed to solve thi...

grovkillen wrote: ↑22 Sep 2018, 17:59 Okay I need to try it myself. I'm currently in the move with getting this ship floating

no worries, it's working just need to prepare for resets and power outs so not critical

grovkillen wrote: ↑22 Sep 2018, 17:22 You can always first try to add it to a dummy. I'm not sure system variables are up to speed for it to be used inline.

do you mean like :

TaskValueSet,3,4,%syshour%

tried this and the dummy is not set even though the clock is up and running

also tried :

If %syshour% > 13

cant get this to trip the timers.

having got everything else to work I must have missed something daft but stuck again

well I almost have it. the on and off routines work fine but the reset on boot is causing a problem. I think I need to reference %systime% rather than clock#time but its not playing nice. I started with : If %systime% > [clock#onh]:[clock#onm]:00 and %systime% < [clock#offh]:[clock#offm]:00 but simp...

Instead of 00 you can use 59 :lol: exactly what I am doing. it works but its messy trying to decide how far I want to go at the moment as I can add loads of variables so could setup everything in one rule and make any editing easy but not sure if I want to go that far. its tempting as this is stand...

Yes that would not render in a match. Time stamps need that leading zero. You could use system variables maybe? And do tests on a bead board? 8-) I keep forgetting I have breadboard! :oops: never have the correct dupont cables when I need them! need M-M so of course today can only find M-F or F-F b...

just thinking about - on Clock#Time=All,[clock#onh]:[clock#onm] do if [clock#onm] is less than 10 will missing the leading 0 cause an issue? so with : [clock#onh] = 9 [clock#onm] = 0 [clock#onh]:[clock#onm] = 9:0 which I could see being a problem as the format isn't what is expected. do you know wha...

my poor fish will be getting a disco today as I start testing this

what difference does the dummy type make?

just curious as I set that the first time but the 4 variables show no matter the type set

with the clock#time command would this work?

on Clock#Time=All,[clock#onh]:[clock#onm] do

Yes the rules editor need some love, I will give it some in a couple of weeks. just thinking about ways to make this one more usable for me and thinking that I can split the ON routine from the OFF routine and the Reset routine when I write it and make them separate rules so that I can comment more...

amazing what a large G&T some food and great advice can do. I think I got there.... on Clock#Time=All,09:00 do //will run once a day at 9am timerSet,1,10 //Set Timer 1 for the next event in 10 seconds timerSet,2,10 //Set Timer 2 for the next event in 10 seconds TaskValueSet,2,1,4095 TaskValueSet...

Instead of delay you can use timer. That way you can build a "loop". Tomorrow I hope to have some time to help you out with that. thanks, I may be getting there :D on Clock#Time=All,22:12 do //will run once a day at ?am timerSet,1,1 //Set Timer 1 for the next event in 1 seconds TaskValueS...

And to make it clear, the rules are parsed in the core loop. It's not a actual running code inside the ESP. So it's pseudo coding. sounds similar to Domoticz "blocky" great for really simple things but falls over if you want to do anything less simple. hoping I can work with or around any...

If you upload all your settings (screenshots) I'd be able to assist you better. not sure there are any settings. vanilla upload and added the PCA9685 as 2w on D3 and D4 added rules from the advanced tools and NTP server doesn't look like I can upload a pic to this site and don't have any image host...

Multiple ifs are not yet supported. ok..... but each if on its own only runs once. I would have expected a if to loop until the condition was satisfied but this does not work either. what I am trying to achieve shouldn't be too tricky but if the rules don't let me then will I need to do this in the...

grovkillen wrote: ↑21 Sep 2018, 21:11
Where did you post the rules? I wish to help.

Hi, thank you, posted in viewtopic.php?f=6&t=5838

any help would be great as i think i must be nearly there but head is getting scrambled now

well 4 hours later and I am getting fed up of something that should be simple giving garbage outputs and nonsensical logs. is this just a case of not being something that can be done with rules? I have tried multiple ways of getting a trigger and simple increments to variables which according to the...

thank you very much. I was hoping so but have so far had a simple setup and a frustrating 4 hours not getting what should be a simple rule to work..... I really hope I am missing something obvious but at this rate the love affair could be over before it starts. The possibilities are great if it work...

ok made a few changes and slowly getting there..... I have changed the dummy device to "light" and variables to "dim1" and "dim2" on Clock#Time=All,16:15 do //will run once a day at ?am if [light#dim1]<4095 Delay 100 TaskValueSet 2,1,[light#dim1]+1 PCAPWM,0,[light#dim1]...

hi, I have created a dummy device called "Dimmer" and given it values names "1" and "2" creating the following rule and without the IF I can switch on and off at the given times but I want the PWM to increment by 1 every second and as it stands nothing happens. what am ...

Hi There, been using ESP's for a while now as started with Sonoff devices and quickly flashed to Tasmota and set up Domoticz. grabbed a pile of nodeMCU with motor shields for additional projects and have finally found a need when I killed the controller on my home made LED aquarium lighting so after...