No communication after Update (nothing works anymore)

Maschler commented 3 years ago

Describe the bug

Hello,

after I made an update from the Raspi, unfortunately nothing works anymore. In the Deconz representation no more connections between the individual components arise. In the Phoscon APP all components are there, but they are grayed out. Restart etc. I have already tried everything. I have also pulled the Conbee 2 in and out....

Steps to reproduce the behavior

I do not know.

Expected behavior

Normal function after restart.

Screenshots

grafik

Environment

Host system: Raspberry Pi 4 4gb
Running method: I am using Raspbian Buster Desktop form https://phoscon.de/en/raspbee/sdcard
Firmware version: 26660700
deCONZ version: 2.07.01 / 8.12.2020
Device: ConBee II
Do you use an USB extension cable: no
Is there any other USB or serial devices connected to the host system? If so: Which? --> HDD

deCONZ Logs

16:16:11:508 APS-DATA.confirm id: 238, status: 0xA7 NO_ACK 16:16:12:263 APS-DATA.request id: 72, addrmode: 0x03, addr: 0x680ae2fffeee74fd, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00 16:16:13:339 APS-DATA.confirm id: 72, status: 0xE1 16:16:14:063 APS-DATA.request id: 80, addrmode: 0x03, addr: 0x14b457fffec4e9df, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00 16:16:15:671 Mgmt_Lqi_req zdpSeq: 99 to 0x00212EFFFF05B0C4 start index 0 16:16:15:671 APS-DATA.request id: 88, addrmode: 0x03, addr: 0x00212effff05b0c4, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x04 16:16:15:694 APS-DATA.confirm id: 88, status: 0x00 SUCCESS 16:16:15:695 APS-DATA.confirm request id: 88 -> confirmed, timeout 34641696 16:16:15:703 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 117, rssi: 32 16:16:15:704 APS-DATA.indication request id: 88 -> finished 16:16:15:705 APS-DATA.request id: 88 erase from queue 16:16:15:706 ZDP status = 0x00 -> SUCCESS 16:16:15:706 ZDP Mgmt_Lqi_rsp zdpSeq: 99 from 0x00212EFFFF05B0C4 total: 3, startIndex: 0, listCount: 1 16:16:15:707 neighbor: 0x00212EFFFF009CAC (0xD6BE), LQI: 228, relation: 0x02 rxOnWHenIdle: 1 16:16:19:031 Mgmt_Lqi_req zdpSeq: 100 to 0x00212EFFFF05B0C4 start index 1 16:16:19:032 APS-DATA.request id: 103, addrmode: 0x03, addr: 0x00212effff05b0c4, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x04 16:16:19:046 APS-DATA.confirm id: 103, status: 0x00 SUCCESS 16:16:19:047 APS-DATA.confirm request id: 103 -> confirmed, timeout 35068280 16:16:19:051 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 108, rssi: 41 16:16:19:052 APS-DATA.indication request id: 103 -> finished 16:16:19:052 APS-DATA.request id: 103 erase from queue 16:16:19:053 ZDP status = 0x00 -> SUCCESS 16:16:19:053 ZDP Mgmt_Lqi_rsp zdpSeq: 100 from 0x00212EFFFF05B0C4 total: 3, startIndex: 1, listCount: 1 16:16:19:053 neighbor: 0x7CB03EAA00A338E0 (0xE6E7), LQI: 252, relation: 0x02 rxOnWHenIdle: 1 16:16:22:391 Mgmt_Lqi_req zdpSeq: 101 to 0x00212EFFFF05B0C4 start index 2 16:16:22:392 APS-DATA.request id: 118, addrmode: 0x03, addr: 0x00212effff05b0c4, profile: 0x0000, cluster: 0x0031, ep: 0x00 -> 0x00 queue: 1 len: 2 tx.options 0x04 16:16:22:412 APS-DATA.confirm id: 118, status: 0x00 SUCCESS 16:16:22:413 APS-DATA.confirm request id: 118 -> confirmed, timeout 34631136 16:16:22:422 APS-DATA.indication srcAddr: 0x0000, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x8031, lqi: 138, rssi: -57 16:16:22:424 APS-DATA.indication request id: 118 -> finished 16:16:22:425 APS-DATA.request id: 118 erase from queue 16:16:22:425 ZDP status = 0x00 -> SUCCESS 16:16:22:426 ZDP Mgmt_Lqi_rsp zdpSeq: 101 from 0x00212EFFFF05B0C4 total: 3, startIndex: 2, listCount: 1 16:16:22:427 * neighbor: 0x0017880108330786 (0xCA45), LQI: 85, relation: 0x02 rxOnWHenIdle: 1 16:16:27:551 APS-DATA.indication srcAddr: 0xc26f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -45 16:16:27:552 APS-DATA.request id: 142, addrmode: 0x02, addr: 0xc26f, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 1 len: 12 tx.options 0x04 16:16:27:565 APS-DATA.confirm id: 142, status: 0xD0 16:16:29:767 APS-DATA.indication srcAddr: 0xc26f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 85, rssi: -50 16:16:29:768 APS-DATA.request id: 153, addrmode: 0x02, addr: 0xc26f, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 1 len: 12 tx.options 0x04 16:16:29:874 APS-DATA.confirm id: 153, status: 0xD0 16:16:30:986 APS-DATA.indication srcAddr: 0xd25f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -45 16:16:30:986 APS-DATA.request id: 160, addrmode: 0x02, addr: 0xd25f, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 1 len: 12 tx.options 0x04 16:16:31:006 APS-DATA.confirm id: 160, status: 0xD0 16:16:34:131 0x14B457FFFEC4E9DF error APSDE-DATA.confirm: 0xA7 on task 16:16:34:132 APS-DATA.confirm id: 80, status: 0xA7 NO_ACK 16:16:34:263 APS-DATA.request id: 174, addrmode: 0x03, addr: 0x0017880108330786, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x0B queue: 0 len: 5 tx.options 0x00 16:16:35:340 0x0017880108330786 error APSDE-DATA.confirm: 0xE1 on task 16:16:35:341 APS-DATA.confirm id: 174, status: 0xE1 16:16:36:063 APS-DATA.request id: 182, addrmode: 0x03, addr: 0x14b457fffec4e9df, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00

