BabaIsYou

I totaly agree that the binding/location in cluster that are device/manufacturer specific are to be preferably located in devices DDF. But, as I remember, that does not make it writable...

> I schedule this for the next beta after stable, so we need to work out a opinion and naming for these items :) Seems we skipped some milestones ......

Could try this DDF ? You,Ll have two devices, one On/off "light" and one Consumption "sensor" ``` { "schema": "devcap1.schema.json", "manufacturername": ["_TZE200_a7sghmms", "_TZE200_sh1btabb"], "modelid": ["TS0601", "TS0601"], "vendor": "GIEXperience", "product": "Smart...

I saw for the swversion but was not an issue at this step ;-) I don't know what Homebridge is displaying or not, can you have a look using REST-API...

The Consumption sensor could eventually be replaced by ``` "type": "$TYPE_OPEN_CLOSE_SENSOR", "restapi": "/sensors", "uuid": [ "$address.ext", "0x01", "0x0500" ], ``` instead of ``` "type": "$TYPE_CONSUMPTION_SENSOR", "restapi": "/sensors", "uuid": [ "$address.ext",...

I know that some devices are an in-between mode that's perhaps not clearly identified and that some measures are only considered under one angle (electricity) in REST-API. But from my...

I see no more addition at this step than swversion. I suggest also to change` "status": "Gold"`, for `"status": "Silver",` and to put the new DDF in https://github.com/dresden-elektronik/deconz-rest-plugin/tree/f837452b4eec614746e3ba56f214b1096342a797/devices/tuya with name...

If you add something like `close #6944` in the comment of the PR, github will automatically close this issues once PR merged with a next version.

Yes seems good. Waiting for approval.

> I finally test it and work very well with my rfid tag bought on amazon. Which one please ?