CC2531 stops operating

1

Hello, everybody,
I am using zigbee2mqtt V1.14.2 (commit #954b891) on a RaspberryPi 1B, together with a CC2531, latest firmware (20190608) . There are 12 Zigbee devices connected, most of them are IKEA Tradfri bulbs.
Approximatly once a day, the CC2531 stops working. Then I have to plug off the stick and plug in it again. After that I have to restart the zigbee2mqtt service.
I already changed the Raspi, I changed the CC2531, re-flashed it, checked the power supply, nothing helped.
Has anybody an idea what the problem could be and how to solve it?

Thanks
Oli

2

Is the CC2531 directly plugged in the Pi? If so, try using a USB extension cable.

3

Is the CC2531 directly plugged in the Pi?

Yes, it is

If so, try using a USB extension cable.

That sounds weird, but I will try…
What’s the reason for this ?

Thanks
Oli

4

A USB extension cable is not going to make any difference. As USB is not designed to use extension cables (passive male A to female A) at all, and these cables are often of inferior quality, you could in fact end up with a system that is less stable. In a case like this, I rather use a small remote USB hub.

I also suffer from a CC2531 crash about once a day. In this case, pressing the S1 button does not reset the CC2531 (cannot turn off green LED) and you need to unplug and replug it. I have set logging level at debug, and it occasionally shows MEM_ERROR when in this state.

I also suspect that it is no longer operating correctly at that point, and ‘coordinates’ the Zigbee network into a bad state.

I always shut down zigbee2mqtt before power cycling the CC2531, to avoid unplugging it at a critical time (when e.g. the FLASH is written) so it does not end up in a state where it won’t boot anymore.

I have ordered a more powerful stick which I expect will improve things due to much more RAM being available.

5

Using a USB extension cable has helped quite a few Zigbee2MQTT users - particularly those with Raspberry Pi boards. Getting the CC2531 away from all the radio “hash” generated by the computer and away from the computer boards’ built in WiFi + Bluetooth radios sometimes improves performance significantly.

2 Likes
6

I have a Raspi 1B, There is no Wifi or Bluetooth.
The extension cable did not help.

This morning It stops operating again. The following messages are in the log:

Aug 20 07:07:27 zigbee-server npm[10883]: zigbee2mqtt:error 2020-08-20 07:07:27: Publish 'set' 'state' to 'KuechePanels' failed: 'Error: Command 1 genLevelCtrl.moveToLevelWithOnOff({"level":204,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'
Aug 20 07:07:27 zigbee-server npm[10883]: zigbee2mqtt:info  2020-08-20 07:07:27: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'KuechePanels' failed: 'Error: Command 1 genLevelCtrl.moveToLevelWithOnOff({\"level\":204,\"transtime\":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'","meta":{"friendly_name":"KuechePanels"}}'
Aug 20 07:07:33 zigbee-server npm[10883]: zigbee2mqtt:error 2020-08-20 07:07:33: Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({"level":204,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'
Aug 20 07:07:33 zigbee-server npm[10883]: zigbee2mqtt:info  2020-08-20 07:07:33: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({\"level\":204,\"transtime\":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'","meta":{"friendly_name":"KuecheInsel"}}'
Aug 20 07:07:39 zigbee-server npm[10883]: zigbee2mqtt:error 2020-08-20 07:07:39: Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({"level":204,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'
Aug 20 07:07:39 zigbee-server npm[10883]: zigbee2mqtt:info  2020-08-20 07:07:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({\"level\":204,\"transtime\":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'","meta":{"friendly_name":"KuecheInsel"}}'
Aug 20 07:07:45 zigbee-server npm[10883]: (node:10904) UnhandledPromiseRejectionWarning: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms
Aug 20 07:07:45 zigbee-server npm[10883]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 20 07:07:45 zigbee-server npm[10883]:     at ontimeout (timers.js:436:11)
Aug 20 07:07:45 zigbee-server npm[10883]:     at tryOnTimeout (timers.js:300:5)
Aug 20 07:07:45 zigbee-server npm[10883]:     at listOnTimeout (timers.js:263:5)
Aug 20 07:07:45 zigbee-server npm[10883]:     at Timer.processTimers (timers.js:223:10)
Aug 20 07:07:45 zigbee-server npm[10883]: (node:10904) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
7

True and agreed, but it won’t solve the crash problem the OP has.

In the past, I have also suffered from signal integrity issues with passive USB extension cables, to a point where I always use a small USB hub with a micro USB B connector to have a reliable USB logical connection.

8

@OliWee

When the CC2531 has crashed, does pushing S1 help to restore operation ?

Are you using a power supply with sufficient current rating ? As I described earlier, you could also try using a small USB hub that can be externally powered, so that the power to the CC2531 is no longer drawn from the RPi, but rather supplied externally.

The RPi can also present a significant peak load, so beware that just having a working system is no guarantee of a sufficient power supply. It’s also possible that the power supply is simply not able to provide the advertised current at the rated output voltage.

9

Didn’t try that, I will do that next time.

That was also my first suspicion, because I found a few “Under-voltage” messages in the system logs. So I changed my old PS (1.2A) to another one (4.8A). But the issue still occures.
I don’t have an active USB hub to try if this could be the problem. I will try to get one.

Thanks
Oli

10

The Raspberry Pi 1B was notoriously finicky with power requirements - even more so than some of the later RPi boards. If I recall correctly, the original Pi used a polyfuse in line with the 5v input that had a significant voltage drop across it. I suggest trying a couple of different USB cables for supplying power to the Pi. I’ve had more trouble with dodgy USB cables for powering RPis than I’ve had problems with bad power supplies. Ideally use one of the Raspberry Pi branded power supplies, since they put out around 5.1v to overcome some of the losses in the cable.

Are you running Raspbian or Diet Pi or which OS? The Pi 1B isn’t terribly powerful by today’s standards and node tends to make things grunt a bit. It’s possible that it’s just getting a bit busy and not responding to events quickly enough.

Is there a pattern to when it crashes? Is it always just after 07:00?

[EDIT: I agree with vdkeybus that a powered USB hub is worth a try too]

11

I’m using a quite actual Raspbian (buster)

The issue seems to occur if I try to switch on or off my lamps, but only approx. once a day. There is no reguality.

No, it does not help to push one of the two buttons (I tried both).

I now have an active USB hub. Let’s see if this helps…

Thanks
Oli

12

I found that when the CC2531 no longer responds to S1 (LED should also turn off), it has indeed crashed and it is not an USB data transport problem. I don’t the hub will help in this case, but you can try.

Can you check the very first error message after a ‘good’ run, even when the system still seems to operate fine ?

13

This is the first error after hours of properly working. It is the same like I posted in my first post (this time with debug log)

Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:49:32: Received MQTT message on 'zigbee2mqtt/KuecheInsel/set' with data '{"state":"ON","brightness":204}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:49:32: Publishing 'set' 'state' to 'KuecheInsel'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:49:32: Received MQTT message on 'zigbee2mqtt/KuecheInsel/set' with data '{"state":"ON"}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:49:32: Publishing 'set' 'state' to 'KuecheInsel'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuechePanelLinks', payload '{"state":"ON","linkquality":39,"color_temp":375,"brightness":204,"update_available":false}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuechePanels', payload '{"state":"ON","color_temp":375,"brightness":204}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuechePanelRechts', payload '{"state":"ON","color_temp":375,"brightness":204,"update_available":false}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuecheInsel4', payload '{"update_available":false,"state":"ON","brightness":204}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuecheInsel', payload '{"state":"ON","brightness":204}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuecheInsel3', payload '{"update_available":false,"state":"ON","brightness":204}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuecheInsel1', payload '{"update_available":false,"state":"ON","brightness":204}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuecheInsel2', payload '{"update_available":false,"state":"ON","brightness":204}'
Aug 21 19:49:32 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:32: MQTT publish: topic 'zigbee2mqtt/KuecheInsel5', payload '{"update_available":false,"state":"ON","brightness":204}'
Aug 21 19:49:38 zigbee-server npm[13407]: zigbee2mqtt:error 2020-08-21 19:49:38: Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({"level":204,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'
Aug 21 19:49:38 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:49:38: Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({"level":204,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)
Aug 21 19:49:38 zigbee-server npm[13407]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 21 19:49:38 zigbee-server npm[13407]:     at ontimeout (timers.js:436:11)
Aug 21 19:49:38 zigbee-server npm[13407]:     at tryOnTimeout (timers.js:300:5)
Aug 21 19:49:38 zigbee-server npm[13407]:     at listOnTimeout (timers.js:263:5)
Aug 21 19:49:38 zigbee-server npm[13407]:     at Timer.processTimers (timers.js:223:10)
Aug 21 19:49:38 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:49:38: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({\"level\":204,\"transtime\":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'","meta":{"friendly_name":"KuecheInsel"}}'
Aug 21 19:50:31 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms
Aug 21 19:50:31 zigbee-server npm[13407]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 21 19:50:31 zigbee-server npm[13407]:     at ontimeout (timers.js:436:11)
Aug 21 19:50:31 zigbee-server npm[13407]:     at tryOnTimeout (timers.js:300:5)
Aug 21 19:50:31 zigbee-server npm[13407]:     at listOnTimeout (timers.js:263:5)
Aug 21 19:50:31 zigbee-server npm[13407]:     at Timer.processTimers (timers.js:223:10)
Aug 21 19:50:31 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
Aug 21 19:50:31 zigbee-server npm[13407]: (node:13423) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Aug 21 19:50:53 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:50:53: MQTT publish: topic 'zigbee2mqtt/MotionKueche', payload '{"battery":100,"voltage":3045,"illuminance":2,"linkquality":44,"occupancy":true,"illuminance_lux":2,"no_occupancy_since":82}'
Aug 21 19:51:01 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:51:01: MQTT publish: topic 'zigbee2mqtt/MotionKueche', payload '{"battery":100,"voltage":3045,"illuminance":2,"linkquality":44,"occupancy":false,"illuminance_lux":2}'
Aug 21 19:51:02 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:51:02: Received MQTT message on 'zigbee2mqtt/KuechePanels/set' with data '{"state":"OFF"}'
Aug 21 19:51:02 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:51:02: Publishing 'set' 'state' to 'KuechePanels'
Aug 21 19:51:02 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:51:02: Received MQTT message on 'zigbee2mqtt/KuecheInsel/set' with data '{"state":"OFF"}'
Aug 21 19:51:02 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:51:02: Publishing 'set' 'state' to 'KuecheInsel'
Aug 21 19:51:08 zigbee-server npm[13407]: zigbee2mqtt:error 2020-08-21 19:51:08: Publish 'set' 'state' to 'KuechePanels' failed: 'Error: Command 1 genLevelCtrl.moveToLevelWithOnOff({"level":0,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'
Aug 21 19:51:08 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:51:08: Error: Command 1 genLevelCtrl.moveToLevelWithOnOff({"level":0,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)
Aug 21 19:51:08 zigbee-server npm[13407]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 21 19:51:08 zigbee-server npm[13407]:     at ontimeout (timers.js:436:11)
Aug 21 19:51:08 zigbee-server npm[13407]:     at tryOnTimeout (timers.js:300:5)
Aug 21 19:51:08 zigbee-server npm[13407]:     at listOnTimeout (timers.js:263:5)
Aug 21 19:51:08 zigbee-server npm[13407]:     at Timer.processTimers (timers.js:223:10)
Aug 21 19:51:08 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:51:08: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'KuechePanels' failed: 'Error: Command 1 genLevelCtrl.moveToLevelWithOnOff({\"level\":0,\"transtime\":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'","meta":{"friendly_name":"KuechePanels"}}'
Aug 21 19:51:14 zigbee-server npm[13407]: zigbee2mqtt:error 2020-08-21 19:51:14: Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({"level":0,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'
Aug 21 19:51:14 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:51:14: Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({"level":0,"transtime":10}) failed (SRSP - AF - dataRequestExt after 6000ms)
Aug 21 19:51:14 zigbee-server npm[13407]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 21 19:51:14 zigbee-server npm[13407]:     at ontimeout (timers.js:436:11)
Aug 21 19:51:14 zigbee-server npm[13407]:     at tryOnTimeout (timers.js:300:5)
Aug 21 19:51:14 zigbee-server npm[13407]:     at listOnTimeout (timers.js:263:5)
Aug 21 19:51:14 zigbee-server npm[13407]:     at Timer.processTimers (timers.js:223:10)
Aug 21 19:51:14 zigbee-server npm[13407]: zigbee2mqtt:info  2020-08-21 19:51:14: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'KuecheInsel' failed: 'Error: Command 2 genLevelCtrl.moveToLevelWithOnOff({\"level\":0,\"transtime\":10}) failed (SRSP - AF - dataRequestExt after 6000ms)'","meta":{"friendly_name":"KuecheInsel"}}'
Aug 21 19:53:35 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:53:35: Saving state to file /opt/zigbee2mqtt/data/state.json
Aug 21 19:53:51 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms
Aug 21 19:53:51 zigbee-server npm[13407]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 21 19:53:51 zigbee-server npm[13407]:     at ontimeout (timers.js:436:11)
Aug 21 19:53:51 zigbee-server npm[13407]:     at tryOnTimeout (timers.js:300:5)
Aug 21 19:53:51 zigbee-server npm[13407]:     at listOnTimeout (timers.js:263:5)
Aug 21 19:53:51 zigbee-server npm[13407]:     at Timer.processTimers (timers.js:223:10)
Aug 21 19:53:51 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
Aug 21 19:57:11 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms
Aug 21 19:57:11 zigbee-server npm[13407]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 21 19:57:11 zigbee-server npm[13407]:     at ontimeout (timers.js:436:11)
Aug 21 19:57:11 zigbee-server npm[13407]:     at tryOnTimeout (timers.js:300:5)
Aug 21 19:57:11 zigbee-server npm[13407]:     at listOnTimeout (timers.js:263:5)
Aug 21 19:57:11 zigbee-server npm[13407]:     at Timer.processTimers (timers.js:223:10)
Aug 21 19:57:11 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
Aug 21 19:58:35 zigbee-server npm[13407]: zigbee2mqtt:debug 2020-08-21 19:58:35: Saving state to file /opt/zigbee2mqtt/data/state.json
Aug 21 20:00:31 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Error: SRSP - ZDO - mgmtPermitJoinReq after 6000ms
Aug 21 20:00:31 zigbee-server npm[13407]:     at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
Aug 21 20:00:31 zigbee-server npm[13407]:     at ontimeout (timers.js:436:11)
Aug 21 20:00:31 zigbee-server npm[13407]:     at tryOnTimeout (timers.js:300:5)
Aug 21 20:00:31 zigbee-server npm[13407]:     at listOnTimeout (timers.js:263:5)
Aug 21 20:00:31 zigbee-server npm[13407]:     at Timer.processTimers (timers.js:223:10)
Aug 21 20:00:31 zigbee-server npm[13407]: (node:13423) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
14

Next level of failure:
Now I could not solve the problem by replugging the CC2531; I had to re-flash it to get it back to work… :unamused:

CC2652 is ordered… :frowning:

EDIT:
10 minutes later the problem occured again. Plugging off and on the stick does not work. Tried two sticks, both flashed new. This is really annoying…

15

I have a new suspicion:

Here is my config file:

homeassistant: false
permit_join: true
mqtt:
  base_topic: zigbee2mqtt
  server: 'mqtt://dobby'
serial:
  port: /dev/ttyACM0
  disable_led: true
devices:
  '0x000b57fffeb722fa':
    friendly_name: Druckerlicht
  '0x000b57fffec50c33':
    friendly_name: Buerolicht
  '0x00158d000461b321':
    friendly_name: MotionKueche
    occupancy_timeout: 90
    no_occupancy_since:
      - 82
  '0x000b57fffedce0bd':
    friendly_name: KuechePanelLinks
  '0x000b57fffedc1a22':
    friendly_name: KuechePanelRechts
  '0x588e81fffe3f1f4f':
    friendly_name: KuecheInsel1
  '0x588e81fffe3bb4fa':
    friendly_name: KuecheInsel2
  '0x680ae2fffe7e001b':
    friendly_name: KuecheInsel3
  '0x588e81fffe3cb4e2':
    friendly_name: KuecheInsel4
  '0x588e81fffe32b8f2':
    friendly_name: KuecheInsel5
groups:
  '1':
    friendly_name: KuechePanels
    transition: 1
    devices:
      - '0x000b57fffedce0bd'
      - '0x000b57fffedc1a22'
  '2':
    friendly_name: KuechInsel 
    transition: 1
    devices:
      - '0x588e81fffe3f1f4f'
      - '0x588e81fffe3bb4fa'
      - '0x680ae2fffe7e001b'
      - '0x588e81fffe3cb4e2'
      - '0x588e81fffe32b8f2'

Without group 2, everything works fine.
With group 2, the error occurs like I described above.

The devices in group 2 all are IKEA LED1837R5. Could it be, that zigbee2mqtt has a problem with putting 5 of them into a group??

16

Hi all,
My zigbee2mqtt suddenly stopped working last night. The only thing that’s changed is that I unfortunately updated to the latest release of Zigbee2MQTT.

Please help! Is this a bug? Is my CC2531 dead?

> zigbee2mqtt@1.14.4 start /opt/zigbee2mqtt
> node index.js

Zigbee2MQTT:info  2020-09-13 00:15:43: Logging to console and directory: 'data/log/' filename: log.txt
Zigbee2MQTT:debug 2020-09-13 00:15:45: Loaded state from file /opt/zigbee2mqtt/data/state.json
Zigbee2MQTT:info  2020-09-13 00:15:45: Starting Zigbee2MQTT version 1.14.4 (commit #166f1a8)
Zigbee2MQTT:info  2020-09-13 00:15:45: Starting zigbee-herdsman...
Zigbee2MQTT:debug 2020-09-13 00:15:45: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null},"backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","databasePath":"/opt/zigbee2mqtt/data/database.db","network":{"channelList":[11],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6754},"serialPort":{"path":"/dev/ttyACM0"}}'
  zigbee-herdsman:adapter Path '/dev/ttyACM0' is valid for 'ZStackAdapter' +0ms
  zigbee-herdsman:controller:log Starting with options '{"network":{"networkKeyDistribute":false,"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13],"panID":6754,"extendedPanID":[221,221,221,221,221,221,221,221],"channelList":[11]},"serialPort":{"path":"/dev/ttyACM0"},"databasePath":"/opt/zigbee2mqtt/data/database.db","databaseBackupPath":"/opt/zigbee2mqtt/data/database.db.backup","backupPath":"/opt/zigbee2mqtt/data/coordinator_backup.json","adapter":{"concurrent":null}}' +0ms
  zigbee-herdsman:adapter:zStack:znp:log Opening SerialPort with /dev/ttyACM0 and {"baudRate":115200,"rtscts":false,"autoOpen":false} +0ms
  zigbee-herdsman:adapter:zStack:znp:log Serialport opened +5s
  zigbee-herdsman:adapter:zStack:znp:log Writing skip bootloader payload +16s
  zigbee-herdsman:adapter:zStack:unpi:writer --> buffer [239] +0ms
  zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1} +0ms
  zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32] +1s
  zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1} +6s
  zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32] +6s
  zigbee-herdsman:adapter:zStack:znp:SREQ --> SYS - ping - {"capabilities":1} +6s
  zigbee-herdsman:adapter:zStack:unpi:writer --> frame [254,0,33,1,32] +6s
Zigbee2MQTT:error 2020-09-13 00:16:27: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2020-09-13 00:16:27: Failed to start zigbee
Zigbee2MQTT:error 2020-09-13 00:16:27: Exiting...
Zigbee2MQTT:error 2020-09-13 00:16:27: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:90:31)
    at Generator.throw (<anonymous>)
    at rejected (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:25:65)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! zigbee2mqtt@1.14.4 start: `node index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the zigbee2mqtt@1.14.4 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-09-12T23_16_30_821Z-debug.log
17

Hmmm, I’m starting to feel that there is an issue with the current version of zigbee2mqtt, see also here

18

I got the exact same problem. It works a few hours and then suddenly stops with the same errors as in this topic. Is it really still not a proper fix for this?

19

I followed the firmware upgrade guide here which is just a simple software operation (no hardware needed):

It worked. So far. You have to google for the software. The firmware I used is found here:

After the “Image transfer”, I just inserted the stick into my Home Assistant and restartet Zigbee2MQTT. Back in business again. We will see for how long though.

20

I’ve been seeing the same probmems with my CC2531 USB cordinator, and it’s been driving me crazy.
Has there been any fix found for this problem?

Regaining functionality by unplugging and replugging the USB coordinator works a few times, but I found that I needed to reprogram the firmware of the CC2531 using a TI CC Debugger to get it to connect and function again. Lately, I’ve been reprogramming the chip every 7-14 days!
The fact that firmware is getting corrupted seems like a hardware problem, likely the CC2531 chip itself. Since it’s happening to many people, it seems like a defect in the chip design.