You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not using HomeAssistant. Or: a developer has told me to come here.
I have checked the troubleshooting section and my problem is not described there.
I have read the changelog problem was not mentioned there.
Build/Run method
Docker
PKG
Snap package
Manually built (git clone - npm install - npm run build )
zwavejs2mqtt: 3.2.0
zwave-js: 7.1.1
Describe the bug
I tried to click on Stop exclusion when the counting down stuck on 0 s. But after that the whole daemon disappeared:
2021-04-10 13:23:37.545 INFO ZWAVE: Calling api startExclusion with args: [ [length]: 0 ]
2021-04-10 13:23:37.558 INFO ZWAVE: Controller status: Exclusion started
2021-04-10 13:23:37.559 INFO ZWAVE: Success zwave api call startExclusion { success: true, message: 'Success zwave api call', result: true }
TypeError: this.stopExclusion.catch is not a function
at Timeout._onTimeout (/usr/src/app/lib/ZwaveClient.js:2283:37)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7)
To Reproduce
Steps to reproduce the behavior:
Start excluding a node
Wait for timeout
The exclusion will not stop properly, because the counter stuck on 0s
Try to close that with Stop button
And you get this error message
Expected behavior
The counting down stops properly
The Stop button doesn't kill the daemon with a type error
Additional context
In general, I use HA, but when I add/remove node I always turn off that to avoid unwanted states/nodes... e.g. when I add a new node, I always rename that, but the HA remembers the original ids...
Version
Checklist:
Build/Run method
zwavejs2mqtt: 3.2.0
zwave-js: 7.1.1
Describe the bug
I tried to click on Stop exclusion when the counting down stuck on 0 s. But after that the whole daemon disappeared:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Additional context
In general, I use HA, but when I add/remove node I always turn off that to avoid unwanted states/nodes... e.g. when I add a new node, I always rename that, but the HA remembers the original ids...
zwavejs_1.log
Update1
You should not do magic for reproduction:
I bisected the bug and the zwavejs2mqtt: 3.0.3, zwave-js: 7.0.1 was the first bad version.
The text was updated successfully, but these errors were encountered: