It has always been this way. It would be better if the name ELSE was not there. Because it only functions as IF, then.. IF, then etc. This was the reason I switched to LUA scripting. When you want to solve it in Blockly you have to make large scripts which are sometimes hard to debug. To have one ...

Hello @alfred_j_kwak, Thanks for your answer … does that mean there is a bug in the Blocky script engine ? Is it possible to have a so big bug ? Can somebody test on his Domoticz and see if he has the same problem … I'm running Domoticz on a Synology, perhaps it's a specific problem to this dis ...

Yes I read what it says : In my case, if (condition){ } is just true, it's 2016-01-22 21:39:00.428, so "IF" block is executed SUNSET, thats OK ... BUT after I read : else if (other condition) { // executed only if "condition" was false and "other condition" is true } I read executed only if ...

Sorry to insist … I understand that adding just supplementary tests will prevent retriggering, thats OK ... But, I think the "ELSE IF" block should not execute if the "IF" block has executed ? Am I wrong ? Who can explain me that point ? If I'm wrong, what is the "ELSE IF" utility ? this is s ...

Hello, Thank you for your answer, I understand your answer, however, as far as I understand the "ELSE IF", this block should not execute if the "IF' block just executed ? IF this is SUNSET ... set variable to "NIGHT" (NUIT in french) and quit ... I'm missing something here ... Please can you help me

Hello in the above sample I can't understand why the if block is executing, and just after the else if executes too ? blocky.jpg and here is the log that shows the problem : 2016-01-22 21:39:00.428 SUN handler : SUNSET <==================================== end ngRepeat: item in filtered = (logitems ...