[bug] v1.1.0 does not include upstream fixes for zwave-js, despite changelog #511
Closed
1 of 3 tasks
Labels
bug
Something isn't working
Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report
Version
Build/Run method
zwavejs2mqtt version: 1.1.0
zwavejs version: 6.1.3 (see context section)
Describe the bug
I downloaded the latest zwavejs2mqtt release (v1.1.0) so that I could test an upstream bugfix in zwave-js (link). As the v1.1.0 patch notes mention that zwave-js 6.1.3 is included, the fix should be there.
Unfortunately, it is not; when trying to update the LED parameter on the switches, it reverts to the previous value, just as it did before the fix made for zwave-js.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The submitted value should be accepted. Last week I tried deploying zwavejs2mqtt via NodeJS with a manual patch to
@zwave-js
in thenode_modules
to fix the configuration parameter, and it did work then.Additional context
The dependabot PR for the zwave-js 6.1.3 update did get merged for v1.1.0, and this can be seen in the
package.json
(permalink). However in thepackage-lock.json
we can see that@zwave-js/core
is still 6.1.1 (permalink).I haven't tried building it locally from source and forcing an update to the package lock file so I don't know for sure if this is the cause, but it is odd!
The text was updated successfully, but these errors were encountered: