Massive Problems - Error on send command to

Robi1010MD commented 4 years ago

at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58) 2020-08-17 19:35:32.191 - error: zigbee.0 (8705) Error on send command to 0x00158d0002cabd36. Error: Error: Command 0x00158d0002cabd36/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC channel access failure' (225)) at ZStackAdapter. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:309:27) --at Generator.next ()

Hi,

i have massive problems with my zigbee devices. I connect them three times but after a while, i got this error message above. Thanks for your help.

toltemp commented 4 years ago

Probably same issue here with "error on send command to".

Worked well all the time but is hardly useable now. Temporary fix ist to unplug and replug the zigbee USB stick. But this "fix" lasts only a short time before the problem occurs again.

`zigbee.0	2020-08-20 11:47:41.189	error	at Timer.processTimers (timers.js:223:10)
zigbee.0	2020-08-20 11:47:41.189	error	at listOnTimeout (timers.js:263:5)
zigbee.0	2020-08-20 11:47:41.189	error	at tryOnTimeout (timers.js:300:5)
zigbee.0	2020-08-20 11:47:41.189	error	at ontimeout (timers.js:436:11)
zigbee.0	2020-08-20 11:47:41.189	error	at Timeout.waiter.timer.setTimeout [as _onTimeout] (/opt/iobroker/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
zigbee.0	2020-08-20 11:47:41.189	error	(10449) Error on send command to 0x7cb03eaa00ad7783. Error: Error: Command 0x7cb03eaa00ad7783/3 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,

`

xxxTODxxx commented 4 years ago

Have the same problem, after the Version 1.2.X it lost mutible times every day the connections to the devices, only if I disconnect the Stick and restart the adapter, it works again. The old version 1.1.3 works fine.

fusionedv commented 4 years ago

Have the same problem, after the Version 1.2.X it lost mutible times every day the connections to the devices, only if I disconnect the Stick and restart the adapter, it works again. The old version 1.1.3 works fine.

Same here

toltemp commented 4 years ago

It looks like this has been caused by 4 Osram Smart+ Plugs I recently added. I have removed those and everything works fine again. Maybe they misbehave in some way?

krumbholz commented 4 years ago

Möglich. Habe seit v1.2 auch diese Probleme und die Osram Smart+ Plugs schalten nicht zuverlässig. Beim Testen reagieren sie, nachdem man sie manuell geschaltet hat auch per Editieren des Schalt-State. Aber aus einem Script heraus wirkt es als seien sie eingeschlafen oder offline und das Script kann keinen Schaltvorgang auslösen.

zigbee.0 (750) Error on send command to 0x7cb03eaa00b09b11. Error: Error: Command 0x7cb03eaa00b09b11/3 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'undefined' (26))
    at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:309:27)
    at Generator.next (<anonymous>)
    at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)

krumbholz commented 4 years ago

Heute mit der Fehlermeldung:

2020-08-31 21:00:25.132  - error: zigbee.0 (750) Error on send command to 0x7cb03eaa00b09b11. Error: Error: Command 0x7cb03eaa00b09b11/3 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no ack' (233))
    at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:309:27)
    at Generator.next (<anonymous>)
    at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)

VG, Steffen

krumbholz commented 4 years ago

Noch ein Update: Das Schalten von ioBroker aus scheitert und die Verbindung ist offensichtlich gestört. Bediene ich die Osram Smart+ Plug direkt am Taster, gehen sofort Availability und State zuverlässig auf true.

Any Ideas? VG, Steffen

krumbholz commented 4 years ago

Heute scheitert die Steuerung mit diesem Fehler:

zigbee.0 (8289) Error on send command to 0x7cb03eaa0a0890c1. Error: Error: Command 0x7cb03eaa0a0890c1/3 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (SREQ '--> AF - dataRequest - {"dstaddr":4782,"destendpoint":3,"srcendpoint":1,"clusterid":6,"transid":124,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,55,0]}}' failed with status '(0x10: MEM_ERROR)' (expected '(0x00: SUCCESS)'))
    at Znp.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:291:27)
    at Generator.next (<anonymous>)
    at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/znp/znp.js:24:58)

VG

kirovilya commented 4 years ago

@krumbholz https://github.com/Koenkk/zigbee2mqtt/issues/4189#issuecomment-683088925 similar to your problem - try updating coordinator firmware

krumbholz commented 4 years ago

Thanks for the hint, but I'm already using the recommended firmware 20190608. Instead I successfully tried the hint I've read elsewhere to use a USB cable to move the CC2531 away from the host. I don't know if this also solves the issues of the other reporters, but my system is fine now. Best regards, Steffen

dernicc commented 4 years ago

Thanks for the hint, but I'm already using the recommended firmware 20190608. Instead I successfully tried the hint I've read elsewhere to use a USB cable to move the CC2531 away from the host. I don't know if this also solves the issues of the other reporters, but my system is fine now. Best regards, Steffen

I have the same issue but I already have a USB cable connected. With the update it seems that the connection to the USB device is lost.

I am running iobroker in the buanet docker container and I am passing the CC2531-stick to the docker container with ENV. It also seems that the container cannot connect to the CC2531.

The console in the container gives the output to dmesg that cdc_acm 2-1.7:1.0: failed to set dtr/rts.

So maybe the update is causing the CC2531 to crash?

Best regards, Nic

krumbholz commented 4 years ago

Thanks for the hint, but I'm already using the recommended firmware 20190608. Instead I successfully tried the hint I've read elsewhere to use a USB cable to move the CC2531 away from the host. I don't know if this also solves the issues of the other reporters, but my system is fine now. Best regards, Steffen

That was true for the most devices. But the Osram Smart+ Plug still looses its connection after some time. If I press the switch button on the plug, it will of cause switch and also reconnects to the network with updating its status value in ioBroker. Also, I can then switch the plug remotely by controlling the switch value in ioBroker. But after some time (surely after several hours, I don't know exactly) the plug becomes unreachable again. This is reproducable. The log is:

2020-09-07 08:08:34.388  - error: zigbee.0 (819) Error on send command to 0x7cb03eaa00b09b11. Error: Error: Command 0x7cb03eaa00b09b11/3 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'undefined' (26))
    at ZStackAdapter.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:309:27)
    at Generator.next (<anonymous>)
    at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)

Best regards, Steffen

tbludau commented 4 years ago

I have the same problems, my whole environment is crashing nearly every 24 hours. I also have Osram Smart+ Plugs.

Best Regards Thomas

tbludau commented 4 years ago

Have the same problem, after the Version 1.2.X it lost mutible times every day the connections to the devices, only if I disconnect the Stick and restart the adapter, it works again. The old version 1.1.3 works fine.

Exactly the same problem, but with version 1.1.3 i had also Problems with my Osram Smart+ Plugs, but they not affectect anything else.

kirovilya commented 4 years ago

https://github.com/Koenkk/zigbee-herdsman/issues/204

krumbholz commented 4 years ago

Status: I've downgraded to iobroker.zigbee v1.1.0. The first 3 days the behaviour stays the same. But on the third day of frustrated ignoring one of my Osram plugs became controllable via script (the script was running all the time and switches the plug on at 9am and off at 9pm). A second plug still behaves like described above... Error log is

2020-09-10 09:22:42.412  - error: zigbee.0 (5076) Error on send command to 0x7cb03eaa0a0890c1. Error: Error: Command 0x7cb03eaa0a0890c1/3 genOnOff.off({}, {"timeout":10000,"manufacturerCode":null,"disableDefaultResponse":false}) failed (Error: Data request failed with error: 'undefined' (26))
    at Endpoint.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:349:23)
    at Generator.throw (<anonymous>)
    at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/model/endpoint.js:6:65)

Strange. Best regards, Steffen

krumbholz commented 4 years ago

Hi, I'd like to give you an update. After one week since my last comment, all my devices work properly. Maybe the zigbee network needs some time to settle all communication paths. I'm still running v1.1.0 but will update to 1.2.1 and will report later what happened. Best regards.

