Implementing a set-before-get-behaviour with presets

Zaid Abdulla zaid at
Mon Mar 21 12:47:02 EDT 2016

On Fri, 2016-03-18 at 14:40 +0100, Oliver Kraitschy wrote:
> Why doesn't get the second preset executed?

That's due to caching. It's a limitation in this version and is
unfortunately difficult to fix without introducing undesired side
effects. A quick workaround is to add a "refersh" configuration in your
first preset with interval of 1 second. This will force the cache
duration to not exceed 1 second which should hopefully be enough time
for it to expire within the same session.

> - How are tags supposed to be used in preconditions? Can i use
> several tags in one precondition? Like: Tags =
> "configured,refreshed"? Do i need a separate precondition for each
> tag?

Add multiple tag filters in your precondition, one for each tag.

> - How is weight evaluated and used? Does it determine an order of
> execution or a precedence of execution?

It doesn't determine the ordering, it determines which preset takes
proirity in case of configuration conflicts.

> - If i add a refresh configuration with an interval (age) of 0
> seconds, does that mean it's executed only once?
> - If i don't enter an interval for a refresh configuration, the cwmp
> worker dies.

It means it will be executed infinite number of times :) Value should
be 1+.

> When is a preset executed? After the inform of a device?

Right after inform only when there are no pending tasks in queue.


More information about the Users mailing list