search

Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
12.07k stars 1.68k forks source link

Error: AREQ - SYS - resetInd after 30000ms #2899

Closed huahe closed 4 years ago

huahe commented 4 years ago

Hello !

I recently moved everything to a Intel NUC Model # DC3217IYE

I installed Ubuntu 18.04 LTS and set up everything there.

But zigbee2mqtt does not work.

This is what I am getting:

https://pastebin.com/66a214ME

Everything is ok, the port, the permissions, etc, but it does not work. Same happens in hassio addon.

I connected it directly to one of the NUC USB ports, using a powered hub and through an extension cable. Same result.

It worked once with this setup, I was able to start an interview with an Ikea switch, but never again.

Any ideas?

Thanks.

Bug Report

What happened

What did you expect to happen

How to reproduce it (minimal and precise)

Debug Info

zigbee2mqtt version: CC253X firmware version:

crystallero commented 4 years ago

I am seeing this in the host too:


[41651.967554] eth0: renamed from vethf989487
[41651.984067] hassio: port 6(veth459ed60) entered blocking state
[41651.984076] hassio: port 6(veth459ed60) entered forwarding state
[42314.441243] cdc_acm 2-1.7:1.0: failed to set dtr/rts
[42314.682897] hassio: port 6(veth459ed60) entered disabled state
[42314.683099] vethf989487: renamed from eth0
[42314.770924] hassio: port 6(veth459ed60) entered disabled state
[42314.775674] device veth459ed60 left promiscuous mode
[42314.775683] hassio: port 6(veth459ed60) entered disabled state
[42315.136450] hassio: port 6(veth44049d9) entered blocking state
[42315.136455] hassio: port 6(veth44049d9) entered disabled state
[42315.136650] device veth44049d9 entered promiscuous mode
[42315.136961] hassio: port 6(veth44049d9) entered blocking state
[42315.136965] hassio: port 6(veth44049d9) entered forwarding state
[42315.151033] IPv6: ADDRCONF(NETDEV_CHANGE): veth44049d9: link becomes ready
[42315.655919] hassio: port 6(veth44049d9) entered disabled state
[42315.660033] eth0: renamed from veth73a873b
[42315.679129] hassio: port 6(veth44049d9) entered blocking state
[42315.679139] hassio: port 6(veth44049d9) entered forwarding state
[42324.681301] cdc_acm 2-1.7:1.0: failed to set dtr/rts
[42410.185871] cdc_acm 2-1.7:1.0: failed to set dtr/rts
[42417.865803] cdc_acm 2-1.7:1.0: failed to set dtr/rts
[42502.346243] cdc_acm 2-1.7:1.0: failed to set dtr/rts
[42511.050343] cdc_acm 2-1.7:1.0: failed to set dtr/rts```
GMFalka commented 4 years ago

@crystallero

I have the same problem! So its probably not just on your end.

Do you see the belowed log repeating? (sudo journalctl -f)

Repeating in log:

kernel: usb 3-12: new full-speed USB device number 50 using xhci_hcd
kernel: usb 3-12: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
kernel: usb 3-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 3-12: Product: TI CC2531 USB CDC
kernel: usb 3-12: Manufacturer: Texas Instruments
kernel: usb 3-12: SerialNumber: __0X00124B001936940B
kernel: cdc_acm 3-12:1.0: ttyACM0: USB ACM device
mtp-probe[9324]: checking bus 3, device 50: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-12"
mtp-probe[9324]: bus: 3, device: 50 was not an MTP device
snapd[622]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
mtp-probe[9328]: checking bus 3, device 50: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-12"
b mtp-probe[9328]: bus: 3, device: 50 was not an MTP device

When starting zigbee2mqtt:

usb 3-13: USB disconnect, device number 52
kernel: cdc_acm 3-13:1.0: failed to set dtr/rts_
kernel: usb 3-13: new full-speed USB device number 53 using xhci_hcd
kernel: usb 3-13: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
kernel: usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 3-13: Product: TI CC2531 USB CDC
kernel: usb 3-13: Manufacturer: Texas Instruments
kernel: usb 3-13: SerialNumber: __0X00124B001936940B
kernel: cdc_acm 3-13:1.0: ttyACM0: USB ACM device
mtp-probe[9538]: checking bus 3, device 53: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-13"
mtp-probe[9538]: bus: 3, device: 53 was not an MTP device
snapd[622]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug
mtp-probe[9541]: checking bus 3, device 53: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-13"
mtp-probe[9541]: bus: 3, device: 53 was not an MTP device

maybe this is the problem? kernel: cdc_acm 3-13:1.0: failed to set dtr/rts_

@Koenkk Please save us! :)

crystallero commented 4 years ago

The weird thing is that I keep seeing the USB disappearing in the host machine. Sometimes the USB green led even goes off. Is it a hardware issue? Or maybe the NUC USB host? I think I read that @Koenkk uses zigbee2mqtt in a NUC too, so I guess that it should work flawlessly

This is so frustrating :(

GMFalka commented 4 years ago

The weird thing is that I keep seeing the USB disappearing in the host machine. Sometimes the USB green led even goes off. Is it a hardware issue? Or maybe the NUC USB host? I think I read that @Koenkk uses zigbee2mqtt in a NUC too, so I guess that it should work flawlessly

This is so frustrating :(

Im also seeing in the journalctl log thst it disconnects and reconnect every few minutes. Consistant interval. I don't think it's a faulty hw. I was using this stick from the same PC, same usb port. Only differenfe is the fresh install of Ubuntu 19.10. Even tried using the old zigbee install folder. Didn't change the error msg.

Also modem manager is purged from my system.

oklih commented 4 years ago

I also have this problem, I cant find what to do to get it to work. Pulling out the USB, sometimes get it back online. Just moved to docker with SSD from an SDcard.

dfsx1 commented 4 years ago

As I reported in https://github.com/Koenkk/zigbee2mqtt/issues/2897#issuecomment-583101035 I got it at least starting up again after pulling the USB out and quickly back in, 1 second before starting the docker container. But all pairing fails and it it very unstable (the docker container crashes periodically). I even tried pulling the previous 1.9.0 zigbee2mqtt docker release, but the issue persists?!

oklih commented 4 years ago

So i had a RFLink also attached to a usb port. I pulled it out and changed the tty port for the Zigbee2mqtt device. Now I have a different error along with the old one! Sorry if I wrongly put in the log.

2020-02-07T00:24:47: PM2 log: Launching in no daemon mode 2020-02-07T00:24:47: PM2 log: App [npm:0] starting in -fork mode- 2020-02-07T00:24:47: PM2 log: App [npm:0] online zigbee2mqtt@1.10.0 start /zigbee2mqtt-1.10.0 node index.js zigbee2mqtt:info 2020-02-07 00:24:50: Logging to console and directory: '/share/zigbee2mqtt/log/2020-02-07.00-24-50' filename: log.txt zigbee2mqtt:info 2020-02-07 00:24:51: Starting zigbee2mqtt version 1.10.0 (commit #unknown) zigbee2mqtt:info 2020-02-07 00:24:51: Starting zigbee-herdsman... (node:58) UnhandledPromiseRejectionWarning: Error: SREQ '--> ZDO - activeEpReq - {"dstaddr":0,"nwkaddrofinterest":0}' failed with status '194' (expected '0') at Znp. (/zigbee2mqtt-1.10.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:246:27) at Generator.next () at fulfilled (/zigbee2mqtt-1.10.0/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:5:58) (node:58) 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) (node:58) [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. zigbee2mqtt:error 2020-02-07 00:25:02: Error while starting zigbee-herdsman zigbee2mqtt:error 2020-02-07 00:25:02: Failed to start zigbee zigbee2mqtt:error 2020-02-07 00:25:02: Exiting... zigbee2mqtt:error 2020-02-07 00:25:02: Error: AREQ - ZDO - activeEpRsp after 10000ms at Timeout._onTimeout (/zigbee2mqtt-1.10.0/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24) at listOnTimeout (internal/timers.js:531:17) at processTimers (internal/timers.js:475:7)

Koenkk commented 4 years ago

Make sure to check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start

GMFalka commented 4 years ago

Make sure to check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start

All checked. Stick is recognized on the correct port User has write access to the same port. Tried the reset button. Modem manager is purged

Koenkk commented 4 years ago

@GMFalka can you post the log when running with zigbee herdsman debug logging enabled?

To enable herdsman debug logging, see https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

GMFalka commented 4 years ago

@GMFalka can you post the log when running with zigbee herdsman debug logging enabled?

To enable herdsman debug logging, see https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

Yes sir. Tonight as soon as I get home. I have a debug log at hand with the docker version, but probably you need a non-dockerized. :)

dfsx1 commented 4 years ago

With debug I see multiple times:

serialport/bindings/unixRead read error [Error: EAGAIN: resource temporarily unavailable, read] { errno: -11, code: 'EAGAIN', syscall: 'read' }

and also:

zigbee-herdsman:adapter:zStack:znp:error Error while parsing to ZpiObject 'RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 5. Received 6

GMFalka commented 4 years ago

I have the same error on docker with debug btw 

herdsman:adapter:zStack:unpi:parser --- parseNext []
2020-02-07T13:00:49.206Z serialport/stream _read reading { start: 142, toRead: 65394 }
2020-02-07T13:00:49.208Z serialport/binding-abstract read
2020-02-07T13:00:49.208Z serialport/bindings/unixRead Starting read
2020-02-07T13:00:49.209Z serialport/bindings/unixRead read error [Error: EAGAIN: resource temporarily unavailable, read] {
  errno: -11,
  code: 'EAGAIN',
oklih commented 4 years ago

Hi All, I have temp installed Hass.io on a SD card again and restored my backup. After changing and updating the system again, it still did not work. So I read somewhere that a reflash of the cc2531 did the trick. looks like it is working again. Now I have reconnected everything and is working fine. I don't think i will be going back to docker for now. untill it is better supported and I have better understanding of docker! (lol)

dfsx1 commented 4 years ago

@oklih Thank you, reflashing the CC2531 also seems to work for me :)

GMFalka commented 4 years ago

I will try to reflash the stick.

I saw other new tickets with the same error we have. Maybe an ubuntu update? Strange that a lot of ppl have the same problem out of the blue

papperone commented 4 years ago

hi, I am trying to have zigbee2mqtt running on a windows 10 pc but it fails with the same error I do see here; I'm using a CC2530 with latest coordinator firmware loaded, what can I try to do to understand the reason of this failure? I can only add I donwload latest jnode (12.15-0 LTS) as the 10 LTS (as suggested in zigbee2mqtt instructions) is not available for download

PS: I can add that the same dongle on a RPi of a friend of mine with Hassio + zigbee2mqtt addon works perfectly but I do need to have it run on my Windows PC

papperone commented 4 years ago

I will try to reflash the stick.

I saw other new tickets with the same error we have. Maybe an ubuntu update? Strange that a lot of ppl have the same problem out of the blue

I have exactly the same but on Windows10 SO so cannot be linked to Ubuntu....

crystallero commented 4 years ago

I reflashed the stick and it still doesn't work.

I tried in an old laptop (same Ubuntu version) and seemed to work in the beginning. But it stopped working after a while :(

Koenkk commented 4 years ago

To all: in case you have this issue please provide the herdsman debug logging, otherwise I cannot help (https://github.com/Koenkk/zigbee2mqtt/issues/2899#issuecomment-583283159). Post it on pastebin.com and link it here.

papperone commented 4 years ago

here is my log (the only one I could have found) https://pastebin.com/6ww6hzYi if you need other one thanks to let me know where I shoudl look for...

Koenkk commented 4 years ago

This log will only be logged to the screen when running with the npm start mentioned in https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

murjam commented 4 years ago

Here's my log: https://pastebin.com/5RRk2H65 :bowing_man:

papperone commented 4 years ago

This log will only be logged to the screen when running with the npm start mentioned in https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

how can I run the below under windows CMD window, I do not understand?

To enable debug logging for Zigbee-herdman start zigbee2mqtt with: DEBUG=zigbee-herdsman* npm start. Zigbee-herdsman is the Zigbee library where Zigbee2mqtt is based up-on

MarcSN311 commented 4 years ago

I had the same problems some users were mentioning. when running hersman with debug settings I am getting an other error message instead of Error: AREQ - SYS - resetInd after 30000ms

https://pastebin.com/fmd9yVsK

It seems to be working now, after pulling the stick and plugging it back in.

Koenkk commented 4 years ago

@papperone 

setx DEBUG "zigbee-herdsman:*"
npm start
Koenkk commented 4 years ago

So for the people having this issue, please fill in the following questionnaire:

papperone commented 4 years ago

here it is:

https://pastebin.com/Zunz9tNC

Koenkk commented 4 years ago

@papperone for the CC2530 you need to set rtscts: false (see docs: https://www.zigbee2mqtt.io/information/supported_adapters.html#texas-instruments-cc2530-optionally-with-a-cc2591-or-cc2592-rf-frontend)

MarcSN311 commented 4 years ago
GMFalka commented 4 years ago

Questionnaire:

  • What kind of adapter is it? (CC2531 or CC2530) CC2531
  • What firmware is flashed on it? CC2531_DEFAULT_20190608
  • Did you ever manage to start Zigbee2mqtt with this adapter? Yes. Worked VERY reliable for months (maybe a year) without a single problem.
  • What is your OS and hardware? If you every manage to start zigbee2mqtt adapter, did you change anything recently to this? A tower PC with intel cpu and ubuntu 18.10. I just did an ssd wipe and installed ubuntu 19.04.
  • Did you check every step of the FAQ? Especially verify that you didn't got a CC2540 instead of a CC2531 Yes!

Heres my log (DEBUG=zigbee-herdsman* npm start)

dvdbosch commented 4 years ago

I had the same problem! If fixed it (wonderly) by changes the usb devices to a different port (apperently it was misconfigured in the configuration file).

murjam commented 4 years ago

I had the same problem and realized I tried to use CC2540 with CC2531 firmware (was thinking I have CC2531) 🙈

Koenkk commented 4 years ago

@MarcSN311 @GMFalka can you try if reflashing the stick solves the issue?

GMFalka commented 4 years ago

@MarcSN311 @GMFalka can you try if reflashing the stick solves the issue?

Hi @Koenkk!

Reflashing the stick worked. Thanks. Now im just waiting for the network to settle. Lots of no network route 205 error, but it does detect bulb states.

Its strange, it got corrupted because of an ubuntu reinstall (maybe docker is the culprit)

kizhaev commented 4 years ago

Having the same issue, here is the log: https://pastebin.com/uWxkph1E

What kind of adapter is it? (CC2531 or CC2530) CC2531

What firmware is flashed on it? CC2531_DEFAULT_20190608

Did you ever manage to start Zigbee2mqtt with this adapter? No

What is your OS and hardware? If you every manage to start zigbee2mqtt adapter, did you change anything recently to this? Hassio + RPi4b

Did you check every step of the FAQ? Especially verify that you didn't got a CC2540 instead of a CC2531 Yes, it is CC2531 for sure.

oklih commented 4 years ago

So a while ago I was on docker, and had trouble with my CC2531 adapter. I moved to hass.io on SD for testing. Al seemed to work fine, but now in a few days I get the same problems I had while I was on docker. Below I put the questionere:

What kind of adapter is it? (CC2531 or CC2530) CC2531

What firmware is flashed on it? CC2531_DEFAULT_20190608, flashed it twice, because I thought that would do the trick to get it working again.

Did you ever manage to start Zigbee2mqtt with this adapter? Yes, was working before al of the updates recently in Home Assistant.

What is your OS and hardware? If you every manage to start zigbee2mqtt adapter, did you change anything recently to this? Hass.io (latest version 105.3) + RPI4B

Did you check every step of the FAQ? Especially verify that you didn't got a CC2540 instead of a CC2531? Yes, I did. also checked online where I bought it. questioning everything by now.

Strange thing is that it sometimes does work with the Xiaomi temp sensors. they give data back, but when I set a wall switch to on I get an error in de log. When I get it to work by pulling out the adapter and pluging it in again. at the moment it is not working again and giving the "Error while starting zigbee-herdsman" error again. I hope there will be a sollution soon. :)

Koenkk commented 4 years ago

@oklih unfortunately this is not something that can be fixed from the zigbee2mqtt side, the issue is that the zigbee2mqtt cannot connect to the adapter, this could e.g. be due to the sniffer firmware being corrupted (try reflashing), wrong port, system issue, etc.

I've improved the error logging in the latest dev branch.

oklih commented 4 years ago

@Koenkk I have found an old backup of my hassio, I downgraded to this snapshot and al started working again. I don't know why, maybe there is an error in my config after the update to 105.x. currently on 104.2. I have updated the add-on of zigbee2mqtt. No errors there yet. Tomorrow I will try the hass.io update to 105.3. Pray that everything will stay the same. Or maybe moving to docker and back again, using the config of the snapshots did mess up my config. Thanx for the advice, I will let everyone know how the update will be.

timdonovanuk commented 4 years ago

Just had this. Was moving my z2m install out of HassOS into a docker running on a host. Brand new z2m install, resigned to the fact I'm going to have to repair everything. Still getting this error:

So for the people having this issue, please fill in the following questionnaire:

What kind of adapter is it? CC1352P-2 What firmware is flashed on it? Latest Did you ever manage to start Zigbee2mqtt with this adapter? Yes, but not in this environment What is your OS and hardware? If you every manage to start zigbee2mqtt adapter, did you change anything recently to this?

oppergod commented 4 years ago

Had the same issue and reflashing the CC2531 fixed the issue for me.

timdonovanuk commented 4 years ago

Have now tried a reflash, no luck. If I could figure out how to turn on zigbee-herdsman debug logging in a docker container I'd provide logs.

I've now switched back to a CC2531 and also now get this..maybe there is something wrong now with Proxmox usb passthrough to docker, but it was working fine. The test -w /dev/ttyACM1 command executes fine also.

cg-n commented 4 years ago

I tried reflashing multiple times on a CC2531 I purchased in the last couple weeks, but had no success on getting it to connect and appear as /tty/ACM0. The flash would by all accounts appear successful (success messages, proper green lights on debugger and CC2531), and then when I would plug in the CC2531 by itself while running dmesg -wH I wouldn't see it recognized. The green light on the CC2531 would stay on for a few seconds and then turn off until I plugged it in again.

I purchased a second CC2531, followed the same instructions for flashing it using the same equipment and environment, and it works perfectly. It shows up in dmesg -wH on connection and I can see it as /tty/ACM0. I feel like a bad batch of CC2531s went out, or at least a batch that isn't compatible with the latest CC2531_DEFAULT_20190608 firmware.

timdonovanuk commented 4 years ago

Still no luck here, although now I can't even get a trusty CC2531 working in a VM. Not sure where it's all gone wrong, as I had it working fine the other day! Will try on bare metal Pi tomorrow.

timdonovanuk commented 4 years ago

Argh! Somehow my docker install had shat the bed. It was persisting z2m invocations even through reboots, and restarting the containers again, even though I didn't background them when I ran them. I don't know how I managed to get it doing that..not experienced it before. I started to wonder why my VM running z2m needed 4GB of ram and was using 100% CPU..and then found this:

2020-02-20 23_31_34-SmarTTY - Docker

I had z2m running over 50 times somehow! No wonder none of my zigbee USB sticks would work! I killed them all off and then z2m started first time. Dooooh.

Tamadite commented 4 years ago

Just for the record: same error code same solution as given above that is reflashing. I reflashed it with the same version I had (ver DEFAULT_20190608). Mine died without no apparent reason in the middle of the day.

stale[bot] commented 4 years ago

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.

joaofl commented 4 years ago

I had the exact same error, which manifested after I replaced my CC2531 with another one of the same, but with external antenna. Tried to re-flash, reinstall the container, followed the FAQ. Nothing worked. What solved my problem was to stop the container, remove the zigbee2mqtt folder, and start it over again.

rm -rf /shared/zigbee2mqtt

@Koenkk There might be something with the state machine at start. Maybe worth checking that.

Koenkk commented 4 years ago

@joaofl not sure where this could come from. Can you provide the herdsman debug logging when the error occurs?

To enable herdsman debug logging, see https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

joaofl commented 4 years ago

Thing is that I can no longer reproduce the issue, but my logs/errors were not any different from the ones mentioned in this thread. Sorry that I'm not able to help much further. If it happens again, I'll make sure to dump the logs here.