Zigbee2MQTT with zzh! CC2652R Stick not working

jesc · October 13, 2020, 2:52pm

So, I ordered the CC2652 Adapter (Electrolama, zig-a-zig-ah!) on Tindie, but I can’t get it to work with Zigbee2MQTT. I’m switching from a CC2351 adapter.

I burned the firmware (CC26X2R1_20200925.zip: znp_CC26X2R1_LAUNCHXL_tirtos_ccs.hex) as described here:
https://electrolama.com/projects/zig-a-zig-ah/#flash-firmware
That seemd to work fine.

Switching from CC2531, I edited the Pan_Id (increased the decimal number from 6754 to 6755). Sadly, the adapter port is not the same, so I tried /dev/ttyUSB0 (and /dev/ttyAMA0 and also /dev/serial/by-id/usb-1a86_USB2.0-Serial-if00-port0). But I do get some different error message. With USB0 and usb-1a86_USB2.0-Serial-if00-port0 I get:

Zigbee2MQTT:error 2020-10-13 16:43:09: Error: SRSP - SYS - osalNvRead after 6000ms
    at Timeout._onTimeout (/zigbee2mqtt-1.15.0/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm
 ERR!
 [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-10-13T14_43_09_435Z-debug.log

I check Host Messages, and everyhting seems fine:

[10260.551796] usb 1-1.1.3: new full-speed USB device number 6 using dwc_otg
[10260.684919] usb 1-1.1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.63
[10260.692179] usb 1-1.1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[10260.699792] usb 1-1.1.3: Product: USB2.0-Serial
[10260.707389] ch341 1-1.1.3:1.0: ch341-uart converter detected
[10260.719794] usb 1-1.1.3: ch341-uart converter now attached to ttyUSB0

I also tried to install Zigbee Integration. It looks promising (but I needed to tell him in the configuration, that it’s on /dev/ttyUSB0 - but I didn’t need to select wich type, like “ti_cc” (worked automatically, I assume):

I tried to reboot a couple of times and I tried different USB Ports on my rpi3 without changing anything.

I know that I need to re-pair all my zigbee devices.

How do I get Zigbee2MQTT up and running again?

jesc · October 14, 2020, 7:24am

So. I tried some other stuff.

I reflashed the Stick on windows (instead on Linux like the first time)
I added “rtscts: false” to Zigbee2MQTT like it’s recommended here https://electrolama.com/projects/zig-a-zig-ah/#configuration
I used the path “/dev/ttyUSB0”
I tested:

➜  ~ test -w /dev/ttyUSB0 && echo success || echo failure
success
➜  ~

Here is my Configuration:

data_path: /share/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://core-mosquitto'
  user: zigbee2mqtt
  password: password4zigbee2mqtt!
serial:
  port: /dev/ttyUSB0
  disable_led: true
advanced:
  rtscts: false
  availability_timeout: 0
  report: true
  log_level: info
  pan_id: 6756
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 11
    - 12
    - 1
    - 4
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/dev/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  restartdelay: 1
  initialdelay: 1
  options: '-d -d'
  log: false

And here are my Errors:

npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!
 A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-10-14T06_09_50_367Z-debug.log
2020-10-14T08:09:50: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-10-14T08:09:50: PM2 log: App [npm:0] starting in -fork mode-
2020-10-14T08:09:50: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.15.0
> node index.js
Zigbee2MQTT:info  2020-10-14 08:09:56: Logging to console and directory: '/share/zigbee2mqtt/log/2020-10-14.08-09-55' filename: log.txt
Zigbee2MQTT:info  2020-10-14 08:09:57: Starting Zigbee2MQTT version 1.15.0 (commit #1.15.0)
Zigbee2MQTT:info  2020-10-14 08:09:57: Starting zigbee-herdsman...
Zigbee2MQTT:error 2020-10-14 08:10:12: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-10-14 08:10:12: Failed to start zigbee
Zigbee2MQTT:error 2020-10-14 08:10:12: Exiting...
Zigbee2MQTT:error 2020-10-14 08:10:12: Error: SRSP - ZDO - simpleDescReq after 6000ms
    at Timeout._onTimeout (/zigbee2mqtt-1.15.0/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
npm
 ERR! code ELIFECYCLE
npm ERR! errno 1
npm 
ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR!
 This is probably not a problem with npm. There is likely additional logging output above.
npm 
ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-10-14T06_10_12_409Z-debug.log
2020-10-14T08:10:12: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-10-14T08:10:12: PM2 log: App [npm:0] starting in -fork mode-
2020-10-14T08:10:12: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.15.0
> node index.js
Zigbee2MQTT:info  2020-10-14 08:10:17: Logging to console and directory: '/share/zigbee2mqtt/log/2020-10-14.08-10-17' filename: log.txt
Zigbee2MQTT:info  2020-10-14 08:10:19: Starting Zigbee2MQTT version 1.15.0 (commit #1.15.0)
Zigbee2MQTT:info  2020-10-14 08:10:19: Starting zigbee-herdsman...
Zigbee2MQTT:error 2020-10-14 08:10:33: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-10-14 08:10:33: Failed to start zigbee
Zigbee2MQTT:error 2020-10-14 08:10:33: Exiting...
Zigbee2MQTT:error 2020-10-14 08:10:33: Error: SREQ '--> SYS - osalNvItemInit - {"id":33,"offset":0,"osal":true,"product":-1,"value":[173,5,2,51,20,51,0,30,0,0,0,1,5,1,143,0,20,0,2,5,30,0,0,0,11,0,0,0,0,0,0,0,0,0,0,0,100,26,8,0,0,8,0,0,15,15,4,0,1,0,0,0,1,0,0,0,0,167,20,46,102,54,18,135,167,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,15,3,0,1,120,10,1,0,0,0,0,0,0,0],"len":116,"initvalue":[173,5,2,51,20,51,0,30,0,0,0,1,5,1,143,0,20,0,2,5,30,0,0,0,11,0,0,0,0,0,0,0,0,0,0,0,100,26,8,0,0,8,0,0,15,15,4,0,1,0,0,0,1,0,0,0,0,167,20,46,102,54,18,135,167,1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,15,3,0,1,120,10,1,0,0,0,0,0,0,0],"initlen":116}' failed with status '(0x00: SUCCESS)' (expected '(0x09: NV_ITEM_INITIALIZED)')
    at Znp.<anonymous> (/zigbee2mqtt-1.15.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27)
    at Generator.next (<anonymous>)
    at fulfilled (/zigbee2mqtt-1.15.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58)
npm
 
ERR! code ELIFECYCLE
npm ERR! 
errno 1
npm
 ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!
 A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-10-14T06_10_33_824Z-debug.log
2020-10-14T08:10:34: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-10-14T08:10:34: PM2 log: App [npm:0] starting in -fork mode-
2020-10-14T08:10:34: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.15.0
> node index.js
Zigbee2MQTT:info  2020-10-14 08:10:39: Logging to console and directory: '/share/zigbee2mqtt/log/2020-10-14.08-10-39' filename: log.txt
Zigbee2MQTT:info  2020-10-14 08:10:41: Starting Zigbee2MQTT version 1.15.0 (commit #1.15.0)
Zigbee2MQTT:info  2020-10-14 08:10:41: Starting zigbee-herdsman...
Zigbee2MQTT:error 2020-10-14 08:10:55: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-10-14 08:10:55: Failed to start zigbee
Zigbee2MQTT:error 2020-10-14 08:10:55: Exiting...
Zigbee2MQTT:error 2020-10-14 08:10:55: Error: SRSP - SYS - osalNvRead after 6000ms
    at Timeout._onTimeout (/zigbee2mqtt-1.15.0/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:549:17)
    at processTimers (internal/timers.js:492:7)
npm
 ERR! code ELIFECYCLE
npm ERR! errno
 1
npm 
ERR! [email protected] start: `node index.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!
 A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-10-14T06_10_55_637Z-debug.log
2020-10-14T08:10:55: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2020-10-14T08:10:55: PM2 log: App [npm:0] starting in -fork mode-
2020-10-14T08:10:55: PM2 log: App [npm:0] online
> [email protected] start /zigbee2mqtt-1.15.0
> node index.js
Zigbee2MQTT:info  2020-10-14 08:11:01: Logging to console and directory: '/share/zigbee2mqtt/log/2020-10-14.08-11-01' filename: log.txt
Zigbee2MQTT:info  2020-10-14 08:11:03: Starting Zigbee2MQTT version 1.15.0 (commit #1.15.0)
Zigbee2MQTT:info  2020-10-14 08:11:03: Starting zigbee-herdsman...

Any Idea would be appreciated. Also any Idea how to debug this.

Thanks for your help.

Jens

jesc · October 15, 2020, 6:02am

I couldn’t find a solution, but after I upgraded my hardware from a RPi3 to an RPi4, it just worked. Same Configuration (I restored a recent backup), just other hardware. I can’t say, why it didn’t worked. But I check, for example, if there is a possible under-voltage on my RPi3 - but it wasn’t. Also no other obvious problems (high cpu temperature). So, maybe someone in the future could find a solution or my “hardware migration” helped to get around this.

Don_Lim · October 15, 2020, 9:27am

This is exactly what is happening to me on my RPi3. Lucky for me, my new RPi4 is on the way. Luckily I read this else I’ll be working at it all day!

dan123 · October 15, 2020, 10:26am

When I first got my CC2652R I could not get it working. It turned out I had to either press the button on the CC2652R just after plugging it into the USB socket or hold the button when plugging it in (can’t remember which one).

I found the fix referenced elsewhere after a google, I had a quick look just now but cant find it.

May be worth looking into…

jesc · October 15, 2020, 10:53am

Yes, you’re right. I read that, too and tried it. It didn’t work for me. Also, the reference said, it is most probably only on Intel Hardware and not on ARM base Boards like RPi. It was definitely a short press while inserting, because long press would turn it into bootloader mode where you can burn the firmware. I thought I read it on https://electrolama.com/projects/zig-a-zig-ah/ - but I couldn’t find it there either.

JohannCR · March 24, 2021, 11:05pm

Had the same problem, solved by reflashing and reinstalling usb drivers on syno.

jesc · March 25, 2021, 9:23am

Thank you, @JohannCR. In my case probably also reflashing did it. I’m not on a synology (instead I’m on a RPi), but I think, it’s a good advice for people on synology.