Zibee2mqtt with cc2531 stability issue

Configuration
21

I did the same before, But it did not help. The network is still unstable.

22

Is your cc2531 connected using an USB extension cable ? It might be rf interference from USB3 ports.

23

thanks for the advice, Its already connected through extension cable of 30cm

24

HI,

My system is unstable again. I reset the system again but I have issues now on my log. Can someone explain my log bellow?

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] socat.sh: executing…
[23:04:53] INFO: Socat not enabled, marking service as down
[cont-init.d] socat.sh: exited 0.
[cont-init.d] zigbee2mqtt.sh: executing…
[23:04:54] INFO: MQTT available, fetching server detail …
[23:04:54] INFO: Previous config file found, checking backup
[23:04:54] INFO: Creating backup config in ‘/config/zigbee2mqtt/.configuration.yaml.bk’
[23:04:54] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks …
[cont-init.d] zigbee2mqtt.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[23:04:54] INFO: Handing over control to Zigbee2mqtt Core …

[email protected] start /app
node index.js
Zigbee2MQTT:warn 2021-07-28 23:04:59: permit_join set to true in configuration.yaml.
Zigbee2MQTT:warn 2021-07-28 23:04:59: Allowing new devices to join.
Zigbee2MQTT:warn 2021-07-28 23:04:59: Set permit_join to false once you joined all devices.
(node:329) UnhandledPromiseRejectionWarning: Error: SREQ ‘–> AF - dataRequestExt - {“dstaddrmode”:2,“dstaddr”:“0x000000000000fffd”,“destendpoint”:242,“dstpanid”:0,“srcendpoint”:242,“clusterid”:33,“transid”:75,“options”:0,“radius”:30,“len”:6,“data”:{“type”:“Buffer”,“data”:[25,3,2,11,254,0]}}’ failed with status ‘(0x11: BUFFER_FULL)’ (expected ‘(0x00: SUCCESS)’)
** at Znp. (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27)**
** at Generator.next ()**
** at fulfilled (/app/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58)**
(Use node --trace-warnings ... to show where the warning was created)
(node:329) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see Command-line API | Node.js v21.6.2 Documentation). (rejection id: 1)
(node:329) [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.

Thanks,
Itzik

25

My first reaction would be something wrong happened via communicating with usb but it is better to move this thread to zigbee2mqtt repository as an issue and follow there.

1 Like
26

Finally I switched conbee…It much more stable