It may be a bug...
But I have witnessed this behavior before and have adjusted some of my own code to deal with it.. Here's an example of it from the Multiplug driver, prior to my change. I was using a 3 second polling interval. You can see it was generating an event for each update and also writing it to the database.
| switch | off | DEVICE | 2019-11-10 12:27:05.117 PM EST | |||
|---|---|---|---|---|---|---|
| switch | off | DEVICE | 2019-11-10 12:27:01.725 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:58.331 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:54.904 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:51.522 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:15.004 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:11.538 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:08.235 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:04.939 PM EST | |||
| switch | off | DEVICE | 2019-11-10 12:26:01.649 PM EST |
