request unsuccess: 17 #184

todfox · 2018-07-07T14:32:12Z

It would be grand if this bug could be squashed.

 {"message":"request unsuccess: 17","stack":"Error: request unsuccess: 17
    at /opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/zdo.js:46:21
    at CcZnp.<anonymous> (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:257:13)
    at Object.onceWrapper (events.js:315:30)
    at emitOne (events.js:116:13)
    at CcZnp.emit (events.js:211:7)
    at CcZnp._mtIncomingDataHdlr(/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:357:14)
    at /opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:333:22
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)"}

Koenkk · 2018-07-07T20:10:09Z

Are you running the latest firmware from: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/CC2531/bin ?

todfox · 2018-07-07T20:19:07Z

Yup. But I can reflash it if you think that that is the reason.

…

On Sat, Jul 7, 2018 at 2:10 PM Koen Kanters ***@***.***> wrote: Are you running the latest firmware from: https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/CC2531/bin ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#184 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXritnvJAyfvrdrPQZ347hKlOmjAz3Wwks5uERWjgaJpZM4VGYOL> .

Koenkk · 2018-07-07T21:11:28Z

If you are on the latest version it is ok, does zigbee2mqtt still work after this error?

todfox · 2018-07-07T22:13:37Z

Yes. That said, I have noticed that pairing becomes near impossible thereafter.

…

On Sat, Jul 7, 2018 at 3:11 PM Koen Kanters ***@***.***> wrote: If you are on the latest version it is ok, does zigbee2mqtt still work after this error? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#184 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXrith_dbAYYAmKwXLHep8T35hkuS9T2ks5uESQCgaJpZM4VGYOL> .

todfox · 2018-07-09T05:54:00Z

After a couple days of faffing around, I re-flashed the sniffer. All seems to be working now.

todfox · 2018-07-09T19:23:41Z

It's back!

todfox · 2018-07-09T19:24:02Z

2018-7-9 13:21:32 INFO
        {"message":"request unsuccess: 17","stack":"Error: request unsuccess: 17
    at /opt/zigbee2mqtt/node_modules/zigbee-shepherd/lib/components/zdo.js:46:21
    at CcZnp.<anonymous> (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:257:13)
    at Object.onceWrapper (events.js:315:30)
    at emitOne (events.js:116:13)
    at CcZnp.emit (events.js:211:7)
    at CcZnp._mtIncomingDataHdlr (/opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:357:14)
    at /opt/zigbee2mqtt/node_modules/cc-znp/lib/ccznp.js:333:22
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)"}

Koenkk · 2018-07-10T16:48:36Z

Ok, lets gather more information on when this happens.

Do you still receive update of the devices after this error?

todfox · 2018-07-16T16:35:12Z

I have found that after flashing the device the error goes away and all is well.

Sonsi79 · 2018-08-02T18:43:51Z

Today im also getting this error during start of zigbee2mqtt.
I have completely update zigbee2mqtt on dev branch.

Should i try to reflash again? Im on newest version of firmware

Sonsi79 · 2018-08-02T19:01:57Z

strange. during try of pair there is absolutely no message on screen or log... I have try to pair 2 new devices after start zigbee2mqtt.
Here is my debug log.

Maybe i should go back to master branch and try?
log.txt

Sonsi79 · 2018-08-02T19:13:54Z

Ok. I have reflash the stick and everything works. The Error message is gone and im able to pair new devices... sorry for confusing you

kirovilya · 2018-08-03T06:29:12Z

Because it is fixed by a reflash, then I think this is due to the memory in the chip. And maybe with the number of connected devices.

tb-killa · 2018-08-03T16:49:56Z

What the Status about move Devices to zigbee shepherd alone and have maximum of availabel memory ?

Koenkk · 2018-08-04T16:55:39Z

@tb-killa no update on that yet, if I remember correctly we also need Z-stack 3.0 for that. #211

ryanbeaton · 2018-08-06T07:52:05Z

@Koenkk you said you changed NWK_MAX_DEVICE_LIST=0
in issue #134 from @kirovilya find. Did that not work?

_{Sent with GitHawk}

