CC2652P Adapter not reachable any more

[mhl66]

Adapter: EBYTE E72 2G4M20S1E (CC2652P) (newest Firmware, of course...)

Version 1.5.6 works with the known issues (IKEA STYRBAR etc. etc.), but 1.6.1 does not any more:

zigbee.0	2021-08-28 19:18:04.939	error	Error herdsman start
zigbee.0	2021-08-28 19:18:04.938	error	Failed to start Zigbee
zigbee.0	2021-08-28 19:18:04.938	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
zigbee.0	2021-08-28 19:18:04.724	info	Installed Version: ioBroker/ioBroker.zigbee#master
zigbee.0	2021-08-28 19:18:04.696	info	Starting Zigbee npm ...
zigbee.0	2021-08-28 19:18:04.694	info	Try to reconnect. 1 attempts left
zigbee.0	2021-08-28 19:17:54.691	error	Error herdsman start
zigbee.0	2021-08-28 19:17:54.691	error	Failed to start Zigbee
zigbee.0	2021-08-28 19:17:54.690	error	Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)"

Please HELP!

[Apollon77]

Try to restart the system and check that the device is there in /dev/tty... can not lock port norally means that an other process already uses it

[mhl66]

Thanks, but I did this. Port is /dev/ttyUSB0. Alternative Zigbee adapter "CONBEE II" is working perfectly (but is only rudimentarily supported ("experimental support"). Thus, the serial ports are working.

[Apollon77]

And conbe is clearly ended when you start iobroker zigbee process? Try also "iobroker fix"

[mhl66]

No, CONBEE (deconz) is running, but has another PAN and another serial port. But I tried the CC... adapter alone, too (without success).

[mhl66]

(Firmware of CC2652P is double-checked...) (And "iobroker fix" is futile, since I twice reinstalled everything on the basis of the Raspbian Simple Image (TINY).

That there is an error in 1.6.1 is evident - here is the whole start process log:

2021-08-29 14:50:54.790 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 2473

2021-08-29 14:50:57.518 - info: zigbee.0 (2473) starting. Version 1.6.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.5, js-controller: 3.3.15 2021-08-29 14:50:57.618 - info: zigbee.0 (2473) Starting Zigbee npm ... 2021-08-29 14:50:58.112 - info: zigbee.0 (2473) Installed Version: iobroker.zigbee 2021-08-29 14:50:59.895 - info: zigbee.0 (2473) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210319}} 2021-08-29 14:50:59.919 - info: zigbee.0 (2473) Unable to disable LED, unsupported function. 2021-08-29 14:51:00.021 - info: zigbee.0 (2473) --> transmitPower : normal 2021-08-29 14:51:00.088 - info: zigbee.0 (2473) Currently no devices. 2021-08-29 14:51:00.090 - info: zigbee.0 (2473) Zigbee started 2021-08-29 14:51:00.093 - error: zigbee.0 (2473) 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(). 2021-08-29 14:51:00.094 - error: zigbee.0 (2473) unhandled promise rejection: SRSP - SYS - osalNvRead after 0,2ms 2021-08-29 14:51:00.101 - error: zigbee.0 (2473) Error: SRSP - SYS - osalNvRead after 0,2ms at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7) 2021-08-29 14:51:00.102 - error: zigbee.0 (2473) SRSP - SYS - osalNvRead after 0,2ms 2021-08-29 14:51:00.111 - info: zigbee.0 (2473) cleaned everything up... 2021-08-29 14:51:00.113 - info: zigbee.0 (2473) Zigbee: disabling joining new devices. 2021-08-29 14:51:00.613 - info: zigbee.0 (2473) terminating 2021-08-29 14:51:00.615 - warn: zigbee.0 (2473) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-08-29 14:51:01.180 - error: host.raspberrypi Caught by controller[0]: 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(). The promise rejected with the reason: 2021-08-29 14:51:01.181 - error: host.raspberrypi Caught by controller[1]: Error: SRSP - SYS - osalNvRead after 0,2ms 2021-08-29 14:51:01.182 - error: host.raspberrypi Caught by controller[1]: at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) 2021-08-29 14:51:01.182 - error: host.raspberrypi Caught by controller[1]: at listOnTimeout (internal/timers.js:554:17) 2021-08-29 14:51:01.182 - error: host.raspberrypi Caught by controller[1]: at processTimers (internal/timers.js:497:7) 2021-08-29 14:51:01.183 - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-08-29 14:51:01.183 - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled

[1N4148]

Got something similar in an older version (was discussed here). Solution was to start the adapter with a different extended pan id and pan id. After sucessful start of the adapter the values can be reverted to the original values to get the network back.

[mhl66]

No, did this (i.e. ExtPAN = DDDDDDDDDDDD1234, PanID = 0x0001, switched back afterwards) does not help at all.

[mhl66]

