Number of instances of scene has been reduced due to exceeding limit.

[Mib 15]

I get now since I have updated to 4.058 Beta this message:

 

 To many instances | Scene: Licht BEW
Number of instances of scene has been reduced due to exceeding limit.

 

the scene does not work anymore.

 

--[[
%% properties
620 value
%% globals
--]]
 
-- VARIABLEN Konfiguration (Bewegungsmelder muss oben unter %% properties aufgeführt sein) löst die szene aus
-----------------------------------------------------------------------------------------------------------------------------------------
local scene = 200 -- ID dieser Szene EG Vorzimmer
local motion = 620 -- ID des Bewegungssensors
local licht = 622 -- ID Lichtsensor
local switch = 769 -- ID der Lampe
 
local nachtstart = 1600 --22:00 = 2200
local nachtende = 0100 -- 07:00 = 0700
local starttimer = 60 -- licht an zeit (+ zeit des bewegungssensors - par. 6)
local lichtwert = 1 -- grenze zum nachtmodus (nur ausführen, wenn licht größer als)
-----------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------
---------------------Script-----------------
fibaro:debug("start1")
if (fibaro:countScenes()>1) then
 fibaro:debug("stop scene");
 fibaro:abort();
end
 
-- SCHALTE LICHT EIN & AUS (wenn nicht nacht)
if (tonumber(fibaro:getValue(motion, "value")) > 0 ) and tonumber(fibaro:getValue(licht, "value")) > lichtwert and (tonumber(os.date("%H%M")) >= nachtstart or tonumber(os.date("%H%M")) <= nachtende) then -- hier fehlt noch "und schalter aus"
 fibaro:debug("ausgelöst");
 --led auf wert einstellen
 fibaro:call(switch, "turnOn");
 -- timer start und einstellen
 timer = os.time();
 while os.time() - timer < starttimer do
 fibaro:sleep(1000);
 -- Timer zurücksetzen, wenn neue Bewegung erkannt wird innherhalb der Verzögerungszeit
 if (tonumber(fibaro:getValue(motion, "value"))) > 0 then
 timer = os.time();
 end
end
 -- Schalte Licht aus, wenn Timer vollständig abgelaufen ist
 fibaro:call(switch, "turnOff");
end
fibaro:debug("ende1");
fibaro:killScenes(scene);

 

 

 

[petergebruers 1,268]

I agree with user aleks.

Regarding the trigger frequency, the manual of the FGWP-101 says: "In extreme cases, reports may be sent *every second* if rapid and significant power load changes occur. Frequent reporting may overload the Z-Wave network so these parameter's settings should reflect significant changes in power load only."

I still have to experiment with parameters 40 to 49 to determine what would be the best setting for my plasma TV. I think user fuuss has the same type of TV set. I expect a plasma TV to draw significant more power when it's picture is "light" than when it's "dark". That would explain the rapid changes in power. But I have to test that hypothesis...

[fuuss 25]

I tried to change like you said

 

Please login or register to see this code.

But still I get

Please login or register to see this code.

So still the scene execute 2 times

[petergebruers 1,268]

This *might* be one of those scripts that is easier to read & write as an "autostart" script, an endless loop. I can try to do that, but probably not today. If anyone else want's to try that, or something else, don't hesitate.

[Guest sk8er000]

Hello, 

I've unfortunately update my system at the last beta, but after changing the value at some scenes to 10 everithing seems to work except this scene:

 

here's the LUA code (but the scene is created in block mode):

 

 

--[[

%% properties

463 value

506 value

51 value

%% globals

--]]

 

local delayedCheck0 = false;

if ( tonumber(fibaro:getValue(51, "value")) <= 19 ) then

delayedCheck0 = true;

end

setTimeout(function()

local delayedCheck1 = false;

local tempDeviceState1, deviceLastModification1 = fibaro:get(463, "value");

if (( tonumber(fibaro:getValue(463, "value")) > 0 ) and (os.time() - deviceLastModification1) >= 150) then

delayedCheck1 = true;

end

local delayedCheck2 = false;

local tempDeviceState2, deviceLastModification2 = fibaro:get(506, "value");

if (( tonumber(fibaro:getValue(506, "value")) > 0 ) and (os.time() - deviceLastModification2) >= 150) then

delayedCheck2 = true;

end

 

local startSource = fibaro:getSourceTrigger();

if (

 ( delayedCheck0 == true )

and

 ( delayedCheck1 == true )

and

 ( delayedCheck2 == true )

or

startSource["type"] == "other"

)

then

fibaro:startScene(61);

fibaro:call(252, "pressButton", "2");

fibaro:call(250, "pressButton", "2");

end

end, 150000)

 