Koenkk · 2018-08-06T14:42:22Z

@ryanbeaton no that didn't work.

cmille34 · 2018-08-13T11:21:30Z

I just got this error again, I just reflashed a couple weeks ago. I was slowly adding new items back in and one of the temp sensors wouldn't pair. Sure enough, I rebooted the zigbee2mqtt docker and found this error:
2018-08-13T02:19:01.503Z - info: Zigbee: allowing new devices to join. 2018-08-13T02:19:01.504Z - info: Connecting to MQTT server at mqtt://192.168.1.104:1883 2018-08-13T02:19:01.574Z - info: zigbee-shepherd ready 2018-08-13T02:19:01.703Z - info: Error: request unsuccess: 17 at /app/node_modules/zigbee-shepherd/lib/components/zdo.js:46:21 at CcZnp.<anonymous> (/app/node_modules/cc-znp/lib/ccznp.js:257:13) at Object.onceWrapper (events.js:315:30) at emitOne (events.js:116:13) at CcZnp.emit (events.js:211:7) at CcZnp._mtIncomingDataHdlr (/app/node_modules/cc-znp/lib/ccznp.js:357:14) at /app/node_modules/cc-znp/lib/ccznp.js:333:22 at _combinedTickCallback (internal/process/next_tick.js:131:7) at process._tickCallback (internal/process/next_tick.js:180:9)

Is there any other firmware i should be trying or is https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/CC2531/bin still the latest?

Koenkk · 2018-08-13T17:00:26Z

@cmille34 how many devices have you paired now?

cmille34 · 2018-08-13T17:03:20Z

@Koenkk 15 devices now. I can't add a 16th because i get that request unsuccess 17 error. I was able to add these 3 devices fine yesterday , then I went to add another one and noticed it wouldn't pair. Reflash and start over or is there any debugging/troubleshooting you would like me to do first?

Sonsi79 · 2018-08-13T17:11:16Z

I was also getting these error for a 2nd time. Reflash fixed again.
I have 18 devices running at the Moment.

Koenkk · 2018-08-13T17:57:11Z

Found out that error code 17 means that the buffer of the CC2531 is full. Honestly I'm a bit lost on how to fix this issue.

@jackchased do you know more about this issue?

cmille34 · 2018-08-13T23:45:42Z

@Koenkk I just reflashed and repaired a bunch of devices again and after the 16th one I get the error 17. Once I get that error 17 I have to reflash and start all over. I guess Ill repair only 15 devices and just stay there until more information comes around about why this keeps happening.

Koenkk · 2018-08-14T16:53:29Z

Lets also see what #211 brings us.

cmille34 · 2018-08-14T16:58:09Z

I got error 17 after only pairing 13 things yesterday. I just went back to using the Xiaomi gateway for now until this matures a little bit more. I have the flashing hardware and a few cc2531 I can try when this gets a little further along.

arteck · 2018-08-14T18:53:45Z

i have 27 devices online, 6 with error code 17... any idea? but all works

tb-killa · 2018-08-20T06:46:13Z

This could be the fault of Power save (sleep Mode).
Please check if you pressed All four Buttons simultan short, this could bring device up and finish your fault check.

arteck · 2018-08-20T06:52:27Z

press one Button help also..

i think can close here

tb-killa · 2018-08-20T07:20:13Z

Yes, sometimes this works, sometimes you have to press All four. Strange device ;)

matchett808 · 2018-08-20T11:45:10Z

Prior to the new firmware - was it producing error messages like this one?

2018-8-20 12:31:57 - error: Zigbee publish to '0x001e5e0902293394', genOnOff - off - {} - null failed with error Error: AF data request fails, status code: 183. APS no ack.

My stick seems to get itself into a state where I can't recover from occasionally (it normally coincides with me messing about with new devices) - I get the error 17 and then things work for 5 minutes before all the devices stop working.

I'm trying to not go for new firmware as I'd need to repair all my devices - but if I have to I'll just wait for the NV_RESTORE firmware (or for it to be ruled out)

arteck · 2018-08-20T16:20:30Z

which device is it ?? 0x001e5e0902293394

matchett808 · 2018-08-20T16:26:56Z

That's just a plug

arteck · 2018-08-20T16:36:55Z

which plug ?? hue ?? osram ??

matchett808 · 2018-08-20T18:20:40Z

Lol, sorry - yeah, it's a hive plug but it's happening (depending on the restart) with all of them (assortment of bulbs etc)

dzungpv · 2018-08-27T11:36:38Z

I have this problem, try all type of firmware from original TI ZNP to the increase buffer size. One reason for this problem is when signal low, for me it often occurs if the signal lower than -60dbm

Koenkk · 2018-08-27T16:01:12Z

@dzungpv do you have this issue with a CC2531 flashed with https://github.com/Koenkk/Z-Stack-firmware/tree/increased_buffer/coordinator/CC2531/bin ?

dzungpv · 2018-08-27T16:30:21Z

@Koenkk yes, it has some more bug like it hang and must reboot PI, I don't know it is zigbee2mqtt or the hardware/firmware

worf0r · 2018-08-28T20:13:58Z

With the iobroker solution error 17 never occurs with the first command sent to a lightbulb. But very often with the second or third command. Even with good signal...

arteck · 2018-08-29T04:58:25Z

only combined with TRADFRI bulb ... did you forget

worf0r · 2018-08-29T08:15:16Z

Not only Tradfri, also Osram, see here: https://forum.iobroker.net/viewtopic.php?f=36&t=14819&start=80#p171563

arteck · 2018-08-29T12:53:32Z

Osram Stripe maybe, only.... my Osram Bulb E14 works..

nic0dk · 2018-08-30T15:34:47Z

@arteck what software are you using to get he map overview? :) running 23 device myself with 1 router, and getting 17 error too :(

update: fixed it with the flashing the stick with the new firmware 👍

Baseje · 2018-08-30T20:23:53Z

Receive the following error since a day:

zigbee2mqtt:info 2018-8-30 22:21:06 Zigbee publish to '0x90fd9ffffed42943', genOnOff - on - {} - null
zigbee2mqtt:error 2018-8-30 22:21:06 Zigbee publish to '0x90fd9ffffed42943', genOnOff - on - {} - null failed with error Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.

Also after updating to the latest firmware of the CC2531, no results...
Any idea?

Koenkk · 2018-08-31T09:33:14Z

@Baseje this is due to an offline device, not an issue with the stick.

Koenkk · 2018-11-09T16:48:35Z

Please let me know if this is still present with the new firmware.

apeeters · 2018-11-20T16:44:23Z

@Koenkk The https://github.com/Koenkk/Z-Stack-firmware/tree/increased_buffer/coordinator/CC2531/bin link is dead. Should we use https://github.com/Koenkk/Z-Stack-firmware/tree/optimize/coordinator/CC2531/bin to fix this issue instead?

Koenkk · 2018-11-20T18:55:39Z

@apeeters please use https://github.com/Koenkk/Z-Stack-firmware/tree/optimize/coordinator (this will be the new firmware, not that the CC2530 firmware is not up yet.)

salopette · 2018-11-20T19:46:04Z

@ Koenkk is this the firmware for the Zigbee stick as a gateway or as a router?

Thank you

Koenkk · 2018-11-21T10:06:32Z

coordinator (gateway). Router firmwares can be found here: https://github.com/Koenkk/Z-Stack-firmware/tree/master/router

alexalex89 · 2018-11-23T15:38:53Z

Is the optimize/coordinator CC2530_CC2591 firmware final? (bin/hex)

Koenkk · 2018-11-23T15:55:23Z

yes

alexalex89 · 2018-11-23T15:56:34Z

I just flashed it and got hundreds of 205 "no network route" errors ... What am I doing wrong? Do I have to re-pair all devices after flashing?

Edit: Got it - thanks :-) It works!

NiNo-213 · 2019-03-05T22:17:05Z

I´ve the same problem mentioned above with my 2 osram smart plug+. how can i find out which firmware ist flashed on my cc2531 stick & how can I update/upgrade the firmware? any ota possibility, coz I bought the stick flashed from somebody and have not the necessary hardware on hand to flash it by meself once again.. thx + b.rgds

Koenkk · 2019-03-06T06:46:17Z

@NiNo-213 http://www.zigbee2mqtt.io/getting_started/flashing_the_cc2531.html#how-to-check-the-installed-firmware-version

For the dev firmware you currently need the CC debugger, once it is in master, you can use the TI serial boot loader tool.

todfox closed this as completed Jul 9, 2018

todfox reopened this Jul 9, 2018

ciotlosm added the problem Something isn't working label Jul 11, 2018

kirovilya mentioned this issue Aug 2, 2018

No Battery State for Xiaomi Smokedetector JTYJ-GD-01LM/BW #150

Closed

arteck mentioned this issue Aug 26, 2018

Problems when sending more than one command to a lightbulb ioBroker/ioBroker.zigbee#45

Closed

Koenkk closed this as completed Nov 9, 2018

request unsuccess: 17 #184

request unsuccess: 17 #184

Comments

todfox commented Jul 7, 2018 • edited by ciotlosm Loading

Koenkk commented Jul 7, 2018

todfox commented Jul 7, 2018 via email

Koenkk commented Jul 7, 2018

todfox commented Jul 7, 2018 via email

todfox commented Jul 9, 2018

todfox commented Jul 9, 2018

todfox commented Jul 9, 2018 • edited by ciotlosm Loading

Koenkk commented Jul 10, 2018

todfox commented Jul 16, 2018

Sonsi79 commented Aug 2, 2018

Sonsi79 commented Aug 2, 2018

Sonsi79 commented Aug 2, 2018

kirovilya commented Aug 3, 2018

tb-killa commented Aug 3, 2018

Koenkk commented Aug 4, 2018

ryanbeaton commented Aug 6, 2018

Koenkk commented Aug 6, 2018

cmille34 commented Aug 13, 2018

Koenkk commented Aug 13, 2018

cmille34 commented Aug 13, 2018

Sonsi79 commented Aug 13, 2018

Koenkk commented Aug 13, 2018

cmille34 commented Aug 13, 2018

Koenkk commented Aug 14, 2018

cmille34 commented Aug 14, 2018

arteck commented Aug 14, 2018 • edited Loading

tb-killa commented Aug 20, 2018

arteck commented Aug 20, 2018 • edited Loading

tb-killa commented Aug 20, 2018

matchett808 commented Aug 20, 2018

arteck commented Aug 20, 2018

matchett808 commented Aug 20, 2018

arteck commented Aug 20, 2018

matchett808 commented Aug 20, 2018

dzungpv commented Aug 27, 2018

Koenkk commented Aug 27, 2018

dzungpv commented Aug 27, 2018

worf0r commented Aug 28, 2018

arteck commented Aug 29, 2018

worf0r commented Aug 29, 2018

arteck commented Aug 29, 2018

nic0dk commented Aug 30, 2018 • edited Loading

Baseje commented Aug 30, 2018 • edited by ciotlosm Loading

Koenkk commented Aug 31, 2018

Koenkk commented Nov 9, 2018

apeeters commented Nov 20, 2018

Koenkk commented Nov 20, 2018

salopette commented Nov 20, 2018

Koenkk commented Nov 21, 2018

alexalex89 commented Nov 23, 2018 • edited Loading

Koenkk commented Nov 23, 2018

alexalex89 commented Nov 23, 2018 • edited Loading

NiNo-213 commented Mar 5, 2019

Koenkk commented Mar 6, 2019

todfox commented Jul 7, 2018 •

edited by ciotlosm

Loading

todfox commented Jul 9, 2018 •

edited by ciotlosm

Loading

arteck commented Aug 14, 2018 •

edited

Loading

arteck commented Aug 20, 2018 •

edited

Loading

nic0dk commented Aug 30, 2018 •

edited

Loading

Baseje commented Aug 30, 2018 •

edited by ciotlosm

Loading

alexalex89 commented Nov 23, 2018 •

edited

Loading

alexalex89 commented Nov 23, 2018 •

edited

Loading