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: add method to return Zniffer capture as Buffer #6836

Merged
merged 3 commits into from
May 15, 2024

Conversation

raman325
Copy link
Contributor

If we want to support Zniffer's in the server, we need the Buffer for the capture instead of outputting to a file. This enables that to occur

AlCalzone
AlCalzone previously approved these changes May 15, 2024
Copy link
Member

@AlCalzone AlCalzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I changed the method name to be a bit more obvious.

@AlCalzone
Copy link
Member

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) May 15, 2024 07:25
@zwave-js-bot zwave-js-bot merged commit 43c4299 into zwave-js:master May 15, 2024
15 checks passed
@raman325 raman325 deleted the capture branch May 15, 2024 17: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.

3 participants