dgreif/ring v10.0.0 on GitHub

support ring edge camera streaming (b30d99f)
receive dings from push notifications (c9f130f)
homebridge: faster snapshots from camera notifications (7fc821b)
add cocoa_floodlight (c7a7e9c), closes #893
api: simple webrtc session (bac7a49)
api: allow custom peer connections for streaming (3e9e784)
api: convert ding handling to use notifications (5b62318)
api: update notification types (15d3e7e)

homebridge: add name option to schema so that it won't be removed by config-ui (af6755a), closes #870
include device name when setting push token (2466a25), closes #920
npm audit fix (c1fe605)
remove doorbell press simulation options (e1d1225)
update dependencies (4b25595)
cameras: wait to activate session until connected (9a49389)
handle push notification for unknown camera (cc8fc2a)
hide ECONNRESET errors from push receiver (1196d96)
update dependencies (4b97fb3)
update uuid namespace to force new client sessions (bc3e943)
separate streaming setup for ring edge vs regular cameras (6281cf9)
api: allow snapshot to be force-updated based on options (fa0212a)
drop support for node 10 (509d556)
homebridge: increase minimum homebridge version to 1.4.0 (d5be74a)
remove sip calling in favor of live calls (7aeae37)
use Buffer.from (2b28d90)

The sendDoorbellMotionNotificationsToTv and sendCameraMotionNotificationsToTv options have been removed. These options were originally inteded as a workaround for the fact that tvOS would only automatically start streaming for doorbell presses and not for motion events. tvOS 15 now supports this features as an option in the UI, so we no longer need this option at the plugin level.
api: All ding-related functionality will now use the PushNotification type, and the ActiveDing type has been removed
api: The cameraDingsPollingSeconds option has been removed. Ding events will now be received via push notifications (no setup required)
api: The treatKnockAsDing option has been removed. Knocks should now register as "dings" automatically, though I have not been able to test this functionality
ring-client-api only (homebridge not impacted) - All streaming will now be done using the new Ring api via WebRTC + WebSockets. For those using camera.streamVideo, you should not notice any difference. Anyone directly interacting with sip sessions, you will need to migrate to the new LiveCall api. It's fairly similar, and should be more reliable long term. A number of other sip-specific methods have been removed from the RingCamera api as well.
Node 10 is no longer officially supported. It may still work, but could break without warning in the future.
homebridge: The minimum supported homebridge version for this plugin is now 1.4.0