DDFs not loaded on deCONZ restart through API

[ebaauw]

Does the issue really belong here?

• I definitively want to report a bug within deCONZ or its REST-API

Is there already an existing issue for this?

• I have searched the existing issues and there is none for the bug at hand

Describe the bug

Sometimes, when restarting deCONZ through the API, deCONZ won't load any DDFs. Consequently, devices no longer exposed by legacy code are missing from the API, and devices still exposed by legacy code miss the advanced features from the DDF.

After exiting deCONZ (from the GUI) and restarting it, the DDFs are loaded again.

Steps to reproduce the behavior

Issue a POST to /config/restartapp and watch the GUI after deCONZ has restarted.

I've seen the issue a couple of times yesterday, but this morning, trying to get a screenshot, it doesn't appear, of course. I suspect there might be some sort of racing condition on startup, see also #6710.

EDIT Later today, the issue re-appeared, updated the screenshots.

Expected behavior

DDFs should be applied.

Screenshots

Before restart:

After restart:

Environment

• Host system: Raspberry
• Running method: Raspbian
• Firmware version: 26780700
• deCONZ version (not Home assistant Addon version!): 2.28.1
• Device: RaspBee II

deCONZ Logs

No response

Additional context

No response

[SwoopX]

Hm, interesting case. If I'm not mistaken, manup just recently added some additional debug output where any DDF loading could go south. Maybe you can share the first couple of seconds of deconz' startup log hoping that gives us more valuable insights.

[ebaauw]

What debug options do you need for that?

[SwoopX]

What debug options do you need for that?

I'd say the usual suffices: --dbg-error=2 --dbg-info=2 --dbg-ddf=1 --dbg-dev=1

[ebaauw]

Attached log except when restarting deCONZ through API (after which DDFs wouldn't be loaded) vs restarting deCONZ manually afterwards (after which DDFs are loaded).
log.gz

Only running with --http-port=80 --dbg-ddf=1 --dbg-error=2; I'll change that in case the issue re-occurs.

[SwoopX]

This part of your log is pretty remarkable:

Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | LTG002
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | RWL022
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: dresden elektronik | Kobold
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | LTA009
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: innr | SP 240
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | 915005996501
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: IKEA of Sweden | TRADFRI Driver 30W
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | SML003
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | RDM001
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | LTU001
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: icasa | ICZB-IW11D
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | LCA006
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF identifier pair: Signify Netherlands B.V. | LWA028
Sep 15 12:36:35 pi5 deCONZ[2466075]: 12:36:29:227 DDF try to find raw JSON DDFs for 13 identifier pairs

It seems deconz has decided just to load your light DDFs. The rest of the log is not less remarkable, as all DDFs are apparently reloaded like at least 10 times in a row without any result. I'm not sure how many different sensor devices are to be expected, but maybe the search/load attempts correspond in this regard?

Anyway, something is seriously going wrong here, but unfortunately the log has not all what could potentially be useful onboard from a debug flag perspective.

[ebaauw]

how many different sensor devices are to be expected

Four, I think: Hue dimmer switch, Hue motion sensor, and Hue wall switch module (2 modelid values)