I had to replace a broken FYRTUR with a new one. It had an old firmware installed and adding it via Phoscon did not work. After updating to the latest firmware I was able to add it via Phoscon and the lights API endpoint is there. But the battery endpoint is missing.
I tried paring it again, reading everything via deCONZ, reading the Power Configuration Cluster also works without problems. But no battery sensor is created
Both are in the same DDF, I don’t see why can have only a part of the DDF.
You are looking directly in the API to be sure ? In phoscon/help/API Information/sensor ?
Yeah good idea, but the network need to be in permit join (“add new light” in Phoscon) in same time, to permit the device creation in API.
Just joined it freshly in our test network here with v2.27.4-beta, it creates the ZHABattery correctly.
However the unit has an older firmware SwBuildId 2.3.079.
I’ll check if OTA to newer version makes a difference.
After OTA update to 24.4.13 the device still works.
In comparison the simple descriptor only got a new Identify client cluster (0x0003) but no changes which may cause troubles otherwise.
Note I’m testing with v2.27.4-beta not sure if that makes a difference.
The v2.26.3 still had the old Ikea blinds DDFs which where removed later on in favor for blinds.json DDF.
But this would kill the option to override existing “stock ddf” by simply putting it into /home/pi/.local/share/dresden-elektronik/deCONZ/devices/, right?