Single-click light operation

[Vladimír Třebický]

Hey all!

[I'm new to this, got my house finished a few months ago and now am starting to make adjustments to the supplier Loxone setup.]

Is there a (reasonable) way to switch to a single-click operation of light switches? I.e., by default, a single click cycles through moods and a double-click turns lights off. Instead, I'd like a single click to:

* Cycle through moods *including* "lights off".

* Turn off lights of the last click has been longer than X seconds.

I'm guessing there is a way to do this, but I was hoping I'm maybe not the only one who gets occasionally irritated when the capacitance sensor on the Touch doesn't pick up the first click.

Thanks!

V.

[duncan]

im assuming you are using loxone touch wall switches? then you need to change their mode from pulse or automatic to on/off to be able to detect a long click

choose 2 of the 5 inputs from the touch, pass each through a longclick block and feed the 01 (short click) output to the + and - inputs of the lighting controller to cycle through the moods

connect the long click 2nd, 3rd and 4th outputs to the off input of the lighting controller - this is to catch any length of long click

there will be a slight delay (the time taken by the long click to evaluate the input) 

[duncan]

if you want a really long click there will be an unacceptable delay using this method above so this will work, keeping the delay to a minimum:

[Paul Watkin]

for the first question - in the loxone config file for the installation open the relevant lighting controller and under the moods tab create a mood called off using the green +, you can then cycle through moods including off - the column with the plus in it determines if the mood is added to the moods you can cycle through via the switch - useful if you want to have moods that can only called by an automation or sensor 

You can also add moods via the app but i find config simpler (also if you do make changes via the app, make sure to save them into config with a save from miniserver when you next open config)

Depending on what automation bits you have installed the double click may well do a whole lot more than just turn the lights off - it is supposed to signify leaving the room so may also adjust heating, shading, audio etc

in previous versions of config you were able to turn off double and tripple click on the switch properties but I can't see it in the latest version but may not be looking in the right place as still getting used to the new software

for the second question i am struggling to understand the use case as you would potentially set a mood and then x many seconds later the light would turn off whether you wanted it to or not - would need more of an explanation as to what you are trying to achieve

Paul

On Sunday, 22 March 2026 at 13:55:49 UTC vladimir...@gmail.com wrote:

[Vladimír Třebický]

Thanks everyone! Sorry, I didn't do a great job explaining the Why.

* Most guests don't understand that lights need to be turned off using a double click. My kids struggle with it too. (Yes, I have motion sensors, so lights don't really need to be switched off very often, but 1. they're not in every room and 2. I disable them in Night mode.) From UX PoV, people IMHO subconsciously expect a single-tap operation: tap once: lights are on, tap again, lights are off.

* I have the basic Touch Tree buttons, i.e., the plastic ones. I'm not sure what's wrong exactly, but maybe 30% of the cases when I try to double-tap, only the second tap gets registered, i.e., instead of turning off the light, it just cycles the mood.

A simple solution to my, perhaps extravagant requirement is to simply only have 2 moods: On and Off. But then I like moods! Well, I only really have 2: Bright and Dim, but still!

So what I was hoping for is what I crudely tried to describe above. Perhaps a different way to look at it (i.e., no long clicks involved):

* If off, a tap turns the light on.

* If on, a tap turns the light off. *Except* for when the tap comes within X seconds (say 3) from the last one, it cycles the mood instead.

I guess I could Pico-C this, but I'd need a block for every Touch and I'm guessing it's not great to have so much Pico-C.

Again: My Loxone setup works great, this is my first smart home and I'm having a ton of fun with it. This single-tap thing is almost a vanity, I was just wondering if others might have thought about something like this, too. There's a good chance I'm fixing the wrong problem, too!

Thanks!

--
You received this message because you are subscribed to the Google Groups "Loxone English" group.
To unsubscribe from this group and stop receiving emails from it, send an email to loxone-englis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/loxone-english/3fa93437-c9d4-403b-a01f-c6a088760509n%40googlegroups.com.

[Jonathan Dixon]

Try this:

* Connect your switch to the T5/1 input rather than M+

* Order the moods with your default mood as the first mood, OFF as the second, then all the others listed after it

(As others mention, if you want some moods to be app/automation only and not available from the push button, unselect them from the "+" column)

This isn't quite what you need, but is very close: for most users a single click will turn on (DefaultOn) unless it is already on in which case it will turn it off.

The exception is if the device is currently on but set to a mood other than DefaultOn. In that case, they must press the button twice: the first press sets it to DefaultOn, and the second press advances it to OFF. While not perfect this is fairly usable in practice because users might initially think they didn't press it correctly the first time. It also partially introduces the idea of double tap which is the logical progression anyway.

It's what I use in my house, so suggest you try it before going any further.

Doing exactly what you want is unlikely to work in picoC because that introduces high latency and results in laggy responsiveness. I think I could probably cook up the descrete function blocks that would achieve this but it'd be tedious and cumbersome to maintain. (What you really want is a T5/OFF input but unfortunately that doesn't exist)

 

To view this discussion visit https://groups.google.com/d/msgid/loxone-english/CAFsHw-2B0P8Twnm%3DjVVzf3uohvqsHQvRCeLp%2BeMxDjXia8P22g%40mail.gmail.com.

[Vladimír Třebický]

Very cool, thanks, I'll try this!