is there something I can change to get this scene to work again? 

 

thank you all in advance

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[alex88 71]

 

I tried to change like you said

 

Please login or register to see this code.

But still I get

Please login or register to see this code.

So still the scene execute 2 times

 

 

I think it is doing what you want isn't it?

 

The power is >30 so the scene runs:

Please login or register to see this code.

Then it gets to the next check which is, is the power>80

Please login or register to see this code.

In the first debug it is telling you the power is 31.1, so at this stage the scene stops working at the second condition which requires the power to be >80, but then a second later the power has jumped to 81.1, so the scene runs through fully .

 

TBH, I haven't stopped to think about what it is you want this scene to do, but it looks fine to me as it's written i.e. based on the power readings it should run through twice.

 

Perhaps if you wanted more clarity you might want to add a new line under this one:

Please login or register to see this code.

which would be something like this:

Please login or register to see this code.

This way you would know why there were two scenes that ran.

 

I hope that makes sense.

[JanJoh 1]

Okaaaaaaaaaaaaaayyyyyyy!

I understand... Go to the scene... On the "General" page you will find: "Max. running instances:" and the default is 1!

You can set anything up to 10.

I guess you can remove the "countsScenes" incantation at the start of the script, this replaces it.

Problem solved.

 

The "sad" thing is that the "1" default also breaks a "magic scene" which is just "If no motion on 'tvättstuga' for 14 minutes, turn off the lights"

 

Sooo, when the default breaks a "boxed" solution built on the most fundamental of Fibaros tools... Well....

Please login or register to see this image.

/emoticons/default_wink.png" alt=";)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[Roy 0]

I have scenes setup the same as this, created via the graphic blocks way as listed below and still get the notification: - To many instances | Scene: K LED Off -  Number of instances of scene has been reduced due to exceeding limit.

 

Active = Active is so the lights don't come on during the day.

 

This is the simplest of scenes and have played around changing Max. running instances: and still i get the notification.

 

Please login or register to see this image.

 

 

 

 

This needs to be fixed and patched ASAP as it will put people off of buying this system. I'd expect Graphic Blocks just to simply work as it is the way most people will setup this type of scene.

 

I look forward to Fibaro patching this and explaining how to accomplish this via LUA.

 

Hal

 

Hi I think I found a solution for your problem. Just run some test at seems to work!

 

What you need to do:

1. uncheck all the trigger devices in the scene (advanced settings) and  hit "save"

2. go to advanced settings again and check all you trigger devices again. 

[fi-bar-oh 47]

Hi I think I found a solution for your problem. Just run some test at seems to work!

 

What you need to do:

1. uncheck all the trigger devices in the scene (advanced settings) and  hit "save"

2. go to advanced settings again and check all you trigger devices again. 

 

I'm off to test this because if this works you my friend deserve some credit with Fibaro!

[fi-bar-oh 47]

No difference here

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> same old issue... got all excited for a few seconds then

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

[Roy 0]

No difference here

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> same old issue... got all excited for a few seconds then

Please login or register to see this image.

/emoticons/default_icon_wink.gif" alt=";-)" />

 

Sorry, forgot to tell that you also need to increase your "Max. running instances:" , in the general overview of your scene. 

 

It will probably work with 2, but you can also try 4 to be sure.

 

 

Then execute the above steps and I think it should be fine. Your can test your scene now with the "run" button. If not, execute step 1+2 again. 

 

Let me know if it works. 

 

If, not send me some screenshots. . 

 

Good luck!

[fi-bar-oh 47]

Sorry, forgot to tell that you also need to increase your "Max. running instances:" , in the general overview of your scene. 

 

It will probably work with 2, but you can also try 4 to be sure.

 

 

Then execute the above steps and I think it should be fine. Your can test your scene now with the "run" button. If not, execute step 1+2 again. 

 

Let me know if it works. 

 

If, not send me some screenshots. . 

 

Good luck!

 

No it will not work

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> even if i set it to 10! max safe zone is then 300 secs anymore than that it will not work!

[Roy 0]

No it will not work

Please login or register to see this image.

/emoticons/default_smile.png" alt=":)" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" /> even if i set it to 10! max safe zone is then 300 secs anymore than that it will not work!

 

Screenshots?

[fi-bar-oh 47]

Rather than screenshots much quicker to type it...

 

Scene #1: ON (general settings instances = 2)

if motion == breached

then

