# `Grizzly.ZWave.Commands.S2ResynchronizationEvent`
[🔗](https://github.com/smartrent/grizzly/blob/v9.1.4/lib/grizzly/zwave/commands/s2_resynchronization_event.ex#L1)

S2 Resynchronization Event

This event is defined in zipgateway, but doesn't seem to be officially
documented yet. From zipgateway:

```
SOS_EVENT_REASON_UNANSWERED means that a Nonce Report with Singlecast-out-of-Sync
(SOS) = 1 has been received at an unexpected time and no response was sent.

A Nonce Report SOS is considered expected and no SOS_EVENT_REASON_UNANSWERED will be emitted in these case:
  1) libs2 is in Verify Delivery state and receives a Nonce Report SOS from the
     node being delivered to and will re-transmit the encrypted message
  2) libs2 has already re-transmitted and receives a second SOS from the node being transmitted to
     during Verify Delivery timeout. A 
ef S2_send_done_event() with
     status=TRANSMIT_COMPLETE_NO_ACK will be emitted instead.
```

Params:

  * `:node_id` - which node this message pertains to
  * `:reason` - 0 = SOS_EVENT_REASON_UNANSWERED in zipgateway

---

*Consult [api-reference.md](api-reference.md) for complete listing*