Too many instances (but only one max instance!)

[europa 0]

I've read everything i can find on the too-many-instances error, and have followed the advice in a PDF to set most scenes to max one running instance; however, i am still getting frequent too-many-instances errors. Below are two examples of very-simply scenes that give me the error. They are set to one max running instance. I only use block scenes as i can't write LUA code. Any ideas what is going on?

 

Please login or register to see this image.

/monthly_2018_12/image.png.473dd56ac0f5ff6a4b344c481f86395f.png" alt="image.png.473dd56ac0f5ff6a4b344c481f86395f.png" />

 

[malitan 1]

Me to also I got  too many instances errors. why ?

Please login or register to see this attachment.

[jakub.jezek 370]

I would not say it is error message. It just gives you info, that scene was triggered again.

 

@europa, your scene with water would probably require more instances, because it could cycle and hence action could not be done. If it cycles, it creates new instance. So i would probably go with 3 - 5 instaces in this one, just to me sure.

In 2nd scene i would remove Light Sensor 10 and FFS Ceiling from Trigerring device (checkboxes above scene editor), since it gives me felling, that scene has to be triggered at armed and breached sensor. It can stay in scene, but not as Trigger. With that you should minimaze 2nd scene to 1 or 2 instances.

 

@malitan, this is little bit puzzled without additional info Is this scene triggered by that sensor in condition or with Fibaro alarm or both?

 

[malitan 1]

hi @jakub.jezek

 

The scene is very simple. when the Motion sensor breached then the alarm is turn on.

[jires 17]

Hi @malitan

It is not possible to build in the block scene some functions to prevent simultaneous instances of the same scene. I can only be done in properties as you do, but you have notification every time when scene trying to run.

 

I don't know, how you planning this scene to work, but there is solution maybe..

If motion sensor triggering a scene, and scene lasts 900s, then you can change parameters in sensors advanced settings that it will be blind for movements longer time. In that way, you will have fewer situations when sensor changing state from not breached to breached, and will trigger your scene fewer times.

[europa 0]

@jakub.jezekIf i uncheck the Light sensor 10 and FFS ceiling triggering devices, will they not be ignored as conditions for triggering the scene? If not, why are the checkboxes automatically ticked? Is there a better (more efficient) way of writing this (and similar) scenes?

[jakub.jezek 370]

@europa, they will not be ignored in scene condition. They just will not trigger scene. Scene will be triggered only by sensor, when breached and armed. I have tested this with predefines variables in one or two projects.

[Hildybeest 0]

I find that Fibaro needs some usability experts... It is one thing to be powerful by being advanced, however true elegance in design is achieved only when advanced technology is reduced to a very palatable dish that most can enjoy...