Many reinstalls later...New Raspi, new OS (DietPi / Debian 11), firmware current: MANY warnings on adapter install with 1.6.1, and everytime similar errors when starting the adapter:

host.DietPi | 2021-09-01 00:43:25.331 | info | Restart adapter system.adapter.zigbee.0 because enabled
-- | -- | -- | --
host.DietPi | 2021-09-01 00:43:25.330 | error | instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.DietPi | 2021-09-01 00:43:25.329 | error | Caught by controller[1]: at processTimers (internal/timers.js:497:7)
host.DietPi | 2021-09-01 00:43:25.329 | error | Caught by controller[1]: at listOnTimeout (internal/timers.js:554:17)
host.DietPi | 2021-09-01 00:43:25.328 | error | Caught by controller[1]: at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
host.DietPi | 2021-09-01 00:43:25.328 | error | Caught by controller[1]: Error: SRSP - SYS - osalNvRead after 0,2ms
host.DietPi | 2021-09-01 00:43:25.327 | error | Caught by controller[0]: 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(). The promise rejected with the reason:
zigbee.0 | 2021-09-01 00:43:24.738 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
zigbee.0 | 2021-09-01 00:43:24.735 | info | terminating
zigbee.0 | 2021-09-01 00:43:24.235 | info | Zigbee: disabling joining new devices.
zigbee.0 | 2021-09-01 00:43:24.233 | info | cleaned everything up...
zigbee.0 | 2021-09-01 00:43:24.221 | error | SRSP - SYS - osalNvRead after 0,2ms
zigbee.0 | 2021-09-01 00:43:24.221 | error | Error: SRSP - SYS - osalNvRead after 0,2ms at Timeout._onTimeout (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35) at listOnTimeout (internal/timers.js:554:17) at processTimers (internal/timers.js:497:7)
zigbee.0 | 2021-09-01 00:43:24.214 | error | unhandled promise rejection: SRSP - SYS - osalNvRead after 0,2ms
zigbee.0 | 2021-09-01 00:43:24.214 | error | 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().
zigbee.0 | 2021-09-01 00:43:24.210 | info | Zigbee started
zigbee.0 | 2021-09-01 00:43:24.208 | info | Currently no devices.
zigbee.0 | 2021-09-01 00:43:24.144 | info | --> transmitPower : high
zigbee.0 | 2021-09-01 00:43:24.013 | info | Unable to disable LED, unsupported function.
zigbee.0 | 2021-09-01 00:43:24.001 | info | Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210319}}
zigbee.0 | 2021-09-01 00:43:22.160 | info | Installed Version: ioBroker/ioBroker.zigbee#master
zigbee.0 | 2021-09-01 00:43:21.722 | info | Starting Zigbee npm ...
zigbee.0 | 2021-09-01 00:43:21.598 | info | starting. Version 1.6.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.6, js-controller: 3.3.15
host.DietPi | 2021-09-01 00:43:18.829 | info | instance system.adapter.zigbee.0 started with pid 13846

Mod Edit: Code tags.

[1N4148]

This happend also with an empty/fresh/new zigbee database? A symptom of my fault was, that the adapter didn't come up with the current config/database but could be started with a fresh config/new database.

[mhl66]

Yes, thus I wrote "New Raspi, new OS (DietPi / Debian 11)" (see above): exactly the same errors!

[1N4148]

Ok I thought so but I didn't know if you have restored a backup after fresh installation.

[Z18Aplha]

Same errors here. adapter Version 1.6.0 and 1.6.1 Zigbee Board: CC2652R

i use a docker container to run iobroker, but this should not be the problem. A zigbee2mqtt docker container runs perfect without any problems.

Ok i tried version 1.5.6 and it works. I thought my firmware on my board is new enough. Can somebody tell me, why zigbee2mqtt works fine with the new herdsmen, but this adapter doesn't?

[Valentin-Gonchar]

I have the same issue

[kirovilya]

Can you try latest version from github?

[Dome2075]

Same Problem. Zigbee Board: CC2652R

zigbee.0 | 2021-12-06 20:18:02.360 | error | Error herdsman start
zigbee.0 | 2021-12-06 20:18:02.359 | error | Failed to start Zigbee
zigbee.0 | 2021-12-06 20:18:02.359 | error | Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
zigbee.0 | 2021-12-06 20:18:02.036 | info | Installed Version: iobroker.zigbee@1.6.8
zigbee.0 | 2021-12-06 20:18:02.012 | info | Starting Zigbee npm ...
zigbee.0 | 2021-12-06 20:18:02.011 | info | Try to reconnect. 1 attempts left
zigbee.0 | 2021-12-06 20:17:52.007 | error | Error herdsman start
zigbee.0 | 2021-12-06 20:17:52.007 | error | Failed to start Zigbee
zigbee.0 | 2021-12-06 20:17:52.006 | error | Starting zigbee-herdsman problem : "All table entries need to be the same length"
zigbee.0 | 2021-12-06 20:17:44.988 | info | Installed Version: iobroker.zigbee@1.6.8
zigbee.0 | 2021-12-06 20:17:44.432 | info | Starting Zigbee npm ...
zigbee.0 | 2021-12-06 20:17:44.325 | info | starting. Version 1.6.8 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 3.3.21
host.IOBroker | 2021-12-06 20:17:41.255 | info | instance system.adapter.zigbee.0 started with pid 337
host.IOBroker | 2021-12-06 20:17:39.250 | info | instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