markusfoerster commented 3 years ago

I had the same issue with the CC2531 (most current koenkk firmware) and the Zigbee adapter version 1.2.1. Most devices lost connection in less than 24h. The error messages already posted were pretty much the same on my system. However, I decided the switch to a Conbee II adapter and replaced the CC2531. I added some thermostat Zigbee devices quite recently and those do not work with an older version of the ioBroker Zigbee adapter. So, downgrading was not an option. Everything works like a charm now!

nachon77 commented 3 years ago

A similar problem here. I thought the problem comes from new smart plugs i have installed. (Blitzwolf SHP13). But these new Smart Plugs were the reasons for updating the Adapter. Since then the Adpater crashes regularly. I used the Adapter version 1.1.2 before without any craches. How are your experience now?

arteck commented 3 years ago

for ALL : the adapter version is here not important.. we make more PR's under same Adapter version.. so you can not say : Adapter Version 1.2.1 is buggy

nachon77 commented 3 years ago

@arteck Of course not. I think nobody wanted to say that. We all only try to find the solution or a workaround and try to help to locate the error.

krumbholz commented 3 years ago

Hi, as I said 7 days ago I updated to 1.2.1 again. And ... everything was fine. Until today, when I just enjoyed the view into the zigbee network diagram just 5min before one Osram Smartplug was scripted to be switched. That failed with the typical error:

Error on send command to 0x7cb03eaa00b09b11. Error: Error: Command 0x7cb03eaa00b09b11/3 genOnOff.off({}, {'timeout':10000,'disableResponse':false,'disableDefaultResponse':false,'direction':0,'srcEndpoint':null,'reservedBits':0,'manufacturerCode':null,'transactionSequenceNumber':null}) failed (Data request failed with error: 'undefined' (26))

When I left the server working, it was successful. If I was inspecting it - not. So maybe there is a relation... I don't know. So I'll try to leave the server alone hoping everthing comes back to proper function.

Best regards, Steffen

First1time commented 3 years ago

for artek, with absolutly respekt for you and your team on GIT Hub. I like your performance and i stand full behind you. I read a lot of stuff in your forum and learn a lot.

@ once i´m not a pro in Zigbee. It is more or less a hobby. I don´t want to say there is a bug in version 1.2.1, i will only say there is no communication between Stick & 1.2.1. This communication will be closed after some minutes run time. Why: Situation: Hue Hub Rasp 4 & 3 & 2 On Rasp4: Io Broker Zigbee Node Red All will combined via wifi and node red Sample: Zigbee Osram Motion sensor will controll a Hue lamp and must switch it about the Zigbee adapter. It doesn´t works. All messages and all options, that needs the Zigbeestick, wouldn´t work in my system. It is possible to send messages via Node Red dashboard to lamps, who placed in the hue bridge. But it is not possible to send this messages to lamps who used only the Zigbeeadapter. It is not only Osram smart+ it´s also Aquara ... everthing what run´s only about 1.2.1 & CC2531. I´m not a expert, i can only write what i see. Also i tested the CC2531 stick (i have 7). I flushed all to coordinator firmeware from ti. All sticks will shown in the folder. All sticks works for 10 to 20 minutes. After that you can flash it new, or you can reboot the system. Latest work´s not often. This was all after the update from 1.1.3.

Maybe this message is helpfull for us to fixed the issue. Is it possible to download the 1.1.3 on webspace?

Kind regards, Rainer

tbludau commented 3 years ago

I've a strange problem at the moment. As described from First1time the Osram Plugs made the same problems in my environment. After some minutes everything was much slower then before 1.2.1. After 30 minutes my whole Zigbee environment crashed every time. So I deleted the Osram Power Plugs and everything worked fine. But after some days (~15) I saw that everything reacted slower from day to day, and yesterday (29 days) my whole environment crashed again and nothing worked. It looks like, that this is the same problem, but not so fast, when integrated the Osram plugs. It looks like there is a buffer overflow or something like that anywhere in the code.

iobroker Raspberry 3 zigbee 1.2.1 CC2531 stick

xxxTODxxx commented 3 years ago

I have exact the same problem with the 1.2.1 adapter, I deleted the adapter complete and installed it new, it works for some days and now I have the same problem again. It is not only the Osram Plug, I tried it without the osram plug, but it doesn't helped. I never had disconnect problems with the versions before, only after 1.2.

I'm not the only one with this problem, some friends have the same issus.

I use iobroker on a vm over proxmox with a CC2530 modul.

First1time commented 3 years ago

Hello, i´m not an expert about Zigbee, so sorry about my try and error handling. The last days i tried severeal things with the

Zigbeeadapter & IoBroker
CC2531 sticks
on a Raspberry pi4 But there was only sometimes communication between the CC2531 and the Zigbeeadapter. It makes no diffrent if there are an Osram- or an Hue lamp runs about this stick. In the instances the Adapter was green or yellow, but there was no communication to the devices. (all linked about node red)

So the last try and error was: in all four usb slots one CC2531 flushed for coordinator: (normally it doesen´t works) retry for showing today: pi@Klingone:~ $ ls -l /dev/serial/by-id total 0 lrwxrwxrwx 1 root root 13 Oct 4 18:17 usb-Texas_Instruments_TI_CC2531_USB_CDC _0X00124B00014D7C93-if00 -> ../../ttyACM2 lrwxrwxrwx 1 root root 13 Oct 4 18:17 usb-Texas_Instruments_TI_CC2531_USB_CDC _0X00124B00014D7EA8-if00 -> ../../ttyACM1 lrwxrwxrwx 1 root root 13 Oct 4 18:17 usb-Texas_Instruments_TI_CC2531_USB_CDC _0X00124B00014EF229-if00 -> ../../ttyACM0 lrwxrwxrwx 1 root root 13 Oct 4 18:17 usb-Texas_Instruments_TI_CC2531_USB_CDC _0X00124B0018E1F6FD-if00 -> ../../ttyACM3 pi@Klingone:~ $ ls -l /dev/serial/by-id total 0 lrwxrwxrwx 1 root root 13 Oct 4 19:40 usb-Texas_Instruments_TI_CC2531_USB_CDC_0X00124B00014D7C9B-if00 -> ../../ttyACM2 lrwxrwxrwx 1 root root 13 Oct 4 18:17 usb-Texas_Instruments_TI_CC2531_USBCDC0X00124B00014D7EA8-if00 -> ../../ttyACM1 lrwxrwxrwx 1 root root 13 Oct 4 18:17 usb-Texas_Instruments_TI_CC2531_USB_CDC_0X00124B00014EF229-if00 -> ../../ttyACM0 lrwxrwxrwx 1 root root 13 Oct 4 18:17 usb-Texas_Instruments_TI_CC2531_USBCDC0X00124B0018E1F6FD-if00 -> ../../ttyACM3

After swiching the com Port in the IO Broker on ACM2, the adapter goes green and the devices could be swiched. That was the USB Port 1. All other sticks was removed, the devices works fine. After restart (energie off) the the pi4, nothing works anymore. The reason was, that the USB slot for the communication swich to USB Port 3. Stick in Port3 refresh in the instances, com port AMC0, and it works fine again.

Now there is a break in my mindset and maybe somebody can help me.

A USB Slot is like a com port with a fixed address. In this case not. Is this normal? So it would make no sense to fix the com address an ACM0 or? Thank you for your informations, Rainer

xxxTODxxx commented 3 years ago

Update: I had with the latest Zigbee Version from github since 1 week no disconnects anymore.

tbludau commented 3 years ago

xxxTODxxx are the Osram Power Plug adapter working correctly now too? I had a problem when switching off and on sometimes they are not working properly. Or means your update, you don't have disconnects to to your CC2530 module?

xxxTODxxx commented 3 years ago

