Smanar

Yes, so this one is exactly like on the DDF, as you can see you have only state/on and state/reacheable, so on your capture (from iobroker ) it's perhaps old...

@craggyh how are you doing ? what is your OS ? You generaly need to create a text file in a "devices" folder, called what_you_want.json with the DDF contain. >where...

You are using the version with state/flow ? https://github.com/Smanar/deconz-rest-plugin/commit/91d5eb5f4bdf4fde70e4c3bd53856a118410c004

Yes the other version are more options, like alarm or flow measurement. But you need to add 2 files to test it.

The temperature sensor need to be like ``` { "type": "$TYPE_TEMPERATURE_SENSOR", "restapi": "/sensors", "uuid": [ "$address.ext", "0x01", "0x0402" ], "items": [ { "name": "attr/id" }, { "name": "attr/lastannounced" }, {...

It will be not visible on deconz but in the API, using for exemple Phoscon/help/API Information/sensor Need to reload deconz after the DDF addition, and better to delete/re-nclude the device...

Have you aded the tuya unlock sequence ? ``` { "name": "config/tuya_unlock" }, ``` You need to re-include the device after or wait 24h.

Yeah, the editor make too much "magic". On my side I use only text editor, but all codes are good, one is the 'light" code that use the defaut code,...

Nope this device use tuya cluster, so need to catch tuya debug. But I have found the dpid on another project ``` { "name": "state/temperature", "parse": {"fn": "tuya", "dpid": 102,...

Sure, do you want to make the PR ? Or want I make it ?