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(config): update fingerprints for Vesternet devices #6460

Merged
merged 1 commit into from
Oct 24, 2023
Merged

feat(config): update fingerprints for Vesternet devices #6460

merged 1 commit into from
Oct 24, 2023

Conversation

martyn-vesternet
Copy link
Contributor

@martyn-vesternet martyn-vesternet commented Oct 24, 2023

updated firmware version constraints to match newer variants of Vesternet devices.

Updated firmware version constraints to match newer variants of Vesternet devices.
@zwave-js-assistant zwave-js-assistant bot added the config ⚙ Configuration issues or updates label Oct 24, 2023
@martyn-vesternet martyn-vesternet changed the title Update fingerprints for Vesternet devices feat(config): update fingerprints for Vesternet devices Oct 24, 2023
@AlCalzone AlCalzone merged commit 2c2855b into zwave-js:master Oct 24, 2023
14 checks passed
@martyn-vesternet
Copy link
Contributor Author

@AlCalzone I believe these should be in the latest release 12.2.3 but it doesn't look like they've been picked up.

Running HA Supervised docker Z-Wave JS UI version 9.3.0 which also reports Z-Wave JS version 12.2.3. Checking in the file system of the container and the old config files are still present.

DB reports 12.2.3 also but still showing old config files, for example - https://devices.zwave-js.io/?jumpTo=0x0330:0x0200:0xd00f:1.4

That one should now be showing 1.4 - 1.8 for firmware field instead of 1.4 - 1.7

Just wondered if I did something wrong with the commit, or something is amiss somewhere?

@AlCalzone
Copy link
Member

This will be in the next release (probably today). The PR was merged just after the release was cut.

@martyn-vesternet
Copy link
Contributor Author

Apologies, I should have checked the commit order and not just the date!

AlCalzone added a commit that referenced this pull request Oct 31, 2023
### Features
* Allow disabling the unresponsive controller recovery feature (#6480)

### Bugfixes
* Do not abort timed out `Send Data` commands twice (#6484)
* Ensure the default Basic CC values are only exposed if they should be, even with the compat `event` enabled (#6485)
* Auto-remove failed SmartStart nodes when bootstrapping times out (#6483)
* Do not attempt to poll values from nodes that are considered dead (#6470)
* Fixed an issue where the send queue was blocked when recovering controller from missed Send Data callback failed (#6473)
* Instead of restarting the driver, the serial port is now reopened if controller is still missing ACKs after soft-reset (#6477)
* Do not attempt to recover an unresponsive controller before fully initializing (#6480)

### Config file changes
* Tweak Heatit Z-TRM6 options (#6464)
* Add Ring Alarm Panic Button Gen2 (#6453)
* Update fingerprints for Vesternet devices (#6460)

### Changes under the hood
* Added a `mock-server` hook to run code after initializing mocks (#6478)
* Changed the headline in the logs from "ZWAVE-JS" to "Z-WAVE JS" (#6462)
* Lint device config files as part of CI (#6471)
* The `enableSoftReset` driver option is now deprecated in favor of `features.softReset` (#6480)
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.

2 participants