All Zigbee devices not working

deCONZ General Support
1

About 2 days ago I noticed some of the Jasco zigbee switches would not go on when commanded via HomeSeer. Looking at deCONZ, I noticed if I click on the switch and open Cluser Info, Manufacturer Name and Model Identifier were blank. After trying to execute a read, this information would still remain empty. Only after resetting the switch and discovering it again would that information now populate and the switch functioned again.

Does anyone know what caused this and how to correct it without having to delete and rediscover over 100 switches?

Here is my system info:

ConBee III running firmware 26510900
deCONZ 2.29.1

Thank you
-Bob

2

Can you share some logs?

3

First time generating logs for this, can you tell me which ones you are referring to?

4

There you go

6

Is the company really interested to solve these problems? I wrote similar things 6-7 weeks ago by email and even not heart anything

7

Are these switches mains powered? If they are battery powered in order to read attributes the device usually needs to be awake, by pressing a button on the switch after clicking the “read” button.

Can you share a screenshot of deCONZ, are there still green lines between devices?

8

OK, I have the debug data, which is too large to paste here, and I cannot upload as a txt file. How can I get this to you?

9

Pastebin

10

OK, here it is:

Its only about a minute, but if you need more or some specific actions, I can get another dump.

Thank you

11

I think I seen this before let me ask @de_employees

12

Thanks for the logs, on a first look lines with delayed requests stick out:

Delay APS request id: 58 to 0x638B, profile: 0x0000 cluster: 0x8000 node already has busy 3

This is happening for multiple devices and looks like the outgoing queue is piling up.
The upcoming version has a PR to counterfight queue issues https://github.com/dresden-elektronik/deconz-rest-plugin/pull/8074 but I’m not sure if it helps in this case.

Can you please also share the zll.db file, or an backup created in the Phoscon App and send it to support@dresden-elektronik.de I’d like to check which are running on DDFs and which are handled by old code.

13

Backup sent as requested.

14

Checking in to see if there were any updates to this.

15

@manup

16

Hi thanks for the backup, I’d suggest to test with the upcoming version if it works better due the refactored scheduling. I’m currently merging the last code snippets and release should be ready tomorrow.

17

Great, thank you!

Install file located here?
https://deconz.dresden-elektronik.de/win/

(SSL cert expired on the 17th BTW)

Once installed, If I see the Delay messages, is that an indication that this did not get fixed, or should I look for other messages as well?

18

I updated to v2.29.2 and let it run for a few days. Lights seamed to work correctly and after a few days, lights started to not respond. I did a debug, and spotted lots of Delays again.

Here is link to a log:
Phoscon v2.29.2 - Pastebin.com

Any ideas on what else could be done?

19

Thanks for testing the new version and the log. Does a restart of deCONZ help temporarily with the delays?
I’m trying to figure out the affected devices in the log and match them with the database in the backup.

20

I just did a restart and captured a new debug, still lots of Delays. Not sure if random or not, but a light that worked in the beginning failed after a few days.

Prior versions seemed to get worse over time to the point lights would take a while to operate (few seconds) or not work at all. This version seemed to be on the right track where lights did not delay up to the point I noticed a light not responding.

Let me know if you need anything else.

Here is new debug:
Deconz v2.29.2 after a restart - Pastebin.com

21

Thanks, from checking your backup database against the codebase and existing DDFs it can be seen that most of your devices (94) are from “Jasco Products” brand. And here only dimmable and on/off types, so should be rather simple to add as DDF.

I’ll prepare DDFs for the model IDs “43076” and “43080”, hopefully this should tame the scheduler and doesn’t need the legacy code anymore. Another “Jasco Products” DDF shows that they seem to support reporting, which is good to get rid of polling the device state which also amplifies the delayed APS queue messages.