[SOLVED]Too many instances in a LUA script for a RF keypad. [solved]

[RobVeenis 0]

Community,

 

I use a keypad with tags with a Fibaro binary senso to switch mij alarm on and off.

 

Somebody made me a LUA script for that.

When I present a tag the alarm will switch on or off.

 

This is the script:

 

--[[
%% properties
245 value
%% weather
%% events
%% globals
--]]

local startSource = fibaro:getSourceTrigger();
-- 2 streepjes is commentaar
fibaro:debug(fibaro:getGlobalValue("Alarmstatus"))
if (
 ( tonumber(fibaro:getValue(245, "value")) > 0 )  -- keypad activated
and
 ( fibaro:getGlobalValue("Alarmstatus") == "uit" )
)
then
    fibaro:setGlobal("Alarmstatus", "aan");
elseif (
 ( tonumber(fibaro:getValue(245, "value")) > 0 )  -- keypad activated
and
 ( fibaro:getGlobalValue("Alarmstatus") == "aan" )
)
then
    fibaro:setGlobal("Alarmstatus", "uit");  
  
end

fibaro:debug( fibaro:getValue(245, "value"))
fibaro:debug(fibaro:getGlobalValue("Alarmstatus"))

fibaro:sleep(3500)
fibaro:abort()
 

My problem is that I get "too many instances".

 

I guess I need to include the following line:

 

"maxRunningInstances": 2,

 

But I have no clue how and where.

 

Is there anybody that could and would tell me how to do so?

 

It would be highly appreciated!

Please login or register to see this attachment.

[3JL 7]

Hi Rob,

this may help:

there is a sleep command at the end of your code. Likely (but I am not sure) this is to prevent repeated sensing of a tag that’s supposed to be only once.

 

in other words: now that you present your tag, the scripts prevents the alarm from turning on and off because it reads the tag twice. Essentially it waits 3,5 seconds before a new tag is accepted.

 

If this is true, the "too many instances" thing is harmless and even functional. However, it can be annoying. Another way to achieve the same would be to include something like the second example here: 

Please login or register to see this link.

 

In the settings you can then increase the number of allowed instances.

 

let me know if this helps!

J

 

[RobVeenis 0]

Hi J,

 

Thanks for your reply.

 

I have tried your suggestion with >1 until >3 but it didn't help.

Good to hear that it is at least harmless! that makes it allready less annoying 

 

Your thoughts about the delay are correct, without this code the alarm switched on and immediately after it switched off.

 

[3JL 7]

6 hours ago, RobVeenis said:

 

I have tried your suggestion with >1 until >3 but it didn't help.

 

What exactly do you mean? 

[RobVeenis 0]

I mean that I tried the "count scenes"

[3JL 7]

Can you share your code? With the solution suggested, you should no longer get the notification.

[RobVeenis 0]

3JL,

 

Here is the code.

 

--[[
%% properties
245 value
%% weather
%% events
%% globals
--]]
-- Only allow one instance of the current scene to run at a time
if (fibaro:countScenes() > 1) then
  fibaro:abort()
end
local startSource = fibaro:getSourceTrigger();
-- 2 streepjes is commentaar
fibaro:debug(fibaro:getGlobalValue("Alarmstatus"))
if (
 ( tonumber(fibaro:getValue(245, "value")) > 0 )  -- keypad activated
and
 ( fibaro:getGlobalValue("Alarmstatus") == "uit" )
)
then
    fibaro:setGlobal("Alarmstatus", "aan");
elseif (
 ( tonumber(fibaro:getValue(245, "value")) > 0 )  -- keypad activated
and
 ( fibaro:getGlobalValue("Alarmstatus") == "aan" )
)
then
    fibaro:setGlobal("Alarmstatus", "uit");  
  
end

fibaro:debug( fibaro:getValue(245, "value"))
fibaro:debug(fibaro:getGlobalValue("Alarmstatus"))
fibaro:sleep(3500)
fibaro:abort()

[AutoFrank 372]

@RobVeenes

Increase the count just below the header to >3

and raise the number of instances in the scene General tab ( this defaults generally to 2) 

 

The way it is setup now is allowing only one concurrent scene to execute at any point so if your tag registers twice, it gives you the notification you see ...

 

 

 

 

[RobVeenis 0]

@Autofrank,

 

Thanks for your suggestion!

 

At first the problem got worse, increasing the count to 3 and the number of instances to 3 made that the script ran 3 times, switching on, off and on again.

Scenes based on the status of the alarm were not happy with that so the result was that I had 4 scenes with too many instances instead of one!

 

But when I put back the count to 1 again and left the number of instances at 3 the whole problem was solved!

 

Now the script runs once to switch the alarm either on or off and the error message doesn't come back.

 

Thanks a lot to you and 3JL for your help!

 

[3JL 7]

Great! Happy to be of help