Additional context

network size:35 number of routers: 4

Mimiix commented 3 years ago

16:16:13:339 APS-DATA.confirm id: 72, status: 0xE1

That's interference :) I recommend using a Extension cable.

Big4SMK commented 3 years ago

I have the exact same issue after an update today. Same firmware and deconz verzion. Only difference is I'm running on Ubuntu in a VM instead of a rpi4. About 1 in 6 devices are connected, but I can't control them. Very annoying as all my lights are on while I want to go to sleep....

Mimiix commented 3 years ago

@Big4SMK please open a seperate issue.

Maschler commented 3 years ago

Hello,

this is strange because i didn't change anything and it worked great before.

I installed a backup back to the SD card yesterday. After starting the Raspberry everything worked right away. At the same time the stick was in the same position as always.

As long as this does not occur again, you can close this.

Thanks :)

Mimiix commented 3 years ago

@Maschler you had a usb hdd instead of the SD before?

Big4SMK commented 3 years ago

Today, I've restored from backup too. Leading me back to software 2.5.80 but still with new firmware 26660700. This got me back control of about 1/3rd of my devices, with still a lot of 0xE1 but less than before. Then I installed a USB extension cable which got me back control of all my devices. Finally I upgraded to 2.09.03 (somehow apt gave me a newer than the 2.07.01 I got yesterday), and things are still working fine.

Looks like the firmware might have changed something for the worse that can be mitigated by a USB extension cable. I'm all good now.

@mimiix, do you want me to log that in a separate issue?

Mimiix commented 3 years ago

@Big4SMK I'd like to have your full issue in a seperate issue, if you are still experiencing issues 😄.

0xE1 can pop up anytime if there's no extension cable. Could be changes in your surroundings (new wifi, changing wifi channels etc.). A restart of the network (with a firmware update or a reboot for example, where the Conbee is out of the air) causes 0xE1 easiliy as there's not connections yet. So it works, but it's crippled.

It should be seen as a broken water-pipe. Yes, it works and you lose water. But eventually it cracks.

jonnycastaway commented 3 years ago

Exactly this issue hits me last 3 times i updates the Conbee2 Firmware. And i ended up 3x to pair all devices again. And also i had to correct my automations in iobroker etc. So in my eyes it's a but because recovering an gateway backup isn't repair the situation for me. So i'm, searching for a way to completely backup the entire system including Conbee2 Stick config so in a disaster fail i can recover everithing.

github-actions[bot] commented 3 years ago

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

github-actions[bot] commented 3 years ago

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

dresden-elektronik / deconz-rest-plugin