Out of memory /Number of instances of scene has been reduced to high memory usage.

[fuuss 25]

Hi Guy's 

 

I have a problem with a scene , i am on the latest Beta Firmware and I get

 

Out of memory | Scene: Global Check

 

Number of instances of scene has been reduced to high memory usage.

 

What is wrong with this scene ?

Please login or register to see this code.

Thanks in advance for help

 

 

[Alex 32]

Remove "Night" from the GLOBALS header:

Please login or register to see this code.

By changing the global variable the script want to be called again and again.

Why it says "Out of memory" I don't know right now.

[Guest bozman]

Hi, could someone explain more regarding the %% globals, when should I have a value there?

I believed that it always should be there if you want to read that value, but maybe fibaro:getGlobalValue is enough?

 

I have the same problem as FUUSS with memory related issues.

And it's really hard to troubleshot these kind of problems if the limitation in software isn't telling you anything more.

[chaicka 195]

I am pretty new to LUA scripting. Based on recent attempts to troubleshoot some scripts I have and writing new ones, it seems with 4.061 or 4.062 firmware, if global-variable is added to the %%globals section, it keeps triggering the scene/script to run whenever that global-variable is changed. I have since removed it and just use fibaro:getGlobalValue and the script works fine so far and also no more "exceed instances" error/alert coming up.

[Guest bozman]

I tried it quick on a scene firmware 4.062 and if

I use fibaro:getGlobalValue in a if statement and I do not have

that global value in the %%globals it never runs that if statement, 

 

changed it back to have in the %%globals then the if statement works fine.

I can't really understand the logic here.

[boerremk 84]

You only use %%globals if you want a global variable to trigger a scene:

 

I use it to set my alarm; if the global variable "Sleeping" or 'PresentState" is changed, the scene for arming/disarming devices will be run automatically. if the value is 0 is will disarm devices and if set to 1 it will arm devices.

 

So if you just want a value of a global variable you don't need it.

 

top of the Alarm scene:

--[[
%% properties
%% globals
Sleeping
PresentState
--]]

[Guest bozman]

Ok so you are saying that in the scene for instance if you have a sundown as global value you never have in that scene

if sundown=yes then

 turn lights on

end

 

it's enough to have it in the

%%globals

sundown

 

and then in the rest of the scene.

 

lights on

 

that's it?

[boerremk 84]

You will always have to do the check, because if the global variable is saying no, it still will set the lights on (it acts on the change not on the value).

 

Scene 1:

--[[
%% autostart

%% properties
%% globals
--]]

if sundown then

  fibaro:setGlobal("sundown","yes")

elseif sunup then

  fibaro:setGlobal("sundown","no")

end

 

Scene 2:

--[[
%% properties
%% globals
sundown
--]]

if getGlobalValue("sundown") == "yes" then

  lights on

end

 

But you will normally only use it if you really want to have a instant trigger on a change, if you want to set the light you can better make a scene checking the global variable with getGlobalValue and have a  while loop (or with settimeout).

[Guest bozman]

Ok, thanks for that clarification!

[fuuss 25]

I don't really understand what I have to change now , and why this error comes now , and didn't came before

[boerremk 84]

You have to remove the word Night just after %%globals.

 

What the script does is changing the global variable, but the script is triggered by the change of the variable, so it will come in a loop.

Please login or register to see this code.