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 query supported RF regions #6957

Merged
merged 1 commit into from
Jun 24, 2024

Conversation

AlCalzone
Copy link
Member

With the upcoming support for EU Long Range, the list of supported regions can differ between different 700/800 series controllers.

This PR adds a method getSupportedRFRegions, which can be used to dynamically determine which regions to show to a user.

@AlCalzone
Copy link
Member Author

@robertsLando Z-Wave JS UI should use this, like we did with Zniffer.

@AlCalzone
Copy link
Member Author

@zwave-js-bot automerge

@zwave-js-bot zwave-js-bot enabled auto-merge (squash) June 24, 2024 09:39
@zwave-js-bot zwave-js-bot merged commit ba71df5 into master Jun 24, 2024
15 checks passed
@zwave-js-bot zwave-js-bot deleted the get-supported-regions branch June 24, 2024 09:44
AlCalzone added a commit that referenced this pull request Jun 24, 2024
We were informed by Silicon Labs that 700/800 series controllers have a hardware watchdog that can reset the controller when it becomes unresponsive. This feature is now enabled by default in Z-Wave JS and should prevent the controller from hanging indefinitely.

In case this causes new issues, the feature can be disabled by setting the environment variable `ZWAVEJS_DISABLE_WATCHDOG` to any non-empty value, or by setting the driver option `features.watchdog` to `false`.

Please let us know if this actually helps or not.

### Features
* Enable hardware watchdog on 700/800 series controllers (#6954)
* Add method to query supported RF regions (#6957)
* Add notification variable for Door/Window tilt state (#6958)

### Bugfixes
* Fixed an issue where value metadata for unknown notification events with known notification types would only be created if the CC version was exactly 2 (#6959)
@AlCalzone
Copy link
Member Author

I thought we talked about that. Zniffer should definitely have a dynamic frequency selection, because they are totally different for 500 series based Zniffers:
grafik

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.

None yet

3 participants