Sonoff zigbee 3.0 issues with lxc proxmox

[guarddog13]

Describe the issue
I have HAos on Proxmox as a VM running ZHA with the conbee 2 as a coordinator. I wanted to switch to zigbee2mqtt so I purchased a Sonoff 3.0 hoping to make the switch seamlessly. I flashed the dongle and installed zigbee2mqtt. I was able to get the dongle to be recognized once by zigbee2mqtt and when I exited the shell and restarted the zigbee2mqtt lxc the dongle wouldn't be recognized. It's still in the lxc if I use ls -l /dev/serial/by-id.

I've several times to reflash the device, restarted a new zigbee2mqtt instance. I tried it on a deconz lxc and still nothing. I'm fairly close to returning it and just resetting everything and using my conbee 2 in zigbee2mqtt as this definitely isn't seamless.

Any ideas or help would be greatly appreciated

Bug reports will be closed after 12 hours of NO activity.

[guarddog13]

Why is it not an "issue?" I've followed all online tutorials and suggestions and am still getting errors when trying npm start.

[tteck]

It's not a script issue, it's a knowledge issue. Here's the place (Discussions) that someone may help.

[jeeftor]

Could not this mean an update to the readme is needed?

[guarddog13]

Any ideas what I'm doing wrong i truly want to use the sonoff on my own zigbee2mqtt. I've had zero issues setting up other LXCs...Zwave2JS was seamless and extremely easy. I've passed GPUs through to LXCs and VMs. I've had no issues passing the conbee to HA or my zwave stick previously. If i run ls -l /dev/serial/by-id the stick shows.. i put it in config... when i run npm i get unable to find serial port can't lock port errors.

The conbee is on HA and zigbee2mqtt to mqtt separate on its own lxc .. so it shouldn't be a zigbee parrell network error. I'm lost and i really want this stick to work for me.

[guarddog13]

I don't have a discord account or any interest in using it. 😕 🤷‍♂️

[tteck]

when i run npm

Out of curiosity, have you checked to make sure it's not already running?

[guarddog13]

I have as that was one of the suggestions I've found. I had it running one time...after I first flashed it with the firmware. I was able to pair one device with it and it was showing in HA. I was working in the promox shell and needed the command line so exited it out i should've just refreshed lol. Its been screwed ever since.

When i tried starting it again I got the zigbee herdsman cant start and cant find/lock the port. I wonder if was running then as I didn't check that during that instance. I've since flashed the device and reloaded the lxc several times over. It gives the same errors each time I try now.

I even tried using it with deconz. The deconz frontend loads but no device. I passed it thru to my ubuntu vm and Ubuntu can see it with lsusb but there's no return there for ls -l /dev/serial/by-id. I tried configuration with /dev/usb/004/004 in the VM and it obviously didn't like that.

[tteck]

Shutdown Z2M and delete coordinator_backup.json from the data folder and start everything back up

[guarddog13]

Even with fresh installs of zigbee2mqtt? I'll give it a try either way once I'm back near my machine.

[dimatx]

I wanted to switch to zigbee2mqtt so I purchased a Sonoff 3.0 hoping to make the switch seamlessly.

Perhaps you know, but just FYI - Conbee II works perfectly well with Zigbee2MQTT. If your reason to purchase the Sonoff was just to use Z2M, you may not need it.

[guarddog13]

I love the conbee but had heard the sonoff was better with zigbee2mqtt and that it was easier to switch from ZHA to zigbee2mqtt

[guarddog13]

My goal was to avoid having to reset my entire network before transferring it over. I wish switching Zigbee sticks was as easy as ZWave sticks.

[guarddog13]

Here's my output of ls -l /dev/serial/by-id

root@zigbee2mqtt:/opt/zigbee2mqtt/data/log/2022-09-29.22-11-04# ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 Sep 29 21:58 usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_4e769fae4370ec11a3c9233519c2d21c-if00-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 Sep 29 04:36 usb-Silicon_Labs_Zooz_ZST10_700_Z-Wave_Stick_0001-if00-port0 -> ../../ttyUSB0

My Config.

frontend:
  port: 9442
homeassistant: true
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://192.168.1.174:1883'
  user: hassio
  password: PWD
  keepalive: 60
  reject_unauthorized: true
  version: 4
serial:
  port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_4e769fae4370ec11a3c9233519c2d21c-if00-port0
  #adapter: deconz            #(uncomment for ConBee II)
advanced:
  pan_id: GENERATE
  network_key: GENERATE
  channel: 20

The errors in the logs.

Zigbee2MQTT:info  2022-09-29 22:19:58: Logging to console and directory: '/opt/zigbee2mqtt/data/log/2022-09-29.22-19-58' filename: log.txt
Zigbee2MQTT:info  2022-09-29 22:19:58: Starting Zigbee2MQTT version 1.27.2 (commit #7dc48fb)
Zigbee2MQTT:info  2022-09-29 22:19:58: Starting zigbee-herdsman (0.14.53)
Zigbee2MQTT:error 2022-09-29 22:19:58: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-09-29 22:19:58: Failed to start zigbee
Zigbee2MQTT:error 2022-09-29 22:19:58: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-09-29 22:19:58: Exiting...
Zigbee2MQTT:error 2022-09-29 22:19:58: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_4e769fae4370ec11a3c9233519c2d21c-if00-port0'
    at SerialPort.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:146:28)
    at SerialPort._error (/opt/zigbee2mqtt/node_modules/@serialport/stream/lib/index.js:198:14)
    at /opt/zigbee2mqtt/node_modules/@serialport/stream/lib/index.js:242:12

[guarddog13]

If I run test -w /dev/ttyUSB0 && echo success || echo failure on the zwave stick I get a "success" response. The same on the zigbee stick it responds with a failure.

[guarddog13]

I got it. The stick shows up as /dev/ttyusb1 so in the host lxc config I had to change it from 0 to 1. Seems to be working now.