spotlight == on

 

^^ this scene works fine

 

Scene #2: ON (general settings instances = 10)

if motion == safe (300)

then

spotlight == off

 

^^ this scene works with 10 instances!

 

Scene #3: ON (general settings instances = 10)

if motion == safe (900) [30 secs * 10 = 300 and 900 is required]

then

spotlight == off

 

^^ this scene will fail... should i wish to extend to 15 minutes!

[Joacim 11]

Power-trip you are still creating a new instance every time your sensor goes safe that's why you can't do it like that! Either you set the safe timeout on the sensor to a higher number or you have to create a global variable to hold the present state.

 

If safe and 0 instance running

Set 1 instance running

Sleep 900

Turn light of

Set 0 instance running

 

That should work!

[wienog 107]

Rather than screenshots much quicker to type it...

 

Scene #1: ON (general settings instances = 2)

if motion == breached

then

spotlight == on

 

^^ this scene works fine

 

Scene #2: ON (general settings instances = 10)

if motion == safe (300)

then

spotlight == off

 

^^ this scene works with 10 instances!

 

Scene #3: ON (general settings instances = 10)

if motion == safe (900) [30 secs * 10 = 300 and 900 is required]

then

spotlight == off

 

^^ this scene will fail... should i wish to extend to 15 minutes!

An other way to do it is  to add a scene 3 that starts when the motion sensor is 'safe' and switches the light off after 15 minutes (or anything you want). Then you add to scene 1 some code that it should kill scene 3 if scene 1 is triggered (fibaro:killScenes(3) ) 

[fi-bar-oh 47]

An other way to do it is  to add a scene 3 that starts when the motion sensor is 'safe' and switches the light off after 15 minutes (or anything you want). Then you add to scene 1 some code that it should kill scene 3 if scene 1 is triggered (fibaro:killScenes(3) ) 

 

good idea for hc2 owners and again users should not have to do this considering the 'user friendly' interface... shame fibaro just killed all hcl timed scene functionality above 5 min in the process though!

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

[Hallamnet 17]

Hi I think I found a solution for your problem. Just run some test at seems to work!

 

What you need to do:

1. uncheck all the trigger devices in the scene (advanced settings) and  hit "save"

2. go to advanced settings again and check all you trigger devices again.

Sorry for the late reply.

I have tried this and this has had no effect.

Roll on on the next firmware update.

[Elektrorob 2]

I have a HCL so I use graphic blocks.

I try to explane what I have done to make a scene run without the message "number of instances of scene has been reduced due to exceeding limit".

(because my english is not that good)

I have made a variabele   "sunset is set"   when there is sunset.

And everytime i had this messages popt up.

I saw that i used this variabele   "sunset is set"   in 4 different scenes.

So i set the "max. running instances" at 4 and now the message did not pop up anymore.

I hope that you understand me and maybe it helps a bit.

[Roy 0]

good idea for hc2 owners and again users should not have to do this considering the 'user friendly' interface... shame fibaro just killed all hcl timed scene functionality above 5 min in the process though!

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

 

I agree. Sorry but I don't have a lot of time this week to look into it, but the new addon is not "userfriendly" for the fibaro block-scene users.

 

Aleks is right. you should kill all instances when possible, however this is devious proces with building blocks.

[DoDoR 1]

Hi friends need your help,

 

I have the same issueת i can’t solve it (replying to Number of instances of scene has been reduced due to exceeding limit.)

 

The Scene is supposed to check that there is no movement in the room more than ___ minutes and then turn off the air conditioner.

 

But I get the same message on all similar scene (set up for number of scene is 10) :

(replying to Number of instances of scene has been reduced due to exceeding limit.)

 

Can you please advise ? 

 

--[[

%% autostart

%% properties

365 value

%% events

%% globals

--]]

 

local startSource = fibaro:getSourceTrigger();

if(startSource["type"] == "other") then

fibaro:call(362, "setMode", "0");

else

if (( tonumber(fibaro:getValue(365, "value")) == 0 )) then

setTimeout(function()

local delayedCheck0 = false;

local tempDeviceState0, deviceLastModification0 = fibaro:get(365, "value");

if (( tonumber(fibaro:getValue(365, "value")) == 0 ) and (os.time() - deviceLastModification0) >= 1800) then

delayedCheck0 = true;

end

 

local startSource = fibaro:getSourceTrigger();

if (

 ( delayedCheck0 == true )

or

startSource["type"] == "other"

)

then

fibaro:call(362, "setMode", "0");

end

end, 1800000)

end

end