tbludau Ich hatte nur Probleme mit dem Disconnect von dem Stick, alle 1-2 Tage hat der Stick die Verbindung zum Zigbee Adapter verloren, mit der Version von Github läuft es wieder problemlos. Ich habe auch einen Osram Plug, bisher schaltet der auch zuverlässig, aber die Reichweite ist bei den Osram Plugs nicht besonders gut. Die BW-SHP13 von Blitzwolf finde ich ganz interessant, bekommt man auch für unter 10€ (banggood), können 16A, Energiemessung und sind deutlich kleiner. Das sind umgelabelte Tuya Plugs. Bisher hatte ich keine Probleme mit denen.

First1time commented 3 years ago

@ once many thanks to the github-team but i seen no fixing of this problem/issue. (only my fiew of this point)

Best regards, Rainer

Tob1a5 commented 3 years ago

I have the same problem. First I had it with my old cc2531 and then decided to buy a conbee II. Conbee worked for ~1 week and now I have the same issue.

2020-11-04 15:54:05.474 - error: zigbee.0 (4685) Error on send command to 0x680ae2fffea47413. Error: Error: Command 0x680ae2fffea47413/1 genLevelCtrl.moveToLevelWithOnOff({"level":254,"transtime":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (no response received)

at DeconzAdapter. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:552:23) at Generator.throw () at rejected (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/deconz/adapter/deconzAdapter.js:25:65)

Adapter Version: 1.3.1

Robi1010MD commented 3 years ago

Ok, thank you for the many contributions. In the meantime I also switched from the cc2531 to the cc2652rb. After a few days the problems came up again, but I changed my hardware setup: I changed the antenna adapter and the antenna. Now this error message appears really rarely and there are no more connection problems.

I also separated the channels of WLAN and ZIGBEE as far as possible. So it seems to be no software problem...

Translation Ok, danke für die vielen Beiträge. Ich bin mittlerweile auch vom cc2531 auf den cc2652rb umgestiegen. Die Probleme sind nach ein paar Tagen auch wieder aufgetaucht, aber ich habe mein Hardware-Setup geändert: ich habe den antennen-adapter und die antenne getauscht. Jetzt taucht diese Fehlermeldung wirklich nur noch selten auf und es gibt keine Verbindungsprobleme mehr.

Darüber hinaus habe ich auch die Kanäle vom WLAN und ZIGBEE soweit wie möglich auseinander gelegt. Es scheint also kein Software-Problem zu sein...

xxxTODxxx commented 3 years ago

I have no connection problems with the version 1.3.x and my CC2530 Modul anymore, works great now.

thebilberry commented 3 years ago

I’m now happy to know that I’m not the only one with this problems. My setup:

RPI 3
CC2531-Stick (FW 20190608)
ioBroker (slave in multihost),
ioBroker.zigbee Ver. 1.3.1
various Aqara sensors (door, temperature, motion)
3x Smart+ Plugs (OSRAM, LEDVANCE) primarily as repeater

Everything went fine for months. But since three or four weeks there are disconnections every few days. (Error on send command to...) My workaround: restart the RPI every 2-3 days.

Is there a solution meanwhile that has helped you in the long term?

krumbholz commented 3 years ago

Hi, same for me. I thought it was somehow related to Osram Plugs (see above) which I've banned for weeks. For Christmas illumination I've added two of them again and they worked in principal. The only issue with them was, that they go into a deep sleep after a while and they were not reacting instantly but after several tries. With update 1.4.0 the whole zigbee network is breaking down with no log entries and not working until doing power on reset. I'll test it with removed Osram Plugs this weekend...

Cheers, Steffen

Domi920 commented 3 years ago

Hi there, also have very similar problems. However, the entire system crashes completely within a few hours. The following error messages, among others: (9742) Non-pingable device 0x (device number here) TRADFRI remote control was last seen '28123.492' seconds ago.

Followed by many other error messages from various devices.

It only helps to unplug the stick (CC2531 stick (FW 20190608)), plug it in again and restart the instance.

What solutions are there already on this topic?

Thanks to everyone now!

asgothian commented 3 years ago

Hi there, also have very similar problems. However, the entire system crashes completely within a few hours. The following error messages, among others: (9742) Non-pingable device 0x (device number here) TRADFRI remote control was last seen '28123.492' seconds ago.

Followed by many other error messages from various devices.

It only helps to unplug the stick (CC2531 stick (FW 20190608)), plug it in again and restart the instance.

What solutions are there already on this topic?

Thanks to everyone now!

Do your error messages contain the keyword “MEM_ERROR” ? If so, the only advice I can give is to swap coordinators and retire the cc2531.

A.

Domi920 commented 3 years ago

Yes, I get error messages with the keyword "MEM_ERROR" about 25 times a day. Sorry for the likely stupid question, but how do I do this exactly? If you mean to completely replace the CC2531 stick as a device with another device, which one do you? Everything had worked wonderfully at first, only for a few days there have been problems.

I have the problem that a Tradfri (E27 or GU10) lamp is switched on for about 10 seconds. Is heard after 10 seconds Error message in the log:

(9742) Error on send command to 0x(device number here). Error: Error: Command 0x(device number here) genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Data request failed with error: 'MAC no resources' (26)) at ZStackAdapter. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:339:27) at Generator.next () at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)

But after these 10 seconds the light switches on. Can that also have something to do with it? Or what can I do about this lag time problem?

Thank you, greetings Dominik!

asgothian commented 3 years ago

The tags 'MEM_ERROR' and 'MAC no resources' indicate that the memory or resources on your cc2531 are running out. This is an indication that the cc2531 is near its performance limit.

So far, i only know of 2 solutions for this problem:

regular restarts including a full reset of the stick
replace the cc2531 with something with a bit more power. I would suggest a TI based board or a cc2538 based stick, not a conbee II.

A.

Domi920 commented 3 years ago

cc2538

Thank you for your response. However, I only connected 9 devices to the stick. That can't be the limit, can it?

How can I do a complete reset of the CC2531 stick? How often should the reset be triggered? Is that also possible with the software, how? Do I then have to pair all devices again?

Does that have anything to do with this problem too? I have the problem that a Tradfri lamp (E27 or GU10) is switched on for about 10 seconds. Heard after 10 seconds. Error message in the log:

(9742) Error sending the command to 0x (device number here). Error: Error: Command 0x (device number here) genOnOff.on ({}, {"Timeout": 10000, "disableResponse": false, "disableRecovery": false, "disableDefaultResponse": false, "direction": 0, "srcEndpoint ": null," reservedBits ": 0," ManufacturerCode ": null," transactionSequenceNumber ": null}) failed (data request failed with error: 'MAC no resources' (26)) at ZStackAdapter. (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:339:27) at Generator.next () at fulfilled (/opt/iobroker/node_modules/zigbee-herdsman/dist/adapter/z-stack/adapter/zStackAdapter.js:24:58)

After these 10 seconds the light comes on.

Can you recommend a ready-made stick that I can "simply" plug into the USB port on the Raspberry Pi4? Without having to solder or do other manual work. Preferably with a long range.

Greetings Dominik

asgothian commented 3 years ago

you can try to flash the stick with a new firmware - this might remove the problem for a while.

Triggering the reset by software is possible, but not automated as far as i know. Pairing again is not needed in this case.

I also think that you are having some kind of wireless interference, which adds to the problems.

Other than that, i would chose one of these (taken from this page)

Electrolama zig-a-zig-ah! (zzh!) slaesh’s CC2652RB stick Texas Instruments LAUNCHXL-CC26X2R1 Texas Instruments LAUNCHXL-CC1352P-2

A.

krumbholz commented 3 years ago

Hi, I can confirm that (re)flashing the stick may solve this issue (may be for the moment). I had really massive problems esp. with Osram Smart Plugs. Then I gave the reflashing a try. I used a raspberry and this https://notenoughtech.com/home-automation/flashing-cc2531-without-cc-debugger/ solution. No repairing needed for me.

Steffen

Domi920 commented 3 years ago

@krumbholz Thank you for your answer! I didn't do the (re) flashing for the time being, because I wanted to find out the error or the cause of the error. Here is my existing ZigBee configuration: 1x Tradfri E27 lamp, 11 watts, 1000 lumens, white spectrum (Ikea 604.084.83) 1x Tradfri GU10 lamp, 5 watt, 400 lumens, white spectrum (Ikea 904.086.03) 1x remote control Tradfri dimmer 2-button, square (Ikea 704.085.95) 1x remote control Tradfri dimmer 5-button, round (Ikea 304.431.24) 1x motion detector Tradfri (Ikea 704.299.13) 4x temperature sensor & humidity sensor, TuYa TS0201

=> 9 devices

With this number of devices, the CC2531 stick could not cope. Delays in switching operations and complete crashes were the rule after just a few hours.

Now my guess is that the temperature and humidity sensors of the ZigBee network or the CC2531 stick were fatal because the data from these sensors was always sent. Currently I have made 3x temperature and humidity sensors from 4x, i.e. shortened 1x piece. The system has been running for 3 days without noticeable failures. I haven't looked at the log in debug mode!

Unfortunately, I'm only just beginning to build my ZigBee network. If a few more devices are added in the near future, the CC2531 stick will no longer do its job reliably. Now I would be interested in a good alternative!

@asgothian Thanks for your links & excerpts! Have browsed the list of your link. Unfortunately I noticed that ordering is not that easy. I'm from Germany and don't have a credit card, some sticks have to be flashed or possibly assembled. You can hardly get any of the particularly good sticks on Ebay or Amazon.

Now my question would be, which stick would be best? My z. B. transmit power, received power, number of devices, plug and play, no flash hardware required, short delivery time to Germany, ...

Has anyone already gained experience & can recommend a stick?

In Amazon I read a lot about the well-known alternative: ConBee II the universal Zigbee USB gateway

However, @asgothian advised me against. Why this? In Amazon you can only read good reviews that have switched from the CC2531 stick to the ConBee 2 stick.

Thank you for everyone's help!

asgothian commented 3 years ago

Has anyone already gained experience & can recommend a stick?

In Amazon I read a lot about the well-known alternative: ConBee II the universal Zigbee USB gateway

However, @asgothian advised me against. Why this? In Amazon you can only read good reviews that have switched from the CC2531 stick to the ConBee 2 stick.

Thank you for everyone's help!

Lets start at the bottom: Why do i advise against the conbee Stick - the support within zigbee-herdsman-converters is still experimental. There are a number of things which do not work properly, and few of the people working on the iobroker.zigbee adapter have a conbee || available to verify and test the issues. What i remember off the top of my head

issues when displaying the map (especially when used with Osram plugs)
issues with some battery powered sensors

As far as getting the units in Germany - i would suggest checking the "marktplatz" area on the iobroker forum for sources which should work without credit cards.

I would stay away from pre-flashed sticks off eBay or amazon. If you go for a pre-flashed stick, stay with the iobroker forum (forum.iobroker.net), there are several people there who will sell flashed sticks, and they usually offer refreshing if you need a newer firmware.

A.

krumbholz commented 3 years ago

Hi @Domi920 , I think that the pure number of devices should not be the reason of this issue. My setup includes 16 devices and is running without any interruption since my (re)flash almost 10 days before. I just restartet the zigbee instance today to produce this log:

2020-12-30 16:16:59.609  - [32minfo[39m: zigbee.0 (17477) starting. Version 1.4.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.3, js-controller: 3.1.6
2020-12-30 16:16:59.935  - [32minfo[39m: zigbee.0 (17477) Starting Zigbee  npm ...
2020-12-30 16:17:00.882  - [32minfo[39m: zigbee.0 (17477) Installed Version: iobroker.zigbee@1.4.0
2020-12-30 16:17:02.957  - [32minfo[39m: zigbee.0 (17477) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190619}}
2020-12-30 16:17:02.962  - [32minfo[39m: zigbee.0 (17477) Disable LED
2020-12-30 16:17:02.986  - [32minfo[39m: zigbee.0 (17477)   --> transmitPower : normal
2020-12-30 16:17:02.995  - [32minfo[39m: zigbee.0 (17477) Currently 16 devices are joined:
2020-12-30 16:17:03.006  - [32minfo[39m: zigbee.0 (17477) 0x680ae2fffed19173 (addr 3112): E1525/E1745 - IKEA TRADFRI motion sensor (EndDevice)
2020-12-30 16:17:03.020  - [32minfo[39m: zigbee.0 (17477) 0x680ae2fffe3e95df (addr 55341): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
2020-12-30 16:17:03.021  - [32minfo[39m: zigbee.0 (17477) 0x680ae2fffe8fe44d (addr 53475): E1746 - IKEA TRADFRI signal repeater (Router)
2020-12-30 16:17:03.024  - [32minfo[39m: zigbee.0 (17477) 0xf0d1b80000128240 (addr 12813): 4058075181472 - LEDVANCE SMART+ panel 60 x 60cm tunable white (Router)
2020-12-30 16:17:03.025  - [32minfo[39m: zigbee.0 (17477) 0x680ae2fffe368ef0 (addr 13899): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
2020-12-30 16:17:03.026  - [32minfo[39m: zigbee.0 (17477) 0x000d6ffffeab2a04 (addr 7324): E1746 - IKEA TRADFRI signal repeater (Router)
2020-12-30 16:17:03.027  - [32minfo[39m: zigbee.0 (17477) 0x00158d0003d4527b (addr 12008): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2020-12-30 16:17:03.029  - [32minfo[39m: zigbee.0 (17477) 0x7cb03eaa0a0890c1 (addr 4782): AB3257001NJ - OSRAM Smart+ plug (Router)
2020-12-30 16:17:03.030  - [32minfo[39m: zigbee.0 (17477) 0x7cb03eaa0a0895e0 (addr 38915): AB3257001NJ - OSRAM Smart+ plug (Router)
2020-12-30 16:17:03.031  - [32minfo[39m: zigbee.0 (17477) 0x00124b001bfbd2bc (addr 57159): SCM-S1 - Blaupunkt Roller shutter (EndDevice)
2020-12-30 16:17:03.032  - [32minfo[39m: zigbee.0 (17477) 0x680ae2fffe8ffddc (addr 12739): E1746 - IKEA TRADFRI signal repeater (Router)
2020-12-30 16:17:03.033  - [32minfo[39m: zigbee.0 (17477) 0x00158d00053fd25d (addr 10637): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
2020-12-30 16:17:03.036  - [32minfo[39m: zigbee.0 (17477) 0x7cb03eaa00b09b11 (addr 12876): AB3257001NJ - OSRAM Smart+ plug (Router)
2020-12-30 16:17:03.038  - [32minfo[39m: zigbee.0 (17477) 0xec1bbdfffeaa4604 (addr 25754): 511.202 - Iluminize Zigbee 3.0 Schalt-Aktor mini 1x230V, 200W/400W (Router)
2020-12-30 16:17:03.039  - [32minfo[39m: zigbee.0 (17477) 0x60a423fffeeec4a8 (addr 13890): E1743 - IKEA TRADFRI ON/OFF switch (EndDevice)
2020-12-30 16:17:03.041  - [32minfo[39m: zigbee.0 (17477) 0x588e81fffec0a52c (addr 43352): 511.202 - Iluminize Zigbee 3.0 Schalt-Aktor mini 1x230V, 200W/400W (Router)
2020-12-30 16:17:03.043  - [32minfo[39m: zigbee.0 (17477) Zigbee started

Regards, Steffen

Domi920 commented 3 years ago

Sorry for the late reply.

@Krumbholz I didn't mean the number of devices, but how much is sent in the background. With lamps, switches, etc., no transmissions are likely to take place in the idle state. The situation is different with temperature and humidity sensors, as these transmit their data at relatively short intervals. This may also overload the stick in some way. If you have to flash the CC2531 stick at regular intervals, that would unfortunately not be an option for me.

I currently have 2 other different ZigBee networks with different devices in my circle of friends. Will gain experience.

At home I have been using a different stick since today: CC2652P https://forum.iobroker.net/topic/39511/verkaufe-neueste-entwicklung-cc2652p-zigbee-stick

Will test the new stick for the next few days.

Hermelinmaster commented 3 years ago

Hi Guys,

Thanks for all the help and hard work.

I am having the same problems as discussed here. But I am not just loosing connection to the Osram Plugs but to my whole network, no device works anymore after i can't reach the first anymore. And this happens multiple times a day and only can be resolved by SSHing onto the machine, sudo iobroker stop, sudo shutdown and then manually cutting power and restarting. This becomes tedious work and I have a 0% reliability if I want to go out for a weekend. I automate my aquarium and animal lights with iobroker. Right now I often get the following "error": 2021-04-29 06:08:35.098 - error: zigbee.0 (947) Send command to 0xccccccfffebb13bd failed with no error code (Cannot request when znp has not been initialized yet)

When I restart my Raspi 4 everything works like a charm for about an hour, after that I get this or the other error messages posted above. If I dont react to that timely the Raspi will cut power to the CC2531 (led off) and other error-messages appear. But I think the initial problem lies in the error posted by me and develops to the other errors.

With zigbee I have not yet found a decent algorithm to debug the system and the network. But since everything always works from a cold start i doubt that it is a hardware problem and suspect software. I also flashed the newest coordinator firmware to the Stick, that helped for a few days, but everything went back to this state now. I only have 15 Devices and max 8m and a wall between the stick and the furthest device. And again, from a cold start everything works like a charm.

So please help me and my haunted network. The wife-approval-factor went significantly downhill. And thanks in advance for any help.

Kind regards, Hermelin

asgothian commented 3 years ago

I am afraid you may be haunted by a memory overflow bug in the base firmware for the CC2531 stick which render the stick inoperable after a certain amount of time. This effect occurs more frequently with networks which have difficult wireless environments and/or a large number of devices.

In the end, you need to post the messages (errors and warnings) you get before the Message you posted above, as this message clearly states that the ZNP section has failed entirely.

I would strongly suggest that you move from the cc2531 to one of the more powerful zigbee coordinator options.

A.

Hermelinmaster commented 3 years ago

Hi there,

Thanks for your reply. I am more than happy to oblige, hope this helpes more than it confuses or wastes time:

2021-04-29 00:43:33.489 - warn: zigbee.0 (947) Stopping to ping 0x7cb03eaa0a08fb9e Plug 01 after 4 ping attempts

2021-04-29 00:43:33.979 - warn: zigbee.0 (947) Stopping to ping 0x7cb03eaa0a08dd87 Plug 01 after 4 ping attempts 2021-04-29 00:43:33.983 - warn: zigbee.0 (947) Stopping to ping 0x7cb03eaa0a0a36f3 Plug 01 after 4 ping attempts 2021-04-29 00:52:29.693 - warn: zigbee.0 (947) Stopping to ping 0x7cb03eaa0a0a3f35 Plug 01 after 4 ping attempts 2021-04-29 00:58:57.347 - warn: zigbee.0 (947) Stopping to ping 0x0017880106ba9230 LTG002 after 4 ping attempts 2021-04-29 01:20:38.704 - warn: zigbee.0 (947) Stopping to ping 0xd0cf5efffe427584 ZBT-ExtendedColor after 4 ping attempts 2021-04-29 01:43:12.843 - warn: zigbee.0 (947) Stopping to ping 0x0017880106ba7b91 LTG002 after 4 ping attempts 2021-04-29 01:43:59.431 - warn: zigbee.0 (947) Stopping to ping 0x0017880106ba7c28 LTG002 after 4 ping attempts 2021-04-29 02:00:03.284 - warn: zigbee.0 (947) Stopping to ping 0x0017880106ba8f79 LTG002 after 4 ping attempts 2021-04-29 02:00:03.794 - warn: zigbee.0 (947) Stopping to ping 0x00124b002114bfc3 GL-C-006 after 4 ping attempts undefined 2021-04-29 06:08:35.098 - error: zigbee.0 (947) Send command to 0xccccccfffebb13bd failed with no error code (Cannot request when znp has not been initialized yet) 2021-04-29 10:15:59.844 - info: zigbee.0 (947) cleaned everything up... 2021-04-29 10:15:59.855 - info: host.raspberrypiiobroker received SIGTERM 2021-04-29 10:15:59.860 - info: host.raspberrypiiobroker stopInstance system.adapter.admin.0 (force=false, process=true) 2021-04-29 10:15:59.860 - info: host.raspberrypiiobroker stopInstance system.adapter.discovery.0 (force=false, process=true) 2021-04-29 10:15:59.861 - info: host.raspberrypiiobroker stopInstance system.adapter.info.0 (force=false, process=false) 2021-04-29 10:15:59.862 - info: host.raspberrypiiobroker stopInstance system.adapter.web.0 (force=false, process=true) 2021-04-29 10:15:59.870 - info: host.raspberrypiiobroker stopInstance system.adapter.history.0 (force=false, process=true) 2021-04-29 10:15:59.870 - info: host.raspberrypiiobroker stopInstance system.adapter.javascript.0 (force=false, process=true) 2021-04-29 10:15:59.871 - info: host.raspberrypiiobroker stopInstance system.adapter.cloud.0 (force=false, process=false) 2021-04-29 10:15:59.871 - info: host.raspberrypiiobroker stopInstance system.adapter.vis.0 (force=false, process=false) 2021-04-29 10:15:59.871 - info: host.raspberrypiiobroker stopInstance system.adapter.alexa2.0 (force=false, process=false) 2021-04-29 10:15:59.871 - info: host.raspberrypiiobroker stopInstance system.adapter.hmip.0 (force=false, process=true) 2021-04-29 10:15:59.872 - info: host.raspberrypiiobroker stopInstance system.adapter.rpi2.0 (force=false, process=false) 2021-04-29 10:15:59.872 - info: host.raspberrypiiobroker stopInstance system.adapter.zigbee.0 (force=false, process=true) 2021-04-29 10:15:59.872 - info: host.raspberrypiiobroker stopInstance system.adapter.node-red.0 (force=false, process=true) 2021-04-29 10:15:59.872 - info: host.raspberrypiiobroker stopInstance system.adapter.openweathermap.0 (force=false, process=false) 2021-04-29 10:15:59.873 - info: host.raspberrypiiobroker stopInstance system.adapter.fullcalendar.0 (force=false, process=true) 2021-04-29 10:15:59.873 - info: host.raspberrypiiobroker stopInstance system.adapter.telegram.1 (force=false, process=false) 2021-04-29 10:15:59.873 - info: host.raspberrypiiobroker stopInstance system.adapter.jarvis.0 (force=false, process=true) 2021-04-29 10:15:59.873 - info: host.raspberrypiiobroker stopInstance system.adapter.iot.0 (force=false, process=false) 2021-04-29 10:15:59.889 - info: host.raspberrypiiobroker stopInstance system.adapter.admin.0 send kill signal 2021-04-29 10:15:59.890 - info: host.raspberrypiiobroker stopInstance system.adapter.discovery.0 send kill signal 2021-04-29 10:15:59.890 - info: host.raspberrypiiobroker stopInstance system.adapter.web.0 send kill signal 2021-04-29 10:15:59.891 - info: host.raspberrypiiobroker stopInstance system.adapter.javascript.0 send kill signal 2021-04-29 10:15:59.891 - info: host.raspberrypiiobroker stopInstance system.adapter.hmip.0 send kill signal 2021-04-29 10:15:59.891 - info: host.raspberrypiiobroker stopInstance system.adapter.zigbee.0 send kill signal 2021-04-29 10:15:59.891 - info: host.raspberrypiiobroker stopInstance system.adapter.fullcalendar.0 send kill signal 2021-04-29 10:15:59.891 - info: host.raspberrypiiobroker stopInstance system.adapter.jarvis.0 send kill signal 2021-04-29 10:16:00.872 - info: host.raspberrypiiobroker stopInstance timeout 1000 system.adapter.node-red.0 killing pid 987 2021-04-29 10:16:00.890 - info: host.raspberrypiiobroker stopInstance system.adapter.admin.0 killing pid 627 2021-04-29 10:16:00.891 - info: host.raspberrypiiobroker stopInstance system.adapter.discovery.0 killing pid 735 2021-04-29 10:16:00.893 - info: host.raspberrypiiobroker stopInstance system.adapter.web.0 killing pid 774 2021-04-29 10:16:00.894 - info: host.raspberrypiiobroker stopInstance system.adapter.javascript.0 killing pid 847 2021-04-29 10:16:00.894 - info: host.raspberrypiiobroker stopInstance system.adapter.hmip.0 killing pid 920 2021-04-29 10:16:00.895 - info: host.raspberrypiiobroker stopInstance system.adapter.zigbee.0 killing pid 947 2021-04-29 10:16:00.895 - info: host.raspberrypiiobroker stopInstance system.adapter.fullcalendar.0 killing pid 1026 2021-04-29 10:16:00.896 - info: host.raspberrypiiobroker stopInstance system.adapter.jarvis.0 killing pid 1053 2021-04-29 10:15:59.888 - info: history.0 (801) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2021-04-29 10:16:03.100 - warn: host.raspberrypiiobroker instance system.adapter.zigbee.0 terminated due to SIGTERM 2021-04-29 10:16:03.100 - info: host.raspberrypiiobroker instance system.adapter.zigbee.0 terminated with code null () 2021-04-29 10:16:03.101 - warn: host.raspberrypiiobroker instance system.adapter.jarvis.0 terminated due to SIGTERM 2021-04-29 10:16:03.101 - info: host.raspberrypiiobroker instance system.adapter.jarvis.0 terminated with code null () 2021-04-29 10:16:03.347 - warn: host.raspberrypiiobroker instance system.adapter.admin.0 terminated due to SIGTERM 2021-04-29 10:16:03.348 - info: host.raspberrypiiobroker instance system.adapter.admin.0 terminated with code null () 2021-04-29 10:16:03.348 - warn: host.raspberrypiiobroker instance system.adapter.web.0 terminated due to SIGTERM 2021-04-29 10:16:03.348 - info: host.raspberrypiiobroker instance system.adapter.web.0 terminated with code null () 2021-04-29 10:16:03.349 - warn: host.raspberrypiiobroker instance system.adapter.hmip.0 terminated due to SIGTERM 2021-04-29 10:16:03.349 - info: host.raspberrypiiobroker instance system.adapter.hmip.0 terminated with code null () 2021-04-29 10:16:03.349 - warn: host.raspberrypiiobroker instance system.adapter.node-red.0 terminated due to SIGTERM 2021-04-29 10:16:03.349 - info: host.raspberrypiiobroker instance system.adapter.node-red.0 terminated with code null () 2021-04-29 10:16:03.350 - warn: host.raspberrypiiobroker instance system.adapter.discovery.0 terminated due to SIGTERM 2021-04-29 10:16:03.350 - info: host.raspberrypiiobroker instance system.adapter.discovery.0 terminated with code null () 2021-04-29 10:16:03.394 - warn: host.raspberrypiiobroker instance system.adapter.fullcalendar.0 terminated due to SIGTERM 2021-04-29 10:16:03.395 - info: host.raspberrypiiobroker instance system.adapter.fullcalendar.0 terminated with code null () 2021-04-29 10:16:03.395 - warn: host.raspberrypiiobroker instance system.adapter.javascript.0 terminated due to SIGTERM 2021-04-29 10:16:03.396 - info: host.raspberrypiiobroker instance system.adapter.javascript.0 terminated with code null () 2021-04-29 10:16:03.533 - info: host.raspberrypiiobroker instance system.adapter.history.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-04-29 10:16:03.534 - info: host.raspberrypiiobroker All instances are stopped. 2021-04-29 10:16:03.559 - info: host.raspberrypiiobroker terminated 2021-04-29 10:18:16.384 - info: host.raspberrypiiobroker iobroker.js-controller version 3.2.16 js-controller starting 2021-04-29 10:18:16.390 - info: host.raspberrypiiobroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-04-29 10:18:16.391 - info: host.raspberrypiiobroker hostname: raspberrypiiobroker, node: v10.24.1 2021-04-29 10:18:16.391 - info: host.raspberrypiiobroker ip addresses: 192.168.0.6 2a02:8070:a190:9c00::38aa 2a02:8070:a190:9c00:daa4:27df:2710:7f3d fe80::ac88:5e63:972c:806c 2021-04-29 10:18:16.946 - info: host.raspberrypiiobroker connected to Objects and States 2021-04-29 10:18:16.985 - info: host.raspberrypiiobroker added notifications configuration of host 2021-04-29 10:18:17.589 - info: host.raspberrypiiobroker 18 instances found 2021-04-29 10:18:17.618 - info: host.raspberrypiiobroker starting 11 instances 2021-04-29 10:18:17.736 - info: host.raspberrypiiobroker instance system.adapter.admin.0 started with pid 629 2021-04-29 10:18:19.838 - info: admin.0 (629) starting. Version 4.2.1 in /opt/iobroker/node_modules/iobroker.admin, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:19.883 - info: admin.0 (629) requesting all states 2021-04-29 10:18:19.883 - info: admin.0 (629) requesting all objects 2021-04-29 10:18:20.499 - info: admin.0 (629) received all objects 2021-04-29 10:18:21.002 - info: admin.0 (629) http server listening on port 8081 2021-04-29 10:18:21.002 - info: admin.0 (629) Use link "http://localhost:8081" to configure. 2021-04-29 10:18:21.691 - info: host.raspberrypiiobroker instance system.adapter.discovery.0 started with pid 749 2021-04-29 10:18:23.128 - info: discovery.0 (749) starting. Version 2.6.1 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:25.707 - info: host.raspberrypiiobroker instance system.adapter.web.0 started with pid 776 2021-04-29 10:18:27.293 - info: web.0 (776) starting. Version 3.4.0 in /opt/iobroker/node_modules/iobroker.web, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:27.612 - info: web.0 (776) socket.io server listening on port 8082 2021-04-29 10:18:27.616 - info: web.0 (776) http server listening on port 8082 2021-04-29 10:18:29.700 - info: host.raspberrypiiobroker instance system.adapter.history.0 started with pid 803 2021-04-29 10:18:31.032 - info: history.0 (803) starting. Version 1.9.12 in /opt/iobroker/node_modules/iobroker.history, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:33.706 - info: host.raspberrypiiobroker instance system.adapter.javascript.0 started with pid 861 2021-04-29 10:18:36.658 - info: javascript.0 (861) starting. Version 5.1.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:36.817 - info: javascript.0 (861) requesting all states 2021-04-29 10:18:36.818 - info: javascript.0 (861) requesting all objects 2021-04-29 10:18:37.330 - info: javascript.0 (861) received all objects 2021-04-29 10:18:37.334 - info: javascript.0 (861) received all states 2021-04-29 10:18:37.394 - info: javascript.0 (861) Start javascript script.js.Kevin.Licht.Deckenlicht_im_Schlafzimmer 2021-04-29 10:18:37.463 - info: javascript.0 (861) script.js.Kevin.Licht.Deckenlicht_im_Schlafzimmer: registered 9 subscriptions and 0 schedules 2021-04-29 10:18:37.463 - info: javascript.0 (861) Start javascript script.js.Kevin.Licht.Deckenlicht_Schreibtisch 2021-04-29 10:18:37.475 - info: javascript.0 (861) script.js.Kevin.Licht.Deckenlicht_Schreibtisch: registered 5 subscriptions and 0 schedules 2021-04-29 10:18:37.499 - info: javascript.0 (861) Start javascript script.js.Kevin.Aquarium.Licht+Pumpen 2021-04-29 10:18:37.519 - info: javascript.0 (861) script.js.Kevin.Aquarium.Licht+Pumpen: registered 0 subscriptions and 8 schedules 2021-04-29 10:18:37.520 - info: javascript.0 (861) Start javascript script.js.Kevin.Klima.Heizung_Boost_Funktion 2021-04-29 10:18:37.524 - info: javascript.0 (861) script.js.Kevin.Klima.Heizung_Boost_Funktion: registered 4 subscriptions and 0 schedules 2021-04-29 10:18:37.525 - info: javascript.0 (861) Start javascript script.js.Kevin.Licht.Licht_Sonic 2021-04-29 10:18:37.529 - info: javascript.0 (861) script.js.Kevin.Licht.Licht_Sonic: registered 0 subscriptions and 2 schedules 2021-04-29 10:18:38.789 - info: vis.0 (890) starting. Version 1.3.8 in /opt/iobroker/node_modules/iobroker.vis, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:39.017 - info: vis.0 (890) vis license is OK. 2021-04-29 10:18:40.717 - info: vis.0 (890) Terminated (NO_ERROR): Without reason 2021-04-29 10:18:41.313 - info: host.raspberrypiiobroker instance system.adapter.vis.0 terminated while should be started once 2021-04-29 10:18:41.696 - info: host.raspberrypiiobroker instance system.adapter.hmip.0 started with pid 917 2021-04-29 10:18:43.449 - info: hmip.0 (917) starting. Version 1.9.0 in /opt/iobroker/node_modules/iobroker.hmip, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:44.370 - info: hmip.0 (917) ws connection opened 2021-04-29 10:18:45.322 - info: hmip.0 (917) hmip adapter connected and ready 2021-04-29 10:18:45.670 - info: host.raspberrypiiobroker instance system.adapter.zigbee.0 started with pid 956 2021-04-29 10:18:48.310 - info: zigbee.0 (956) starting. Version 1.4.4 in /opt/iobroker/node_modules/iobroker.zigbee, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:48.432 - info: zigbee.0 (956) Starting Zigbee npm ... 2021-04-29 10:18:48.908 - info: zigbee.0 (956) Installed Version: iobroker.zigbee@1.4.4 2021-04-29 10:18:49.722 - info: host.raspberrypiiobroker instance system.adapter.node-red.0 started with pid 984 2021-04-29 10:18:50.825 - info: node-red.0 (984) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.node-red, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:51.062 - info: node-red.0 (984) Starting node-red: --max-old-space-size=128 /opt/iobroker/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js 2021-04-29 10:18:52.157 - info: zigbee.0 (956) Coordinator firmware version: {"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20201127}} 2021-04-29 10:18:52.168 - info: zigbee.0 (956) --> transmitPower : normal 2021-04-29 10:18:52.178 - info: zigbee.0 (956) Currently 15 devices are joined: 2021-04-29 10:18:52.200 - info: zigbee.0 (956) 0xccccccfffebb13bd (addr 28355): 44435 - Müller Licht Tint LED Stripe, color, opal white (Router) 2021-04-29 10:18:52.215 - info: zigbee.0 (956) 0xd0cf5efffe427584 (addr 49738): 404000/404005/404012 - Müller Licht Tint LED bulb GU10/E14/E27 350/470/806 lumen, dimmable, color, opal white (Router) 2021-04-29 10:18:52.216 - info: zigbee.0 (956) 0x0017880106ba7b91 (addr 11785): 929001953301 - Philips Hue white ambiance GU10 with Bluetooth (Router) 2021-04-29 10:18:52.217 - info: zigbee.0 (956) 0x0017880106ba7c28 (addr 29429): 929001953301 - Philips Hue white ambiance GU10 with Bluetooth (Router) 2021-04-29 10:18:52.219 - info: zigbee.0 (956) 0x00158d0003479255 (addr 59294): MLI-404011 - Müller Licht Tint remote control (EndDevice) 2021-04-29 10:18:52.221 - info: zigbee.0 (956) 0x90fd9ffffe64e5f4 (addr 51836): 404000/404005/404012 - Müller Licht Tint LED bulb GU10/E14/E27 350/470/806 lumen, dimmable, color, opal white (Router) 2021-04-29 10:18:52.222 - info: zigbee.0 (956) 0x0017880106ba9230 (addr 8501): 929001953301 - Philips Hue white ambiance GU10 with Bluetooth (Router) 2021-04-29 10:18:52.223 - info: zigbee.0 (956) 0x0017880106ba8f79 (addr 48503): 929001953301 - Philips Hue white ambiance GU10 with Bluetooth (Router) 2021-04-29 10:18:52.224 - info: zigbee.0 (956) 0x00124b002114bfc3 (addr 10078): GL-C-006 - Gledopto Zigbee LED Controller WW/CW (Router) 2021-04-29 10:18:52.225 - info: zigbee.0 (956) 0x001788010672904b (addr 2442): 324131092621 - Philips Hue dimmer switch (EndDevice) 2021-04-29 10:18:52.226 - info: zigbee.0 (956) 0x7cb03eaa0a0a3f35 (addr 58789): AB3257001NJ - OSRAM Smart+ plug (Router) 2021-04-29 10:18:52.227 - info: zigbee.0 (956) 0x7cb03eaa0a0a36f3 (addr 7903): AB3257001NJ - OSRAM Smart+ plug (Router) 2021-04-29 10:18:52.228 - info: zigbee.0 (956) 0x7cb03eaa0a08dd87 (addr 28120): AB3257001NJ - OSRAM Smart+ plug (Router) 2021-04-29 10:18:52.229 - info: zigbee.0 (956) 0x7cb03eaa0a08fb9e (addr 59623): AB3257001NJ - OSRAM Smart+ plug (Router) 2021-04-29 10:18:52.230 - info: zigbee.0 (956) 0xec1bbdfffec5d044 (addr 25708): HG06335 - Lidl Silvercrest smart motion sensor (EndDevice) 2021-04-29 10:18:52.231 - info: zigbee.0 (956) Zigbee started 2021-04-29 10:18:53.705 - info: host.raspberrypiiobroker instance system.adapter.fullcalendar.0 started with pid 1023 2021-04-29 10:18:55.011 - info: fullcalendar.0 (1023) starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.fullcalendar, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:57.562 - warn: node-red.0 (984) 29 Apr 10:18:57 - [warn] Projekte inaktiviert: editorTheme.projects.enabled=false 2021-04-29 10:18:57.718 - info: host.raspberrypiiobroker instance system.adapter.jarvis.0 started with pid 1062 2021-04-29 10:18:59.013 - info: jarvis.0 (1062) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.jarvis, node: v10.24.1, js-controller: 3.2.16 2021-04-29 10:18:59.096 - info: jarvis.0 (1062) Socket port detected: 8082 2021-04-29 10:22:46.914 - warn: zigbee.0 (956) Failed to ping 0x7cb03eaa0a0a3f35 Plug 01 2021-04-29 10:23:32.408 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 10:23:33.393 - info: jarvis.0 (1062) Processed 26 devices and discarded 0 devices due to incorrect configuration. See browser console log for more details: ["devices","states","processedDevices","addedDevices","ignoredDevices","discardedDevices"] 2021-04-29 10:26:13.444 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 jarvis 2021-04-29 10:31:41.179 - warn: zigbee.0 (956) Failed to ping 0x0017880106ba7b91 LTG002 2021-04-29 10:31:41.861 - warn: zigbee.0 (956) Failed to ping 0xd0cf5efffe427584 ZBT-ExtendedColor 2021-04-29 10:31:59.355 - warn: zigbee.0 (956) Failed to ping 0x0017880106ba7c28 LTG002 2021-04-29 10:37:13.408 - warn: zigbee.0 (956) Stopping to ping 0x90fd9ffffe64e5f4 ZBT-ExtendedColor after 6 ping attempts 2021-04-29 10:40:24.957 - warn: zigbee.0 (956) Stopping to ping 0xccccccfffebb13bd RGBW Lighting after 6 ping attempts 2021-04-29 10:41:21.526 - warn: zigbee.0 (956) Failed to ping 0x0017880106ba9230 LTG002 2021-04-29 10:41:27.531 - warn: zigbee.0 (956) Failed to ping 0x0017880106ba8f79 LTG002 2021-04-29 10:41:33.530 - warn: zigbee.0 (956) Failed to ping 0x00124b002114bfc3 GL-C-006 2021-04-29 10:41:45.534 - warn: zigbee.0 (956) Failed to ping 0x7cb03eaa0a08fb9e Plug 01 2021-04-29 10:42:21.543 - warn: zigbee.0 (956) Failed to ping 0x7cb03eaa0a0a36f3 Plug 01 2021-04-29 10:42:27.544 - warn: zigbee.0 (956) Failed to ping 0x7cb03eaa0a08dd87 Plug 01 2021-04-29 11:03:26.007 - info: javascript.0 (861) script.js.Kevin.Aquarium.Licht+Pumpen: true 2021-04-29 11:03:26.009 - info: javascript.0 (861) script.js.Kevin.Aquarium.Licht+Pumpen: true 2021-04-29 11:03:32.031 - error: zigbee.0 (956) Send command to 0x7cb03eaa0a0a36f3 failed with no error code (SRSP - AF - dataRequest after 6000ms) 2021-04-29 11:03:38.030 - error: zigbee.0 (956) Send command to 0x7cb03eaa0a08dd87 failed with no error code (SRSP - AF - dataRequest after 6000ms) 2021-04-29 11:17:31.955 - warn: zigbee.0 (956) Stopping to ping 0x7cb03eaa0a0a3f35 Plug 01 after 4 ping attempts 2021-04-29 11:27:27.552 - warn: zigbee.0 (956) Stopping to ping 0x0017880106ba7b91 LTG002 after 4 ping attempts 2021-04-29 11:27:33.552 - warn: zigbee.0 (956) Stopping to ping 0xd0cf5efffe427584 ZBT-ExtendedColor after 4 ping attempts 2021-04-29 11:27:45.554 - warn: zigbee.0 (956) Stopping to ping 0x0017880106ba7c28 LTG002 after 4 ping attempts 2021-04-29 11:32:25.813 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:26.787 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:26.803 - warn: jarvis.0 (1062) Wiederverbinden 2021-04-29 11:32:26.853 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:26.987 - warn: jarvis.0 (1062) transport close 2021-04-29 11:32:26.988 - warn: jarvis.0 (1062) Wiederverbinden.. 2021-04-29 11:32:26.989 - warn: jarvis.0 (1062) Wiederverbinden.. 2021-04-29 11:32:28.805 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:28.816 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:28.817 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:28.895 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:29.392 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:30.200 - info: jarvis.0 (1062) Processed 26 devices and discarded 0 devices due to incorrect configuration. See browser console log for more details: ["devices","states","processedDevices","addedDevices","ignoredDevices","discardedDevices"] 2021-04-29 11:32:32.782 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 jarvis 2021-04-29 11:32:32.866 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:33.216 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:32:34.028 - info: jarvis.0 (1062) Processed 26 devices and discarded 0 devices due to incorrect configuration. See browser console log for more details: ["devices","states","processedDevices","addedDevices","ignoredDevices","discardedDevices"] 2021-04-29 11:32:34.604 - error: zigbee.0 (956) Send command to 0x7cb03eaa0a08dd87 failed with no error code (SRSP - AF - dataRequest after 6000ms) 2021-04-29 11:34:58.895 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:35:02.866 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:35:04.025 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 jarvis 2021-04-29 11:35:07.441 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:35:57.542 - warn: zigbee.0 (956) Stopping to ping 0x0017880106ba9230 LTG002 after 4 ping attempts 2021-04-29 11:36:27.547 - warn: zigbee.0 (956) Stopping to ping 0x0017880106ba8f79 LTG002 after 4 ping attempts 2021-04-29 11:36:33.548 - warn: zigbee.0 (956) Stopping to ping 0x00124b002114bfc3 GL-C-006 after 4 ping attempts 2021-04-29 11:36:45.551 - warn: zigbee.0 (956) Stopping to ping 0x7cb03eaa0a08fb9e Plug 01 after 4 ping attempts 2021-04-29 11:37:13.698 - info: web.0 (776) <==Disconnect system.user.admin from ::ffff:192.168.0.7 2021-04-29 11:37:15.559 - warn: zigbee.0 (956) Stopping to ping 0x7cb03eaa0a0a36f3 Plug 01 after 4 ping attempts 2021-04-29 11:37:21.559 - warn: zigbee.0 (956) Stopping to ping 0x7cb03eaa0a08dd87 Plug 01 after 4 ping attempts 2021-04-29 13:16:42.929 - info: web.0 (776) ==>Connected system.user.admin from ::ffff:192.168.0.234 2021-04-29 13:16:43.536 - info: jarvis.0 (1062) Processed 26 devices and discarded 0 devices due to incorrect configuration. See browser console log for more details: ["devices","states","processedDevices","addedDevices","ignoredDevices","discardedDevices"] 2021-04-29 13:16:55.331 - error: zigbee.0 (956) Send command to 0x7cb03eaa0a08dd87 failed with no error code (SRSP - AF - dataRequest after 6000ms) 2021-04-29 13:17:01.333 - error: zigbee.0 (956) Send command to 0x7cb03eaa0a08dd87 failed with no error code (SRSP - AF - dataRequest after 6000ms)

There you can see a cold restart at 10:15 am and network failure after 11am. Lots of warnings and errors. The 956 error happens everytime i want to switch a state and it is not working.

I am thinking about using a different coordinator. But a) I am hesitant since CC2531 should work with this small a network and i don't know if anything else really solves this problem b) the raw signal stregth is enough by the CC2531 c) i fear the work of getting rid of my old bindings, pair all devices to the new coordinator, assemble new groups and changing all my skripts d) the alternatives seem to be quite expensive (on Amazon ~100€) and e) I am unsure which alternative fits best my needs and would require extensive research again (I am leaning towards CC2538 ?). If it becomes necessary to get a more expensive coordinator for this small a network, then the recommendation for the CC2531 should be scrapped imo. Plus, this becomes quite a lot more expensive than using a commercial Gateway...

Thanks again. Best regards, Hermelin

asgothian commented 3 years ago

please post Logs please in code tags
please remove log lines which are of no interest before posting (i.e. any line which references an adapter instance other than "zigbee.0"
The CC3531 is not on the recommended list of Coordinators anymore for some time now. (see here: https://www.zigbee2mqtt.io/information/supported_adapters.html)
In addition to all this, you also need to check your wireless situation. DECT Phones, Microwaves and 2.4 GHz WIFI networks use the same frequency range as the zigbee Network. Choosing the best Channel for Zigbee / WLan is essential for stable operation.
The Alternatives are by no means as expensive as you write. The CC26X2R1 can be obtained for under EUR 50 directly from TI. The CC2538 versions are offered on various places (NOT AMAZON) for prices between EUR 25 and 50)
Your scripts will not require changing, as the State ID is fixed to the HW id of the Zigbee Device. And since you have few devices, i would estimate that a change will take max 1 hr for the entire network. I recently had to change the channel on my Zigbee Network due to wireless interference. With a network of 75 devices, i was done after 20 minutes.
Restarting the entire ioBroker will not alleviate your problems since they seem to be caused by the communication between the zigbee Coordinator, the Devices and the Zigbee Adapter. A restart of the entire PI will only reset the Hardware if the device is completely powered down for at least 30 seconds. Else the USB devices will only trigger a soft reset which will NOT fix a firmware related issue on the CC2531.

A.

ioBroker / ioBroker.zigbee

Massive Problems - Error on send command to #731

2021-04-29 00:43:33.489 - warn: zigbee.0 (947) Stopping to ping 0x7cb03eaa0a08fb9e Plug 01 after 4 ping attempts