Zehir

I updated the playground with the lastest changes ; https://deconz-community.github.io/ddf-tools/

An `unit` items inside the state could be usefull like `°C`, `second`, `kwh`, `lx`, `%`, ... And like for temperature sometime you need to divide the value by 100 to...

About the `buttonevent` values, what about split the key id and the action id like having `1` and `2` instead of `1002` ?

> > About the `buttonevent` values, what about split the key id and the action id like having `1` and `2` instead of `1002` ? > > Thats gonna be...

And what about a button definition in `devices/introspect/` like this : ```javascript { "id": 1, "group": 1, // Like for remotes with more than one group of keys like big...

About the `colorcapability` could be have a array with `key` : `boolean` instead of en binary encoded inside an integer ?

Why set the light state is `PUT /api//lights//state` And set the group state is `PUT /api//groups//action` And for scenes `PUT /api//groups//scenes//lights//state` That don't make sense for me ;)

> > Why set the light state is `PUT /api//lights//state` > > And set the group state is `PUT /api//groups//action` > > That don't make sense for me ;) >...

> `GET http://127.0.0.1/api//devices/introspect/00:17:88:01:08:f7:76:8c` > `GET http://127.0.0.1/api//devices/introspect/00:17:88:01:08:f7:76:8c-02-fc00` Why it's not `GET http://127.0.0.1/api//devices/00:17:88:01:08:f7:76:8c/introspect` like all the rest of the api ?

By splitting `action` and `state` you could get the current action or the current state instead of mixing both. Like action is read write and state readonly