Disable controls in app?

[J V]

Hello

Simple question: is there a way to disable controls in the app? The child lock for most blocks seems to affect the inputs to the block, but not the UI aspects...

I have some controls that I would like to see disabled under some conditions (specifically: some things controlled by a computer that is not always switched on).


I'm now thinking that I would need to use a virtual input, and that one direct to the button/switch/whatever, use childlock on that last one and feeds it status back to the virtual input. It just seems very cumbersome to do so... Any better way?


Thanks!


Jörg

[Lightpicture]

Hello Jörg,

You mean activate and deactivate a switch, for example?
That you don't see it in the visualisation?

You can deactivate a switch in the visualisation with the expert adjustment, but only deactivate!
To activate the switch again, it's only possible in the Loxone config.

[J V]

Thank you for the reply...

Not exactly what I mean... I mean, if a switch is for some reason not functional, is there a way of blocking or hiding it in the app? A bit like a child lock, a way to say in the visualisation that a switch is not usable at this time or prevent the switch from being used.

Jörg

[Lightpicture]

Your welcome.

There is no possiblity to block or hide a switch, with some logic in the software. (Only Loxone knows why it's not possible. 😉)
Only a workaround.
You set R=1 on a switch, then you have no functionality any more in the visualization.

I hope I understood you well.

[Giovani]

I have simmilar requirement: eg to hide/disable particular control if it is unusable due to current state of process - eg: user have possibility to do manual setting of level only if process is in manual mode, otherwise setting of level shall be disabled.

I have additional question: when user change from automatic to manual operation I would like to set value of Virtual input block (to set target level for manual operation) to have same value as current value of parameter which was previously controlled automatically.

[J V]

There is no possiblity to block or hide a switch, with some logic in the software. (Only Loxone knows why it's not possible. 😉)
Only a workaround.
You set R=1 on a switch, then you have no functionality any more in the visualization.

I hope I understood you well.

I will have to try that...
So you mean that as long a R=1, the visual block is "blocked"? Or it still reacts visually but just does not send out a pulse?

One problem may be that setting R on some blocks has an effect: on a radio button, on an EIB switch, it alters the output... but that may not be such a big issue (if the button should be disabled because its functionality would not work anyway, then a change of output should also not be an issue...)

[Lightpicture]

Exactly.
It reacts in the visualisation, but no output signal. (I only use a switch.)

That's the problem, the workaround works not for all switches.
Actually, I'm using 11.2.10.19 (Beta), but I've been using this functionality for a long time.

For me, the perfect way would be to set/unset the activation 1 for hide and visible a switch, etc with a logic.

Florian
I hope that's possible and Loxone will implement this in one of the next Config versions.
Thank you.

[J V]

Thanks for the clarification.
The issue then still stands: the button visually would change its position in the app, giving the impression that the control works.

Probably to avoid that I would have to distinguish between the controls that are visible in the app and the controls that steer devices. For example, I could put a virtual input (as a pushbutton with state visible), and do not allow it to change state if the control should be inactive. The VI would then connect to the button it should control (and this button could be locked with the childlock as present in Loxone config. Similarly, I could put a radiobutton in which the all-off state is used as visualisation for "disabled", and revert it back to that if the underlying control should be disabled. Just seems a lot of work for something that seems quite straight forward....

It would indeed be nice if there would be a way of blocking or even hiding a control based on an input.


Jörg