[TRIGGER] Fix ZeroTier Online/Offline Trigger

The current ZeroTier trigger for node online/offline is using the unique dedupe parameter.

The issue with this is that it checks for unique values across the entire object. If another value like clock or ipAssignments change it will trigger the event again.

For these two triggers, it needs to be updated to only check if the online (boolean) state has changed - and ignore all the other keys.

[zalmanlew]

@luancazarine while that is true, I think that’s why it depends how frequently you poll the data.

It’s worth noting that ZeroTier considers the machine online if lastOnline is in the last 3 minutes. We can include this information in the description of the source.

[zalmanlew]

@luancazarine that’s because you have your node offline, I guess his is primarily an issue in reverse (as long as your node is online, the lastOnline will constantly be updated with the ping time).

If it’s going from offline > online then lastOnline wouldn’t update, however other fields can be updated (manually) and this shouldn’t fire the online event. Only the change of the online state should emit that event.