Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: expose captured Zniffer frames, raw data and add method to clear capture #6852

Merged
merged 1 commit into from
May 15, 2024

Conversation

AlCalzone
Copy link
Member

The "frame" and "corrupted frame" events now include the raw frame data (without Zniffer protocol overhead) as their 2nd parameter. Previously captured frames can be read using the capturedFrames property, and cleared using the clearCapturedFrames() method.

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot merged commit 2246fda into master May 15, 2024
15 checks passed
@zwave-js-bot zwave-js-bot deleted the expose-capture branch May 15, 2024 07:20
AlCalzone added a commit that referenced this pull request May 21, 2024
This release contains several bugfixes and improvements for Zniffer, as well as fixing some deviations from the Z-Wave specification.

### Features
* Zniffer: Expose raw capture data in emitted frames (#6852)
* Zniffer: Expose previously captured frames using `capturedFrames` property and `clearCapturedFrames()` method (#6852)
* Zniffer: Add method to return saved capture file as Buffer (#6836)
* Zniffer: Add a special frame type to distinguish Broadcast frames from singlecast frames without having to inspect the node ID (#6863)
* Zniffer: Add an optional parameter for `znifferProtocolDataRateToString` to omit the protocol name (#6863)
* Zniffer: Add an option to limit the number of captured frames kept in memory (#6863)

### Bugfixes
* Always query Basic CC version as part of the interview
* Do not report `Z-Wave Protocol CC` and `Z-Wave Long Range CC` as supported
* Encode CCs using the version implemented by Z-Wave JS, not the target's version
* Abort S2 bootstrapping when first `KEXReport` incorrectly has echo flag set
* Correct NIF contents, distinguish between securely and insecurely supported commands
* Respond to `ManufacturerSpecificCCGet`
* Correct parsing of auto-channel capabilities in `GetLongRangeChannelResponse` (#6850)
* Include LR node information in NVM conversion (#6846)
* Zniffer: Expose `rssi` field in all `Frame` types (#6851)
* Zniffer: Expose payload in ExplorerInclusionRequest frame

### Changes under the hood
* Docs: add link to Zooz 800 series firmware upgrade (#6856, #6862)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants