Erik Baauw

I don’t I see your branch, it’s probably only available on your fork? Basically, you need create two new item files in `devices/generic/items` for `state/power_multiplier` and `state/power_divisor`. I don’t think...

I'm not sure what would be the best approach to address this. We could probably simply cast the value to `quint64` in the API in `rest_lights.cpp` and `rest_sensors.cpp` and leave...

The change of items to `DataTypeReal` breaks the evaluation of rules conditions, at least for `lt` and `gt`. `Event` defines `m_num` and `m_numPrev` as `int`, where `ResourceItem` defines these as...

> But back to `RAttrExtAddress` the purpose for this item is to have the actual numeric value used by various parts in the DDF/Device machinery. It's not meant to be...

What debug options do you need for that?

Attached log except when restarting deCONZ through API (after which DDFs wouldn't be loaded) vs restarting deCONZ manually afterwards (after which DDFs are loaded). [log.gz](https://github.com/user-attachments/files/17005434/log.gz) Only running with `--http-port=80 --dbg-ddf=1...

> how many different sensor devices are to be expected Four, I think: Hue dimmer switch, Hue motion sensor, and Hue wall switch module (2 `modelid` values)

This issue seems to be solved, indeed; #7935 is still present in 2.29.1.

Not sure why the validation checks fail. These changes pass `ddf-tool validate` locally: ``` $ ddf-tools validate -d devices - Using validator version 2.31.1 ✔ Found 662 files to validate...

@manup, can we merge this? I want to wait with creating the attributes in legacy code, until we can handle them at the device level in DDFs as well (rather...