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

Controller Becomes Unresponsive After Setting New Config Value For Battery Device #6952

Closed
6 of 7 tasks
AlCalzone opened this issue Jun 22, 2024 Discussed in #6951 · 0 comments · Fixed by #6953
Closed
6 of 7 tasks

Controller Becomes Unresponsive After Setting New Config Value For Battery Device #6952

AlCalzone opened this issue Jun 22, 2024 Discussed in #6951 · 0 comments · Fixed by #6953
Labels
bug Something isn't working

Comments

@AlCalzone
Copy link
Member

Discussed in #6951

Originally posted by @ADHDSquir June 22, 2024

Checklist

  • I have read and followed the above instructions

  • I have checked the troubleshooting section and my problem is not described there.

  • I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?
When setting a new configuration value for a battery-powered device, the value is not set and the controller becomes unresponsive to any other commands for any other devices.

What did you expect to happen instead?
The network should continue to function while waiting for a battery powered device to wake up.

Steps to reproduce the behavior:

  1. Select a battery powered device
  2. Change a Configuration value and click the send arrow
  3. The spinning circle says to "wake up your device in order to send commands"
  4. Waking the device doesn't cause the commands to send
  5. No command can be sent to any other device on the network until Z-Wave JS is restarted

Anything else we should know?

Software versions

Driver (node-zwave-js): 12.11.1

Z-Wave JS UI: 9.14.1.7018936

Device information

Manufacturer: Zooz
Model name: ZSE11 Q Sensor
Node ID: 58

Checklist

  • I made sure to provide a driver log on level debug.

  • The log includes a re-interview of the problematic device (if applicable).

  • The log includes the problematic interaction with the device (if applicable).

  • I provided the node ID of the problematic device (if applicable).

Upload Logfile

zwavejs_current.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant