Error while starting zigbee-shepherd - request timeout at CcZnp #118
Comments
|
Same problem here, flashed the USB again but with the same result. I'm using Hassio and tried both versions of Zigbee2MQTT (regular and edge). This made no difference. |
|
I have the same issue - I think it stems from my stick being on |
|
I have tried all USB ports of the RPi but that didn't work. Like you said I changed them in the configuration.yaml file of /share/zigbee2mqtt/. Any other suggestions? |
|
My next guess was to delete my configuration.yaml file every time to create a new one. Still with the same result:
|
|
🤔 the way I'd discovered the issue was by using the I have two USB sticks plugged in, a Z-Wave, and a Zigbee - the Z-Wave took /dev/ttyACM0, so the zigbee was /dev/ttyACM1 for me. You might be able to tell which one is which if you have more than one by looking at the ls -al /dev/serial/by-id/ |
|
I'm using Hassio with the SSH add-on. This terminal command is not usable for me. Or can someone explain me how to make this command executable? |
|
OK, found it. In the end I think it has to do with load shedding of my RPi. I had 4 devices connected. And at that moment the Zigbee thingy did not work. I disconnected all deviced, rebooted the RPi and started putting in the devices one by one. I verified every input in the HASSIO HARDWARE page to see which USB port showed up and edited the configuration.yaml file to the corresponding port. And at that moment the Zigbee Thingy started working. Problem solved... |
|
I have the same issue. Yesterday I updated to 1.2.1 . I'm on hassio (lastest release). |
|
I have the same issue. |
|
Looks like you have a crashed stick, see here: Also I don't have or had "zigbee_shepherd_devices: true" in my config. What does it stand for? EDIT: Nevermind found it
|
|
hi, I too have the problem if I try to restart the zigbee2mqtt haddon continually gives me the error :) zigbee2mqtt:info 3/14/2019, 4:50:48 PM Logging to directory: '/share/zigbee2mqtt/log/2019-03-14.16-50-48'
|
|
@marinoraffaele what is the output of |
|
@Koenkk below the result of the command: |
|
I have the same issues, can't seem to get zigbee2mqtt to work reliably anymore after flashing the latest firmware (20190223) on my CC2531 stick, in combination with updating Zigbee2MQTT. sometimes, I can get it to work by manually starting Zigbee2MQTT and resetting / reinserting the usb stick. Most of the times it doesn't help @Koenkk don't know what you are looking for, but here's my output of " ls /dev " |
|
@Koenkk below the result of the command: i have flashing Firmware CC2531ZNP-Prod_20190223.zip on my CC2531 stick, in combination with updating Zigbee2MQTT.
-------1---------
-------2--------- Log
|
|
@marinoraffaele did it work before? Can you try re-flashing your stick? |
|
I tried to flash the zigbee pen again but the problem persists. if I restart the Raspberry everything works perfectly, at the first restart of hassio the addon zegebemqtt shows the error. |
I reflash the stick to latest firmware, but still get error. Here is my config. But after I deleted "zigbee_shepherd_devices: true" and restart zigbee2mqtt, It return normal. |
|
I don't have the zigbee_shepherd_devices configuration: true but it doesn't work. I repeat the addon works if I restart Raspberry. |
|
Same issue here... |
|
@Michaelnorge did it ever work, or did it stop working after some time? |
|
guys is not able to help me to solve this error when starting the add-on zigbee2mqtt? I do not know what to do. if I try to flash the pen cc2531 as soon as I insert it and the add-on works everything works, if I try to restart it has stopped working with the same error. |
|
Exactly the same issue here...on a Rpi3 |
|
@Koenkk It is working, but after a restart the USB-dongle wont start again. Its light is turning off while booting and the log shows "info: zigbee.0 Error while starting zigbee-shepherd, attempting to fix... (takes 60 seconds)" and after 60 seconds "error: zigbee.0 Error while starting zigbee-shepherd!. Error: request timeout" I need to restart raspberry three times to get the zigbee-dongle in work again. I´m updated everything and made a reflash as well, but it did not help. |
|
For all hasio users, can you check with the latest edge? |
|
I was getting this error on a fresh hassio install, redid the whole thing to hassbian and I'm still getting the same error. Restarting multiple times isn't helping. Pressing the reset button isn't helping. Full debug of startup: zigbee2mqtt:info 3/26/2019, 11:39:21 PM Logging to directory: '/opt/zigbee2mqtt/data/log/2019-03-26.23-39-21' npm ERR! A complete log of this run can be found in: |
|
Note I am seeing this in dmesg, this is taking the usb out, (reflashing), putting it back in and then getting a failed start. The last two error lines appear after the failed start... usb 1-1.2: USB disconnect, device number 4 |
|
Could someone take a minute to describe what led on the stick should do in a correct startup? Currently the led on my stick comes on when you first plug it in, goes out when the "npm start" command is given and stays off as the start fails. In a normal start should the led come back on? |
|
@colmben the procedure should be:
|
|
Great, thanks. |
|
So I am getting green light on re-plug, light off on reset but then the start fails with the timeout message and the green stays off. |
|
what is the output of |
|
pi@hassbian:/opt/zigbee2mqtt $ ls /dev |
|
Slightly easier format to read... pi@hassbian:/opt/zigbee2mqtt $ ls -l /dev |
|
you arent using hassio, right? can you verify write access: http://www.zigbee2mqtt.io/information/zigbee2mqtt_fails_to_start.html |
|
I tried hassio first but had this issue, found it very confusing to confirm anything re usb/serial ports in hassio so I did a fresh hassbian install and that is what I am showing now. Write access looks ok... pi@hassbian:/opt/zigbee2mqtt $ test -w /dev/ttyACM0 && echo success || echo failure |
|
can you try re-flashing the stick? As you also have tried a different os/system, I wouldnt know what to do next (there is a chance that the stick itself is broken though). |
|
I've reflashed with max stability and an old one from last July, both failed with same error. I'll try on an ubuntu laptop and see how it goes. |
|
Same issue on the unbuntu laptop. Oh dear :( I waited months for that CC2531 from AliExpress, arrgggg! |
|
The cable going from the debugger to the cc2531 could be plugged in incorrect. Did you check that? Do you get a confirmation that the firmware was flashed correctly? |
|
I double checked the connections against the picture in https://www.zigbee2mqtt.io/getting_started/flashing_the_cc2531.html The flash seems to go fine. The led comes on in green once the flash has finished: Having said that, I'm just seeing that line re Target: CC 2540 - is that normal? Could I have bought the wrong thing? |
|
Look it up in your Aliexpress order. Does it say cc2540? |
Oh Dear Lord! That Aliexpress page is very confusing, the two pictures for the CC2531 and CC2540 are the same! Anyways, in Irish parlance, I am an ejit, sorry for confusing the thread (though I suspect I wouldn't be the only person to do this so at least it is now one documented possibility for the timeout error). |
|
Glad you found the issue. Hopefully your new cc2531 will arrive faster. |
|
@colmben it this something that can be also verified visually? Is CC2540 written on the chip of the USB? |
I have the same problems (hassbian) since I updated the cc2531 firmware to the (20190223) version. Before that (can't remember the fw version) everything worked without major issues for may be half a year. the stick is on /dev/ttyACM0 just like in the config, and there's write access to the serial port But I cant get Zigbee2mqtt to run as a daemon anymore, output: Also after a while, it looks like the cc2531 stick can't be reset anymore, led goes on immediately after a reset. Only option then is to reflash, and I have to repair almost all devices (18 of them). At the moment I'm using the fw from 20190315. |
|
can you provide the log at the moment it crashes? |
The stick is marked as CC25xx which isn't very helpful! The chip itself is very faint, but I think I see a CC2540 on it. Either way, if you look at the AliExpress order summary I posted, it has the line "Product Properties: CC2540", this indicates I chose the wrong one. Why sellers do multiple different items in one listing like that I don't know, it is very confusing |
|
I had the exact same issue, however with older version/firmware combinations too. To fix this, I have to change the port NOT over the hassio web ui, BUT manually in |
|
So @danielwelch you may want to check out if config changes over the hass.io addon web ui do still work, or just don't work for me because I'm using stock ubuntu instead of a RPI with the pre-configured hass.io image. Maybe the point is that ubuntu has a complete file system, so the config path for me is |
|
This is a known issue that will hopefully be fixed with
#143
The entire config schema will he changed when
#144 merges (this
will only affect edge version at first but the plan is to move the stable
version to this as well).
…On April 9, 2019 at 2:04:53 AM, Moritz Kraus ***@***.***) wrote:
So @danielwelch <https://github.com/danielwelch> you may want to check
out if config changes over the hass.io addon web ui do still work, or
just don't work for me because I'm using stock ubuntu instead of a RPI with
the pre-configured hass.io image. Maybe the point is that ubuntu has a
complete file system, so the config path for me is
/usr/share/hassio/share/zigbee2mqtt/configuration.yaml instead of just
/share/zigbee2mqtt/configuration.yaml . Just my 2 cents...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#118 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHvnbYZprgDaRrJ83-sQXha5Owf5LCJDks5vfDuVgaJpZM4bXfIo>
.
|
|
Same problem here (CC2531), I've been able to operate with aqara devices and tradfi lamps and another CC2531 as a router, after docker upgrade, nothing works, permissions are ok,port is correctly asssigned and I've done all the combinations of button press, unplug restart zigbee2mqtt container... Last Docker version, and stable coordinator firmware. "cc-znp The serialport /dev/ttyACM1 is closed." but I've verified that zigbee2mqtt has write access to the port. Completely stuck, any clue what else to try ? UPDATE: reflashing the CC2531 concentrator with stability firmware has solved it. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I've just recieved a CC2531 Zigbee stick which had the latest firmware on it. I plugged it in to my Home Assistant (RPi 3 - v0.88.1) but I can't get it to work. I've tried pushing the 'debug' button on the stick but it didn't do much. Tried looking up the error but couldn't find a solution
Config
Log
I've tried pushing the 'debug' button on the stick but it didn't do much.
The text was updated successfully, but these errors were encountered: