hub.setTimeout() bug?

[verstegenJCT 5]

After my update (5.171) I get error messages in my scenes. After I assign, calculate and use variables in the hub.setTimeout() function, I get the following error:

 

[08.12.2024] [11:35:36] [ERROR] [SCENE860]: stack index 1, expected number, received number: not a numeric type that fits exactly an integer (number maybe has significant decimals) (bad argument into 'int(unsigned int, const sol::basic_protected_function, false, sol::basic_reference >&)')

 

Is this a bug in the update?

[jgab 2,641]

If you manage to give the time as a (large) float you get that error

Please login or register to see this code.

Please login or register to see this code.

Try to check/log the type of the value before you call, ex.

Please login or register to see this code.

It should be an 'integer'

[verstegenJCT 5]

Thank you @jgab. I have now found a temporary solution by adding the math.floor() function. example:

local s = os.date("%S")

            local timeout = math.floor(60000 - (s * 1000))

            fibaro.setTimeout(timeout, function() -- wait 1 minute

                awayTimer()

            end)