deconz-rest-plugin
deconz-rest-plugin copied to clipboard
dresden-elektronik
DDF hot reload doesn't re-evaluate match conditions
Does the issue really belong here?
- [X] I definitively want to report a bug within deCONZ or its REST-API
Is there already an existing issue for this?
- [X] I have searched the existing issues and there is none for the bug at hand
Describe the bug
Got some new LTA009 Hue lights with ancient firmware, not yet exposing the Hue Effects (0xFC03) cluster. After firmware upgrade, and reload of the Simple Descriptor, the GUI would show the cluster. However, Hot Reload doesn't link the DDF to the device. The DDF would only be matched after deCONZ restart. Note that the DDF has a filter on the existence of the cluster: "matchexpr": "R.hasCluster(0x0b,0xfc03)"
Steps to reproduce the behavior
- Pair LTA009 with old firmware and check that it doesn't expose the Hue Effects cluster;
- Update the firmware through the OTAU plugin, re-read the Simple Descriptor and notice that the light now exposes Hue Effects;
- Try Hot Reload (on another LTA009 that was already exposed through the DDF), and notice the new LTA009 remains unmatched;
- Try to select the DDF manually on the new LTA009 and Hot Reload, and notice the new LTA009 remains unmatched;
- Restart deCONZ and notice the new LTA009 is matched to the DDF.
Expected behavior
Not sure, but I would expect the DDF to be (re-) assigned after updating the device firmware.
Screenshots
No response
Environment
- Host system: Raspberry Pi
- 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
Interestingly, I had a rather similar experience yesterday while trying to add support for the frient pet aware motion sensor. DDF was there and correctly using name and ID but reading those attributes did not trigger the DDF association mechanism 🤔 Had to delete it in deconz and reset'n're-pair to make it work.
I ran into similar problems - not only using hot reload, but also after restarting deCONZ I had flaky results:
- deleted devices have still been known by name after re-adding.
- also old DDF was matched even if device had new firmware and matchexp should not match anymore.
- additionally I have 3x identical devices: one was not matched by DDF while all others were matched.
More info is here (in case it helps): https://github.com/dresden-elektronik/deconz-rest-plugin/issues/6251
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] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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.
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.
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.
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.
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.
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.
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.