Adding extra minutes to sunset

[B_b_B 0]

What I want to do is turn on my lights 15 minutes after sunset.

 

I found the following LUA code at the forum:

Please login or register to see this code.

 

When I try to do this, I get the error: "attempt to perform arithmetic on a nil value". All variables time and sunrise are set.

 

I have no clue what I am doing wrong.

Edited December 1, 2021 by B_b_B

[danidani 1]

I am not sure this is the easiest way but it works for me.

 

Please login or register to see this code.

 

[SmartHomeEddy 1,005]

Please login or register to see this image.

/monthly_2021_12/A6803ABC-D7E2-4C44-BE98-71D734F4ED8A.jpeg.027f904129058b44c8eec2bf6a4279df.jpeg" />

[B_b_B 0]

Not very different from my script? This is what I do:

 

Please login or register to see this code.

 

And that ends in an the error "attempt to perform arithmetic on a nil value"

2 minutes ago, SmartHomeEddy said:

Please login or register to see this link.

 

Trigger / condition is not an issue and try to get it working in Lua

[SmartHomeEddy 1,005]

12 minutes ago, B_b_B said:

Trigger / condition is not an issue and try to get it working in Lua

    +  

 

 

?

[B_b_B 0]

1 minute ago, SmartHomeEddy said:

Please login or register to see this link.

    +  

Please login or register to see this link.

 

 

?

 

That will give me the conditions in LUA. Which are not a problem in this case. Scene runs every minute.

[SmartHomeEddy 1,005]

OK, just thought you wanted to turn on the lights 15 minutes after sunset. 

 

[tinman 1,070]

18 minutes ago, B_b_B said:

 

That will give me the conditions in LUA. Which are not a problem in this case. Scene runs every minute.

 

now depending on what you trying to achive, it might or might not, be useful to trigger every minute to get status of something which happens once a day.

 

Generally the LUA engine will pre-check the trigger, and no execute any code if condition in not met, so less resources consumption. When you do it as "every minute", the engine will execute the LUA code and check there the value, so more resources used.

 

So you decide, when you can use "once per day" use condion block and save resources, or if you need every minute (for what so ever reason) use check in code instead. 

[B_b_B 0]

2 minutes ago, tinman said:

 

now depending on what you trying to achive, it might or might not, be useful to trigger every minute to get status of something which happens once a day.

 

Generally the LUA engine will pre-check the trigger, and no execute any code if condition in not met, so less resources consumption. When you do it as "every minute", the engine will execute the LUA code and check there the value, so more resources used.

 

So you decide, when you can use "once per day" use condion block and save resources, or if you need every minute (for what so ever reason) use check in code instead. 

 

I am creating 1 Lua script with all time bases actions. As I am using a HC3 Lite, and found that it is not possible to upgrade easily to a HC3 (shame on Fibaro!) I am tied to 20 scenes. I do care less about resources in this case, if needed I can switch from every minute to every 5 minutes of specific triggers. I expect that the Lua scene need to run about 10 times a day with different actions based on the time.

6 minutes ago, SmartHomeEddy said:

OK, just thought you wanted to turn on the lights 15 minutes after sunset. 

 

That is true, but this Lua script has a lot more actions

[B_b_B 0]

BTW, this is where the code comes from at this forum:

 

Maybe it is good idea to mention @jgab as he is the author of the original code?

[jgab 2,642]

22 minutes ago, B_b_B said:

BTW, this is where the code comes from at this forum:

 

Maybe it is good idea to mention @jgab as he is the author of the original code?

 

Yes, but you need to copy the whole scene code otherwise it will not work - the helper functions at the end of the scene are the one that allows you to  do 'tonumber' of a "time string" and thus do the arithmetic. 

So copy the whole scene and look at the examples.