Manuel Pietschmann

``` Item.val={1: 1002, 2: 1004, 0: 1001, 255: 1003}[Number(ZclFrame.at(3))] ``` I don't think that will work in Javascript since object keys must be strings. Here's an alternative approach (1): ```js...

> It should be fine, JS engines internally coerces keys that are not string | Symbol via [ToPropertyKey](https://tc39.es/ecma262/#sec-topropertykey) as part of the ECMAScript spec: Thanks I didn't know that. Could...

Cool nice that it works, then I see no problem for merging. I like Web REPL, perhaps some time this should also be integrated into the UI for easier testing.

Hi thanks for the PR, please have a look at the error message. The "options" object isn't a DDF thing.

@SwoopX do you think this PR is ready to merge? My thermostat knowledge is almost nil :)

Ok thanks for the input, I guess to get a better feeling @jjantu can you please add a Request Device Support issue for a more complete picture as described in...

@Smanar @ebaauw @SwoopX I think we should be more explicit here on the device type. The `ZHAControl` seems to be too broad (controlling what and how?) isn't this just another...

Note to my self the API exposes this already with the `capabiities` for various power on features and OTA fields, when a DDF for a device has respective items. Only...

@mattreim @Smanar PR is alright. Just some considerations to enhance the DDF in future. Since a few versions DDFs support "buttons" and "buttonevents" to describe these (similar to button_maps.json). Good...

Cool thanks I like that, but would prefer we add this to https://github.com/dresden-elektronik/deconz since this build the complete application. The ARM Dockerfiles seem to miss `libsqlite3-dev`?