Why shouldn't I use tag() in an expression

[Felipe_CRM]

Help with Tag Expression

Expression bindings are synchronous. They must return a value when executed. The tag() expression function stalls when first called, waiting for a reply to its subscription request. If you scatter tag() expression functions through a bunch of bindings in a commonly-used view, you will have stalls on those views that are the sum of all the stalls in the bindings. Tag bindings don't stall. They simply don't produce any property assignment at all until the subscription answers, and only produc…

Indirect tag in an expression binding?

There are many other posts like this

Just to get you started down the rabbit hole.

EDIT: Another good reason:

Nesting Not Allowed while using Properties in a Template to turn on a Light

Yes, there is. If the items that comprise your tagpath are updated, even if yielding the same result path, the entire expression containing the tag() function will have to execute. With indirect binding, this doesn't happen. The strings themselves have to be reconstructed every time, even if not changing, slowing down the final expression execution. There are a few cases with computed gateway tags where the tag() expression is the only good way to do indirection, and the dynamic stuff above…