Updated Zigbee2mqtt in proxmox now fails to start

Hey Everyone,

So my config is HAOS, MQTT and Zigbee2mqtt all running as separate containers in ProxMox using a conbeeii stick.

So I had just bought some new Inspelning sockets from Ikea in the UK.

I added the devices into z2m fine but noticed that they were showing as unsupported devices though they still worked.
A quick read through and it turns out my z2m install was a little old so I opened up the container and ran the update.sh
A quick peek back at the GUI and the the devices showed the correct icons, I clicked on one to see what other options had changed and the web interface failed to load.

Taking another look at Proxmox and I thought I’d give the entire thing a restart to make sure that everything else was ok and it turns out it wasn’t

I tried an npm start in the z2m folder and it spat out this error

> [email protected] start
> node index.js

Starting Zigbee2MQTT without watchdog.
[2024-10-26 22:26:03] info:     z2m: Logging to console, file (filename: log.log)
[2024-10-26 22:26:03] info:     z2m: Starting Zigbee2MQTT version 1.40.2 (commit #e06848d)
[2024-10-26 22:26:03] info:     z2m: Starting zigbee-herdsman (2.1.3)
[2024-10-26 22:26:04] info:     zh:zstack:znp: Opening SerialPort with {"path":"/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2414869-if00","baudRate":115200,"rtscts":false,"autoOpen":false}
[2024-10-26 22:26:04] info:     zh:zstack:znp: Serialport opened
[2024-10-26 22:26:04] info:     zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2024-10-26 22:26:05] info:     zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2024-10-26 22:26:05] error:    z2m: Error while starting zigbee-herdsman
[2024-10-26 22:26:05] error:    z2m: Failed to start zigbee
[2024-10-26 22:26:05] error:    z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-10-26 22:26:05] error:    z2m: Exiting...
[2024-10-26 22:26:05] error:    z2m: Error: Error: Broken pipe, cannot set

/opt/zigbee2mqtt/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264
  var er = new ERR_STREAM_WRITE_AFTER_END();
           ^
Error: write after end
    at writeAfterEnd (/opt/zigbee2mqtt/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:264:12)
    at DerivedLogger.Writable.write (/opt/zigbee2mqtt/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:300:21)
    at DerivedLogger.log (/opt/zigbee2mqtt/node_modules/winston/lib/winston/logger.js:231:12)
    at Logger.log (/opt/zigbee2mqtt/lib/util/logger.ts:198:25)
    at Logger.info (/opt/zigbee2mqtt/lib/util/logger.ts:211:14)
    at Znp.onPortClose (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:96:16)
    at Object.onceWrapper (node:events:633:26)
    at SerialPort.emit (node:events:530:35)
    at port.close.then.closing (/opt/zigbee2mqtt/node_modules/@serialport/stream/dist/index.js:242:18)

My config currently looks like this

frontend:
  port: 3232
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://<IP_Address>:1883
  user: <username>
  password: <password>
  keepalive: 60
  reject_unauthorized: true
  version: 4
serial:
  port: /dev/ttyACM0
#port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2414869-if00
  adaptor: deconz
advanced:
  pan_id: 4327
  network_key:
    - 241
    - 125
    - 30
    - 160
    - 198
    - 233
    - 192
    - 13
    - 24
    - 121
    - 222
    - 106
    - 10
    - 156
    - 72
    - 37
  channel: 20
devices:
  '0x00158d0004a02612':
    friendly_name: Front Door
    icon: >-
      data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAgAAAAIACAYAAAD0eNT6AAAABGdBTUEAALGPC/xhBQAAACBjSFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3Ccul>158d0006c49dec':
friendly_name: Sunroom Motion
   homeassistant:
      name: Sunroom Motion
    optimistic: true
    icon: >-
      data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAgAAAAIACAYAAAD0eNT6AAABHGlDQ1BpY2MAACiRY2BgMnB0cXJlEmBgyM0rKQpyd1KIiIxSYD/PwMbAzAAGicnFBY4BAT4gdl5+XioDBvh2jYERRF>
  '0x04cd15fffe83f3fb':
    friendly_name: Toggle Switch
    icon: >-
      data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAJYAAACWCAQAAACWCLlpAAAABGdBTUEAALGPC/xhBQAAACBjSFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAAAmJLR0QA/4>
  '0x540f57fffe3c663c':
    friendly_name: Strybar
    homeassistant:
      name: Strybar
    optimistic: true
    icon: >-
      data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAJYAAACWCAYAAAA8AXHiAAAABGdBTUEAALGPC/xhBQAAACBjSFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAABmJLR0QA/w>
  '0xec1bbdfffe8d313c':
    friendly_name: Silvercrest
    homeassistant:
      name: Bens PC
    optimistic: true
    icon: >-
      data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAJYAAACWCAYAAAA8AXHiAAAABGdBTUEAALGPC/xhBQAAACBjSFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAABmJLR0QA/w>
  '0x7cc6b6fffe13e435':
    friendly_name: Inside Porch
    icon: >-
      data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAJYAAACWCAYAAAA8AXHiAAAABGdBTUEAALGPC/xhBQAAACBjSFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAABmJLR0QA/w>
  '0xb0c7defffe979a6b':
    friendly_name: Master Bedroom - LT
  '0x90ab96fffe43cf81':
    friendly_name: Porch Steps
  '0x3410f4fffeeefc04':
    friendly_name: Porch Far
  '0x7cc6b6fffe5f8069':
    friendly_name: Porch Mid
  '0xa46dd4fffe5c1d0d':
    friendly_name: Porch Near
  '0xf84477fffef87bbd':
    friendly_name: Ben's Computer
  '0xf84477fffeea127a':
    friendly_name: Matthews Computer
  '0x6cfd22fffe0e99c2':
    friendly_name: Danny's Computer
  '0xf84477fffef7ece4':
    friendly_name: Andrews Computer

The hashed out port line, I’ve only added that here for completeness as I’ve also tried that as my config as well.

In the proxmox container the conbee shows up as this

lrwxrwxrwx 1 root root 13 Oct 26 21:46 usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2414869-if00 -> ../../ttyACM0

If someone has had this issue before and resolved it I’d love to know what the solution is as at the minute my WiP dashboard is looking a little poorly.

Thanks everyone.

1 Like

I am having the same exact issue and a very similar setup, using Proxmox.

I added a comment to an issue in Zigbee2MQTT, but since this started happening about the same time as you wrote the post here, I am assuming it might have something to do with Proxmox or a specific update we both received recently to our software…

Sorry too hear you’ve had a similar issue.

I was left with a pretty dead system and couldn’t figure it out after following many guide and threads I’ve had to give up on z2m which was a shame because the information that was available when it was running was tremendous.

Sadly I’ve had to just scrap it and jump to ZHA.

Which in all fairness is working really well, couple of quirks, Strybar is a piece of crap now but I can live with using other controls.

I hope you find a solution to your issues soon.
WAF is important here so I had to get it working somehow and now it is and everyone is happy.

I have the same problem with a VM in Unraid. Updated the zigbee2mqtt addon yesterday I think. But it was still working after the update. Now the container fails to start with the error you posted above

Am also having the very same problem.

I do have exact the same problem. Fresh and new installation, without any configuration (but currently still in openHAB :face_with_peeking_eye: :grimacing:)