Virtual inputs having their values forgotten?

[Joakim Arfvidsson]

I use virtual inputs for a few house-global settings, like "heating comfort temperature". Also some per-room settings, like "enable motion light".

I don't exactly understand when, but often the values get forgotten when saving a new configuration to the server. There is no "remanence" option for these, just max/min/default and I have "load default on startup" set to FALSE.

What is the expected behavior, or workarounds using some other mechanism?

[Duncan]

all mine seem to keep the previous value after a restart or sending a new configuration (load default set to false as well)

[Joakim Arfvidsson]

I'm on V10 now, but this happened on V9 too, sometimes. Now it seems to happen more often.

On Tue, Oct 16, 2018 at 12:29 PM Duncan <joanne...@gmail.com> wrote:

all mine seem to keep the previous value after a restart or sending a new configuration (load default set to false as well)

--
You received this message because you are subscribed to a topic in the Google Groups "Loxone English" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/loxone-english/lrga-p4j4U4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to loxone-englis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/loxone-english/7996c7e2-c57a-4f47-9751-eee1d033e98b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Duncan]

in my experience, new or changed virtual inputs seem to default to 0 or 'use default at startup' value where as existing ones seem to survive a reboot or adjustment of a config file when they are left alone

this is with 9.3 - i havnt tried 10 in a production environment because it has nothing new to offer me so far.