A bug in the tracking of watches may cause multiple watch requests for the same device/service/variable, which results in multiple watch triggers when the variable changes. While Reactor already "debounces" these requests, it makes for odd runs of messages in the event log (which logs the pre-debounce callbacks). Otherwise it's harmless.
toggledbits
commented
5 years ago
A bug in the tracking of watches may cause multiple watch requests for the same device/service/variable, which results in multiple watch triggers when the variable changes. While Reactor already "debounces" these requests, it makes for odd runs of messages in the event log (which logs the pre-debounce callbacks). Otherwise it's harmless.