Does enabling "Display Current Values" impact load on the device all of the time...or only when you are viewing the rule?
Is there any reason at all to disable it?
I always assumed disabling current values was used for when it might cause confusion while reading through the workflow. Nothing more than that, as it doesn't apply to the execution.
IMHO it makes conditions in the rule much easier to read and isn't much help unless you have trouble doing the simplest Boolean operations in your head (e..g., true or false = true). That's just my take. 
But it can be helpful to keep enabled since it also puts the same information in logs if you have action logging enabled, and then you'll see the current device state, which can be helpful in cases where you think something like the wrong half of an IF/ELSE executed (or really the "right" half did and this tells you why).
I think the option was put in a while back because for extremely log rules, fetching all the relevant states from the devices could slow down page loading for some people in certain cases. In regular use, the difference shouldn't really matter.
1 Like
I am kind of fine either way.
But if it adds to logging it's seems better to leave it off until you need to figure something out?
By that point it's usually too late to turn it back on. 
It also doesn't "add" much to logging, just a few additional characters for each condition (and expression). The bulk of it would be action logging, which is certainly a choice you can make to leave on or off, and you may choose to leave it off unless you're troubleshooting. But if it's off, the above, of course, doesn't matter at all in this context.
I get the too late issue...but if it's not repeatable there are other issues. I'm just all about making it as easy as possible on the hub. Even if it's minor.
So, it adds to the logging overhead. Is that it? Are rules that it's turn on updating those fields in the background or does that just happen if the rule is displayed / being edited?
Yes, only then -- nothing in "the background" (there is no "background" per se).
The computational impact of Display Current Values is minimal, not something that's going to make any difference to the hub. Logs are the same, they don't really contribute a significant load to the hub. Consider that if Display Current Values were to make any difference, the hub would already have to be pretty much on its knees from something far more taxing.
2 Likes
Thanks...exactly the answer I was looking for!
No.
A very little bit; Nothing to think about.
IMHO the Current Values make the code less readable.
So I usually have disabled Display Current Values.
Only in case of debugging I enable Display Current Values.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
