Motion, lights on has a mind of its own

[Guest aj84]

And my final thread of the day and year relates to a Fibaro Motion sensor with a relay module.

With help from a vesternet thread, I have a scene setup:

Motion == Breached 0s

AND

Hall (Variable) == Active

THEN

Light = on

 

Equally I have the opposite when Motion == safe 120s then turn light off.

 

This for 90% of the time works brilliantly.  I walk into the house and bang, the light turns on

I have the same setup upstairs so as I walk up the stairs, motion kicks in and bang the light turns on.

 

But every so often, it decides there is motion but it doesnt want to turn it on.  

Scenario:

Walk in, motion light flashes but light stays off.

Shuffle around, remove shoes, walk towards a room and suddenly it thinks oh I should really turn the light on now as there is definitely motion detected...and light turns on...sometimes just a little too late!

 

Upstairs scenario:

Walk up the stairs, motion flashes but no light. Go into bedroom, come out motion flashes: nothing on the light turning on.  And then suddenly motion flashes again and light turns on. hello!

 

The only thing I can think is there seems to be a notification always it seems in fibaro:

"To many instances"  And usually this is with the two motion sensor scenes

 

Is this the issue?  My Max running instances is currently set to 4.  Does this need to be higher?

 

Thanks all