Zigbee2mqtt: 1.5.0 on Raspbian Stretch does not work with WeBee CC2530+CC2591 any more

Created on 15 Jul 2019  路  20Comments  路  Source: Koenkk/zigbee2mqtt

Bug Report

What happened

Updated from v1.4.0 to 1.5.0 via update.sh
"error: Error while starting zigbee-shepherd! (Error: request timeout)"

console output
full log
NPM log

What did you expect to happen

Normal operation like before update.
normal log

How to reproduce it (minimal and precise)

Update from 1.4.0 to 1.5.0 via update.sh or install 1.5.0
cd /opt/zigbee2mqtt && npm start

Debug Info

zigbee2mqtt version: 1.5.0
CC253x firmware version: CC2530_CC2591_DEFAULT_20190608

serial:
  port: /dev/ttyS0
advanced:
  rtscts: true

Hello!

Currently I'm evaluating ZigBee with some Aqara sensors and wall switches on a Raspberry Pi 3B+ (Raspbian Stretch) with the UART connected to a WeBee CC2530+CC2591.
After the update it does not work anymore. Quick switch to an CC2531 USB stick and changing the port setting worked. Reverting to v1.4.0 also restores functionality.
Flashed the WeBee board again, installed zigbee2mqtt from scratch, no change.

Most helpful comment

Should be fixed in latest dev branch (for hassio please wait 2 hours until new image is published).

All 20 comments

Hello,
I have the same issue with a CC2530. I have tested the following firmware versions without success:

  • CC2530_DEFAULT_20190608
  • CC2530_MAX_STABILITY_20190315
  • CC2530_SOURCE_ROUTING_20190619
    Reverting solves the problem immediately

Can you provide the logs when running with DEBUG=* npm start on v1.4.0 AND v1.5.0?

Same problem here as mentioned in #1728 . I could try to provide logs today at home, if you would please explain where to set DEBUG= at HassIO. Maybe @TLBM is faster though

@holgerebert I don't see debug logging, can you try running with sudo DEBUG=* npm start instead of DEBUG=* sudo npm start. Also in your 1.5.0 log it shows cannot lock port, which is a different issue as the OP has.

@Koenkk sorry, here are the full logs. I have only seen the some of the log entries above and they are identical to me

log from 1.4.0

log from 1.5.0

I've probably found the issue, will try to publish a fix tonight.

Nice - Thank you!

Should be fixed in latest dev branch (for hassio please wait 2 hours until new image is published).

I can confirm the fix is working using the arm32v6-dev Docker image.

Just tried it and it worked four times in a row and also after a reboot.
Thank you for this great and fast service and this whole project!

Is there a forum for generic questions which are not bug related?

Have a nice evening!

Works fine here. CC2530 still works after restart of zigbee2mqtt. Looks fine. Hass.IO 0.96B2

@tlbm http://zigbee2mqtt.discourse.group/

I will release 1.5.1 with this fix asap.

works for me too. Thank you!

1.5.1 released, @danielwelch can you update the hassio image?

There is no (hassio) update yet. Pretty anoying when your entire zigbee network is down.

Any way to do this manually on hassio?

You can use edge for the time being.

Thanks. I'm afraid that didn't fix it. I'm on Hassio 0.96.2 in docker on Ubuntu 18.04.
The problem started right after the update to 0.96.2. I did not make any configuration changes.

Logs:

[Info] Configuration file found: /share/zigbee2mqtt/configuration.yaml
[Info] Configuration written to /share/zigbee2mqtt/configuration.yaml
2019-07-20T23:26:28: PM2 log: Launching in no daemon mode
2019-07-20T23:26:29: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T23:26:29: PM2 log: App [npm:0] online
> [email protected] start /app
> node index.js
  zigbee2mqtt:info 7/20/2019, 11:26:32 PM Logging to directory: '/share/zigbee2mqtt/log/2019-07-20.23-26-31'
  zigbee2mqtt:info 7/20/2019, 11:26:32 PM Starting zigbee2mqtt version 1.5.1 (commit #unknown)
  zigbee2mqtt:info 7/20/2019, 11:26:32 PM Starting zigbee-shepherd
  zigbee2mqtt:info 7/20/2019, 11:26:39 PM Error while starting zigbee-shepherd, attempting to fix... (takes 60 seconds) (Error: request timeout)
  zigbee2mqtt:info 7/20/2019, 11:27:39 PM Starting zigbee-shepherd
  zigbee2mqtt:error 7/20/2019, 11:27:46 PM Error while starting zigbee-shepherd! (Error: request timeout)
  zigbee2mqtt:error 7/20/2019, 11:27:46 PM Press the reset button on the stick (the one closest to the USB) and start again
  zigbee2mqtt:error 7/20/2019, 11:27:46 PM Failed to start
    {"message":"request timeout","stack":"Error: request timeout\n    at CcZnp.<anonymous> (/app/node_modules/zigbee-herdsman/dist/cc-znp/index.js:208:22)\n    at Object.onceWrapper (events.js:286:20)\n    at CcZnp.emit (events.js:198:13)\n    at Timeout.<anonymous> (/app/node_modules/zigbee-herdsman/dist/cc-znp/index.js:192:18)\n    at ontimeout (timers.js:436:11)\n    at tryOnTimeout (timers.js:300:5)\n    at listOnTimeout (timers.js:263:5)\n    at Timer.processTimers (timers.js:223:10)"}
  zigbee2mqtt:error 7/20/2019, 11:27:46 PM Exiting...
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/2019-07-20T21_27_46_483Z-debug.log
2019-07-20T23:27:49: PM2 log: App [npm:0] exited with code [1] via signal [SIGINT]
2019-07-20T23:27:49: PM2 log: App [npm:0] starting in -fork mode-
2019-07-20T23:27:49: PM2 log: App [npm:0] online

Is this the same issue, or do I need to file a new bug?

Does anyone know why in the config when i put "experimental": {"livolo" :true} when i i save it ,removes the lines entirely?

Was this page helpful?
0 / 5 - 0 ratings