Chunk Watch

In chunk modules, the chunk name is case sensitive. This means that MYCHUNK is not equivalent to mychunk or MyChunk.

In chunk modules, the item names are case sensitive. This means that item1 is not equivalent to Item1 or ITEM1.
To avoid mismatch between names and RegEx ^, ., $, *, +, ?, (, ), [, ], {, }, \, | are not allowed in the names.

can be a RegEx (Regular Expression)
see regular expression.

• ^a.* match any string starting by "a"
• (?i)^a match any string starting by "a" or "A" (case insensitive)
• .*a$ match any string ending by "a"
• .*\d$ match any string ending by a number "1","2","3", etc.
• .at matches any three-character string ending with "at", including "hat", "cat", "bat", "4at", "#at" and " at" (starting with a space).
• [hc]at matches "hat" and "cat".
• [^b]at matches all strings matched by .at except "bat".
• [^hc]at matches all strings matched by .at other than "hat" and "cat".
• ^[hc]at matches "hat" and "cat", but only at the beginning of the string or line.
• [hc]at$ matches "hat" and "cat", but only at the end of the string or line.
• \[.\] matches any single character surrounded by "[" and "]" since the brackets are escaped, for example: "[a]", "[b]", "[7]", "[@]", "[]]", and "[ ]" (bracket space bracket).
• s.* matches s followed by zero or more characters, for example: "s", "saw", "seed", "s3w96.7", and "s6#h%(>>>m n mQ".
• [hc]?at matches "at", "hat", and "cat".
• [hc]*at matches "at", "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on.
• [hc]+at matches "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on, but not "at".
• cat|dog matches "cat" or "dog".
• \\ to search the \ char (backslash)

Empty item names watches the entire chunk When item names is left empty, the module fires the trigger whenever any item in the chunk is modified. This can cause excessive triggering in chunks with many frequently updated items. Set specific item names to filter.

Trigger fires on every write, not only on value change The trigger fires every time a write operation is performed on the chunk item, even if the new value is identical to the old one. If you need to react only to actual value changes, compare the new value against the previous one downstream.

Non-existent chunk: no trigger, no error If the chunk name refers to a chunk that does not exist yet, the module waits silently — no trigger fires, no error is raised. The trigger will start firing once the chunk is created and modified. Enable display errors to be notified.