Improve DDF for dresden elektronik's Kobold

[ebaauw]

• Add missing capabilities and config items;
• Use attribute reporting for state/on and state/bri - any reason why this was disabled in favour of polling?

[ebaauw]

Hm, seeing this every five minutes, and by the looks of it, also on change reports:

 Warning duplicated zcl.cmd: 0x0A, cluster: 0x0006 with zcl.seq: 57 for dresden elektronik / Kobold

The zcl.seq value changes between messages, not sure what is duplicated. Do I need to sniff the traffic, or is this a known issue?

Kobold was on firmware 0102.10000026, but I see no changes after upgrading to .1000002A. Apart from the warnings in the deCONZ log, attribute reporting seems to work, and the GUI attributes as well as the API resource items are updated.

[manup]

Thanks for looking into this :+1: It's a tricky one, for now I'd like to keep the disabled reporting since I need to make some more testing first how this works in different setups.

Iirc the disabled reporting is there due the "non coordinator / lost coordinator" setups which the device needs to support. For example if a Kobold is setup via deCONZ to control a group of lights, and afterwards the coordinator is turned off. The unicast bindings are disabled so that there isn't endless traffic towards the coordinator in that case. Technically not the best approach but that was the path with limited development time available ;)

[github-actions[bot]]

Hey @ebaauw, thanks for your pull request!

[!TIP] Modified bundles can be downloaded here.

DDF Bundles changes

Modified

• dresden_elektronik/kobold.json : Kobold :heavy_check_mark:

Validation

[!TIP] Everything is fine !

_{:clock430: Updated for commit 3957500772616a0a32f435aaf38e75ee3d4fdfe9}