Loxone Support Community

Find answers, ask questions and become part of the Loxone Community.

Loxone Support CommunityCategory: Loxone ConfigNuisance tripping of lights
3 years ago
Nuisance tripping of lights

Hi,

I have a simple setup in the master bedroom with a lighting controller, three light circuits and a presence sensor. I have set up a Night Mode to automatically come on at 10pm and off at 7am.

I know Night Mode is operating because I have ticked the "use" box and I can see it come on. I have connected the night mode to the DisP input of the lighting block, and I have also set an automatic scene called Night which comes on if night mode is active.

Despite all this, last night at 1:48am all the lights came on at full brightness, and the Presence history log showed presence active at 1:48am.

I have tried using Simulation mode in config and I cannot replicate the problem.

Has anyone else experienced anything like this? Is there some additional fault finding I can do?

Regards,

Lindsey


Edit: I have found out that the Touch Nightlight (which enables night mode with a triple click) also disables night mode with a triple click. So If you forget that night mode was on, triple click when you go to sleep, you are actually disabling night mode. This seems like a bug.

1 Answers
3 years ago

Hi Lindsey

What function block are you using to activate your Night operating mode? The recommendation, and how Auto config does this is through a Switch block.

A switch block has a Tr, O, and R input

Tr – can change the output on or off it is a simple trigger.

O – can only turn the output on

R – can only turn the output off.

Therefore if you were using a switch block and had assigned the Nightlight to Tr then it is working exactly as you have configured. This is why it is our general recommendation to use O and R inputs to have dedicated actions, and this is how indeed auto config will do it for you.

KR

Hugh

3 years ago

Thanks Hugh – yes, I was activating Night mode using the Tr input on the switch so each subsequent activation was toggling the output. Changed to O and all OK now!