Mod edit: Removed HTML Tags, added code tags. (A)

[asgothian]

Note that this is not the same issue as the original posters issue. It may have the same "visible" effect, but it has a different cause and error message.

It seems that there is an issue with either the firmware on the stick, the nvram backup or the shepherd.db. Please test:

• stop the zigbee adapter
• remove the files shepherd.db and nvbackup.json from /opt/iobroker/iobroker-data/zigbee_0 (do keep a copy so you can restore them afterwards or you may have to pair all devices again.)
• change the zigbee channel and/or the pan ID (keep note of the old settings so you can restore them)
• start the adapter
• check if this message reappears: error | Starting zigbee-herdsman problem : "All table entries need to be the same length"

If it does, chances are one or more entries from the following list are correct

• your firmware is defunct - the board needs to be flashed with new firmware
• your USB connection is defunct - use a different USB cable, connect to a different USB port (not USB3), disconnect USB3 devices if possible

If the adapter does start, please

• stop the adapter
• restore the original settings (channel, pan ID, ...)
• restore the shepherd.db file.
• do not restore the nvbackup.json file
• start the adapter

If the adapter runs, you are done. If it does not, the shepherd.db file may be defect - please try to restore an older shepherd.db from the backups present in the folder and repeat the test.

A.

[wjaschenkov]

I have the same problem. Zigbee hardware: sonoff zigbee 3.0 usb dongle plus. It is tested on the two different boards(raspberry, odroid) and with two firmware(CC1352P2_CC2652P_launchpad_coordinator_20210708.zip, CC1352P2_CC2652P_launchpad_coordinator_20211114.zip). Tried all points from previous post. Without success.

2021-12-09 22:01:31.805 - info: zigbee.0 (5533) starting. Version 1.6.6 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.22.7, js-controller: 3.3.21 2021-12-09 22:01:32.132 - info: zigbee.0 (5533) Starting Zigbee npm ... 2021-12-09 22:01:34.096 - info: zigbee.0 (5533) Installed Version: iobroker.zigbee@1.6.6 2021-12-09 22:01:54.629 - error: zigbee.0 (5533) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" 2021-12-09 22:01:54.632 - error: zigbee.0 (5533) Failed to start Zigbee 2021-12-09 22:01:54.634 - error: zigbee.0 (5533) Error herdsman start 2021-12-09 22:02:04.644 - info: zigbee.0 (5533) Try to reconnect. 1 attempts left 2021-12-09 22:02:04.649 - info: zigbee.0 (5533) Starting Zigbee npm ... 2021-12-09 22:02:04.693 - info: zigbee.0 (5533) Installed Version: iobroker.zigbee@1.6.6 2021-12-09 22:02:05.250 - error: zigbee.0 (5533) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'" 2021-12-09 22:02:05.252 - error: zigbee.0 (5533) Failed to start Zigbee 2021-12-09 22:02:05.254 - error: zigbee.0 (5533) Error herdsman start

After the first writing of firmware, i could no longer bootloader mode. The other firmware updates were made with the debugger.

[asgothian]

I have the same problem.

You have the same problem only in so far as (in an analogy from another field) your car won't start.

In your case, the stick does not respond to communication from the adapter, i.e. either the stick, the USB connection or the firmware are broken.

Please ensure that

• the Stick not plugged into a USB3 port
• no USB3 Harddrives / SSD are in use when attempting to contact the stick

If the problem remains despite these conditions the stick / firmware are likely not functional.

A.

[wjaschenkov]

Thanks for the tips. None of the boards have USB3. Also when connecting the stick is detected by the kernel. I have had the cc2531 stick on the board for years with no problem. After trying the CC2652P stick without success, I wanted to go back to the cc2531. I had to uninstall and reinstall the adapter, otherwise I had the same error messages with the cc2531 stick even after rebooting the board.

I am thankful for every help.

[Dome2075]

Hi,

i solved problem by reflashing the CC26xx.

importent is this option:

[wjaschenkov]

I have solved my problem. So far I used only "Flash Programmer 2" for the firmware update. These attempts were all successful, but the stick did not work. When I tried Uniflash, the firmware for the debugger boards was also updated. Now the stick works. Thanks for the tips.