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

fix(config): correct reporting frequency parameter values for Sensative AB Strips Comfort / Drips Multisensor #6171

Merged
merged 1 commit into from
Aug 16, 2023
Merged

fix(config): correct reporting frequency parameter values for Sensative AB Strips Comfort / Drips Multisensor #6171

merged 1 commit into from
Aug 16, 2023

Conversation

anon1838
Copy link
Contributor

The Sensative Strips Comfort has incorrect parameters stored in the device configuration. This PR changes the parameters to match the manual.

I have two of these devices, and have manually set one of them to frequent reporting, value 2. The result is as expected; the frequently reporting one reports more often as described in https://sensative.com/strips-comfort-reporting/

The default value for this option is Normal (1) and does not need changing.

Fix Sensative AB / Strips Comfort/Drips Multisensor reporting frequency parameters
@zwave-js-assistant zwave-js-assistant bot added the config ⚙ Configuration issues or updates label Aug 16, 2023
@anon1838 anon1838 changed the title Fix Sensative AB / Strips Comfort/Drips Multisensor reporting frequency parameters fix(config): Change Sensative AB / Strips Comfort/Drips Multisensor reporting frequency parameters to correct values Aug 16, 2023
@anon1838 anon1838 changed the title fix(config): Change Sensative AB / Strips Comfort/Drips Multisensor reporting frequency parameters to correct values fix(config): Correct reporting frequency parameter values for Sensative AB / Strips Comfort/Drips Multisensor Aug 16, 2023
@anon1838 anon1838 changed the title fix(config): Correct reporting frequency parameter values for Sensative AB / Strips Comfort/Drips Multisensor fix(config): correct reporting frequency parameter values for Sensative AB / Strips Comfort/Drips Multisensor Aug 16, 2023
@AlCalzone AlCalzone changed the title fix(config): correct reporting frequency parameter values for Sensative AB / Strips Comfort/Drips Multisensor fix(config): correct reporting frequency parameter values for Sensative AB Strips Comfort / Drips Multisensor Aug 16, 2023
@AlCalzone AlCalzone merged commit 6cce73e into zwave-js:master Aug 16, 2023
AlCalzone added a commit that referenced this pull request Aug 16, 2023
### Features
* When the controller cannot transmit due to being jammed, this is now detected and exposed to applications. In this situation, nodes are no longer being marked as dead. (#6174)
* A hash of the device config used during the interview is now stored and can be used to detect whether a node needs to be re-interviewed after a configuration update (#6170)

### Bugfixes
* Fixed an issue where 700 series controllers were not soft-reset after NVM backup when soft-reset was disabled via config (#6176)

### Config file changes
* Correct reporting frequency parameter values for Sensative AB Strips Comfort / Drips Multisensor (#6171)

### Changes under the hood
* Config file checks now detect invalid firmware version ranges where `min > max` (#6169)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config ⚙ Configuration issues or updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants