Events are sent for characteristics that have not changed

[bdraco]

When client_update_value or set_value is called an event is generated even when the internal state hasn't changed. For cameras motion sensors this can result in 100x of events per hour per camera

[bdraco]

This is actually worse than I first thought, because it triggers the home hub to take another snapshot which ties up the camera connection even if its just the continuation of the same motion activation with new details.