Conbee II with ZHA has started generating a lot of errors and warnings

Since yesterday my log is full of warnings and errors from the ZHA integration. It has been working flawless for 6 months.

The reason for me starting to look in the logs was that my Z-wave entities started to be unresponsive in the UI. I have a USB-dongle for that as well. But there was nothing in the logs indicating any thing bad going on with that integration, instead the log was full with hundreds of messages from the ZHA integration.
So after googling and reading here in the forum I changed the extension cord for my Conbee II USB dongle. And did a restart. Unfortunately the Conbee got a new path and the Z-wave dongle got the old Conbee path. After setting up the integrations again with the new path, the z-wave has been working without problems, but the ZHA integration still reports error every other minutes.
I have also tried moving the Conbee stick around for eliminating interference problems. Even though it seems far-fetched, because I have not change anything in my setup. And the area where the dongle is has been untouched for at least the last 6 month, and I have no neighbors that can have equipment that interferes

This is how my log looks like:

2021-02-28 06:50:16 ERROR (MainThread) [zigpy_deconz.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-02-28 06:50:16 WARNING (MainThread) [zigpy_deconz.api] Serial '/dev/zigbee' connection lost unexpectedly: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-02-28 06:54:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:01:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:09:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:16:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:17:50 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x60'
2021-02-28 07:24:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:25:41 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x65'
2021-02-28 07:31:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:39:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:46:18 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x7e'
2021-02-28 07:46:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 07:49:40 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x83'
2021-02-28 07:53:30 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x8c'
2021-02-28 07:54:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:01:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:09:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:16:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:24:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:31:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:36:35 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xb5'
2021-02-28 08:39:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:46:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 08:50:17 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xbf'
2021-02-28 08:52:27 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xc3'
2021-02-28 08:54:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:01:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:09:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:13:50 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 182, Status: TXStatus.SUCCESS
2021-02-28 09:13:51 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 184, Status: TXStatus.SUCCESS
2021-02-28 09:13:52 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 186, Status: TXStatus.SUCCESS
2021-02-28 09:13:53 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 188, Status: TXStatus.SUCCESS
2021-02-28 09:13:55 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_confirm' command with seq id '0xdc'
2021-02-28 09:14:04 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.write_parameter' command with seq id '0xdd'
2021-02-28 09:14:04 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:16:17 WARNING (MainThread) [zigpy_deconz.zigbee.application] Unexpected transmit confirm for request id 192, Status: TXStatus.SUCCESS
2021-02-28 09:16:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:19:40 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xe3'
2021-02-28 09:24:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:31:22 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xee'
2021-02-28 09:31:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:39:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:46:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 09:54:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:01:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:05:21 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x2d'
2021-02-28 10:09:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:16:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:24:22 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_request' command with seq id '0x47'
2021-02-28 10:24:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:31:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:32:51 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x4e'
2021-02-28 10:39:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:41:03 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x52'
2021-02-28 10:46:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:51:01 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x58'
2021-02-28 10:54:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 10:54:32 ERROR (MainThread) [zigpy_deconz.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-02-28 10:54:32 WARNING (MainThread) [zigpy_deconz.api] Serial '/dev/zigbee' connection lost unexpectedly: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-02-28 11:01:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:05:23 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x6e'
2021-02-28 11:09:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:16:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:23:28 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139947064732208] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
2021-02-28 11:24:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:31:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:38:37 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x8b'
2021-02-28 11:39:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:46:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:51:38 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0x98'
2021-02-28 11:54:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 11:55:28 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xa0'
2021-02-28 12:01:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:05:24 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xb0'
2021-02-28 12:09:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:16:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:24:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:31:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:39:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:46:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:53:38 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xe1'
2021-02-28 12:54:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 12:54:53 ERROR (MainThread) [zigpy_deconz.uart] Lost serial connection: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-02-28 12:54:53 WARNING (MainThread) [zigpy_deconz.api] Serial '/dev/zigbee' connection lost unexpectedly: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2021-02-28 13:01:56 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 13:01:56 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xed'
2021-02-28 13:09:26 WARNING (MainThread) [zigpy_deconz.zigbee.application] No watchdog response
2021-02-28 13:10:47 WARNING (MainThread) [zigpy_deconz.api] No response to 'Command.aps_data_indication' command with seq id '0xf5'

Anyone that have some ideas how to continue the search for this error?

I have the same problem…!
I get the simular in logs: * No response to ‘Command.aps_data_indication’ command with seq id ‘0x44’ and then the Zigbee network becomes unstable or simply stops working. I been trying lost of things like changing channels, reparring devices etc. - But it seems i can get rid of these. Would really like my ZB network to be rocksolid but this is really annoying

I also have similar errors in my log and ZHA has become less reliable since early this year, it used to be solid. Restarting HA Core sometimes causes the ZHA network to stop responding.
The only workaround is to restart the host, which seem to re-initialize things properly.
I am using a Conbee II stick.

The (device disconnected or multiple access on port?) lines in my log was correct.

My problem was that an old Home Assistant version that I used to run in venv before I switched to Docker in a mysterious way had started, and there for also accessing the ConBee. After I killed that instance of HA it has been working flawless again.

I had the same problem too, multiple add/remove of the ConBee II every few seconds either on HomeAssistant Pi4 or Windows 10, 2 different PCs. It was solved by doing a manual firmware update on Windows 10 as explained on https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually
The trick was to enter the command during the 3 seconds between an add and remove USB, listening to the Windows sound. Once the update started it was not removed till the end of the update.
PS C:\Users\Me\AppData\Local\deCONZ\bin> .\GCFFlasher -d COM3 -t 60 -f …/firmware/deCONZ_ConBeeII_0x26680700.bin.GCF
GCFFlasher V3_14 © dresden elektronik ingenieurtechnik gmbh
Reboot device COM3 (ConBee II)
R21B18 Bootloader
Vers: 2.07
build: Jun 17 2019
flashing 164373 bytes: |==============================|
verify: .
SUCCESS

I tried this one above - I still get the same issued in the log file and the network is not working flawlessly :frowning:

Does the Conbee 2 really change the channel when you change it config.yaml and reboot? I can read several places online that you need to repair devices after changing channels, but every time i have made a channel change in the config all devices are still there after a reboot?

I was having this issue today but only with a few sensors. It turned out that it was one of my ikea repeaters (wife unplugged and plugged it into a powerbar on other side of the room it was in).

Even after rebooting host or shutting down host nothing worked until I looked at the ZHA network map/topology and all the problem endpoints were connected to the ikea repeater.

  • It’s sneaky because the repeater isn’t an entity but only a device so it didn’t stick out with red flags. Unplugged the ikea router and put it in a different outlet and viola problem that existed for 12hrs or longer gone after about a min or two following boot-up of the ikea router.
  • seems too simple I know but it worked for me - no HA reboots or anything after moving the USBplug/repeater.
    Hope you have solved your problem already though!

Also having similar warnings in my ZHA log. Does anybody know what this is?

Logger: zigpy_deconz.api
Source: /usr/local/lib/python3.9/site-packages/zigpy_deconz/api.py:307
First occurred: October 6, 2021, 17:38:25 (113 occurrences)
Last logged: 15:49:21

No response to 'Command.aps_data_indication' command with seq id '0xd0'
No response to 'Command.aps_data_indication' command with seq id '0xd9'
No response to 'Command.aps_data_indication' command with seq id '0x37'
No response to 'Command.aps_data_indication' command with seq id '0xdb'
No response to 'Command.aps_data_indication' command with seq id '0xa3'