node-zwave-js: Z-wave JS exits with RangeError [ERR_INVALID_BUFFER_SIZE]: Buffer size must be a multiple of 16-bits

Describe the bug

A clear and concise description of what the bug is. Describe what causes the bug, what you observe, and what happens as a result.

Once the docker container starts, it begins to query devices for approximately 10 minutes. Then it exits with the error : RangeError [ERR_INVALID_BUFFER_SIZE]: Buffer size must be a multiple of 16-bits. It then exits and stops the container. Running on Ubuntu VM (ESXI). Clean install as well as using the Home Assistant integration.

Device information

Which device(s) is/are affected (make/model)?

  • Aeotec Gen 5 USB (Z-Stick)

What are the node IDs?

N/A. The container is stopped before it finishes interrogating all devices (approx 40 zwave devices)

Last Known Working Configuration

  • New device

  • Previously working device (node-zwave-js)

    • Which library version/docker image/adapter version?
    • Have you made any recent configuration changes to the device? Describe.
  • Previously working device (other platform)

    • Which platform? Currently working fine with Homeassistant Zwave 1.4 integration. All node devices working correctly.
    • Have you made any recent configuration changes to the device?

Installation information How did you install node-zwave-js?

  • zwavejs2mqtt (latest) docker image
  • zwavejs2mqtt (dev) docker image
  • ioBroker.zwave2 adapter
  • Pkg
  • Manual Docker build
    • node-zwave-js branch:
    • zwavejs2mqtt branch:
  • Manually built (as described in the docs)
  • Other:

To Reproduce N/A Steps to reproduce the behavior:

  1. Go to ‘…’
  2. Click on ‘…’
  3. Scroll down to ‘…’
  4. See error

Additional context Add any other context about the problem here.

Logfile:

zwaveJS.docx

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 30 (13 by maintainers)

Most upvoted comments

Hemmm I have no idea why you get that error… If that would be really like that my mailbox would be filled by bug like that. I suggest you to remove all your local images of zwavejs2mqtt and try to pull a new one to be sure you are using the correct one

Yes, that occurred to me too! I built a new VM just to be sure and spun up the new docker. It’s been running for the last 20 minutes with no issues whatsoever, found all my devices and is looking great so far! I’ve attached my logs for your reference in case you need them. Let me know if you need anything else.

I really appreciate your kind help. I’m not sure when the home assistant integration will receive this update, but it looks brilliant so far.

Thanks again, @AlCalzone!

zwavejs2mqtt.log zwavejs_1.log

Sorry i forgot to also thank you, @robertsLando. Many apologies and thank you very much also!

Thank you @AlCalzone. I will reinstall and get you the logs.