1.18.0 won't start with Slaesh's CC2652RB: "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" #6517
Comments
|
I'm having the same problem with the same zigbee stick and docker-compose setup |
|
Thanks for creating a new issue for this! There are several others reporting the same on an older (closed) issue: #2997 (comment) |
|
Additional info: The reported error has been observed on a Raspberry Pi 3B+ with Slae'sh CC2652RB USB stick (on extension cable, of course). However, version 1.18.0 works fine on my 2nd system, a Raspberry Pi 4 with Raspbee II add-on card. So it could be limited to CC2562RB, the zStack-Firmware or USB devices. Infact, most (if not all) of the older issue reports are related to CC2652R devices. |
|
I'm on the same setting (slae'sh CC2652 & official Docker Image). For me, it broke with yesterdays release of the dev image, same for todays 1.18 release. |
|
@CSchlipp Did it work with -dev images before yesterday and you have the commit ID of the last working version? |
Yes, it did. The last dev-image running successfully was: Zigbee2MQTT version 1.17.1-dev (commit #1ddd2ac) (latest-dev as of 2021-02-28 04:20:07) The first version that threw this error was Zigbee2MQTT version 1.17.1-dev (commit #57165e3) (latest-dev as of 2021-03-01 04:18:20) |
|
Looks like zigbee-herdsman was updated which updated a dependency "serialport" (sounds like it could have something to do with this) one patch version. Looking into the changes in "serialport" if I can find anything that could have caused this... |
|
same issue slae'sh CC2652 |
|
I'm going to sleep. One thing to try would be to downgrade zigbee-herdsman to see if that solves the issue. |
That‘s an important information, so the bug must have been introduced with latest 1.17.1-dev/1.18.0 version.
Can you link the commit that introduced the change? |
|
here also the same error..[ stupid to upgrade withouth looking here ] Is there a way to downgrade? |
|
Hello everybody, Same issue for me. I've downgraded with those commands : cd /opt/zigbee2mqtt |
|
Had the same issue after upgrading tot 1.18. Using slae.sh CC2652 stick. Linux on intel. Works after reverting to previous version from backup. |
|
Same issue with |
|
I have the exact same problem. But only dockervavailable. @liambrugaro Can I test something with a docker based setup? |
I can confirm this DOES NOT work. @m0wlheld & @liambrugaro (Just tested) It does startup but things don't work properly If it's for any help I'm also using Slaesh's CC2652RB --> usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_41_34-if00-port0 |
|
I'm also having the same issue with 1.18.0 via Docker Compose. |
Are you sure? In my case, it does work with commit 1ddd2ac. Here's what I used to test: $ docker run --device /dev/serial/by-id/usb-Silicon_Labs_slae.sh_cc2652rb_stick_-_slaesh_s_iot_stuff_00_12_4B_00_21_CC_44_12-if00-port0:/dev/ttyACM0 --rm -ti node:latest /bin/bash
root@e1523ad5a16b:/# git clone https://github.com/Koenkk/zigbee2mqtt.git
root@e1523ad5a16b:/# cd zigbee2mqtt
root@e1523ad5a16b:/# npm ci
root@e1523ad5a16b:/# npm startResult after last command: Then I did a checkout on 1ddd2ac: root@e1523ad5a16b:/zigbee2mqtt# git checkout 1ddd2ac
root@e1523ad5a16b:/zigbee2mqtt# npm ci
root@e1523ad5a16b:/zigbee2mqtt# npm startResult after last command: |
It does startup but when I tried to control my devices they did not respond. (Can't debug more right now, working) |
I've double checked the logs again, but the docker image build from this commit was definitely running smoothly for 24h, until the next update broke it. |
Note the log line "Currently 0 devices are joined", that's probably the reason why none of your devices responded ;) |
Yeah in this case, dunno if it was like that on my case :D |
|
Works for me. RPI3B+ with Slaesh's CC2652RB stick, thanks. Maybe a note on what you actually changed? |
|
Unfortunately, the new container I made does not read the contents of the configuration.yaml and keeps reporting that 0 devices are currently joined. Also, the front-end won't start. |
Makes sense, because the default configuration does not enable frontend. But - I'd say that's a different cause / issue. |
True, but the fact that it is not using the correct configuration.yaml file seems to stem from this issue, that's why I thought I'd mention it here, in case more people experience this. |
|
1.18.1 is available now, can you guys confirm that it works? (hass addon in +- 30 mins) |
Yes, it works (using koenkk/zigbee2mqtt:1.18.1 container image). |
|
Also works for me. Thanks for the fast fix! <3 |
|
1.18.1 in Docker works fine! Thanks! |
|
I can confirm 1.18.1 is running without problems. Thanks for the very quick fix! I just saw the new frontend and the dashboard for the first time. Looks amazing, great work! |
|
I can confirm 1.18.1 is running too |
|
CC2531 zStack12 on Rpi4 core-2021.3.0 works smooth. Thanks! |
|
I dont know if this is the same issue, but 1.18.0 and 1.18.1 are not working on my side using slaesh's interface on an rpi 3. Running in docker and it continually fails with |
|
Line 17: exec "$@" My assumption is an error in your docker call, can you post the exact docker command line? |
|
1.18.1 not working for me
|
|
Can someone please help ? Still stuck with this problem... |
|
Hello, still have problem with slaesh. |
That doesn’t mean it is in any way related to this issue, that was solved and closed months ago. Your log doesn’t contain the error message that is in the subject, so it is probably unrelated. Unfortunately I do not have a solution for you but I would start searching for the “Failed to validate path: 'Error: spawn udevadm ENOENT'” message that is in your log. |
yes but didnt found anything about that... also when I change the panid it is starting ... |
|
@m0wlheld I've updated serialport again (what previously caused the issue) since there is a newer version available now. Can you check if the latest dev branch works now (wait at least 1 hour before testing after this comment). |
|
Recent latest-dev (Docker image) works: "Starting Zigbee2MQTT version 1.19.0-dev (commit #c508155)" . No issues. |
|
@m0wlheld it should show 1.20.0-dev, are you sure you are using the latest? |
|
Now I do and still no issues. |
and others
What happened
Just switched from Zigbee2MQTT 1.17.1 (koenkk/zigbee2mqtt:1.17.1) to 1.18.0 (koenkk/zigbee2mqtt:latest) and now Zigbee2MQTT won't start any more (see below). Configuration remained unchanged.
What did you expect to happen
I expected Z2M to start.
How to reproduce it (minimal and precise)
My configuration (network key changed):
Service definition in docker-compose file:
Debug info
Zigbee2MQTT version: 1.18.0 (official Docker image)
Adapter hardware: CC26X2R1 (slae'sh CC2652)
Adapter firmware version: 20210120
The text was updated successfully, but these errors were encountered: