FYRTUR - /battery device is not created

deCONZ General Support
1

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

2

Another difference:

the old ones have "swversion": "24.4.13". The replacement has "swversion": "20190311". I updated to 24.4.13

3

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.

4

I tried reading everyting again while the network was open - no sensor was created. But the swversion is now correct.

I have 3 ZHABattery Sensors

curl -XGET http://.../api/.../sensors | jq '.[] | select(.type == "ZHABattery")' | grep uniqueid
  "uniqueid": "84:71:27:ff:fe:25:f7:b3-01-0001"
  "uniqueid": "84:fd:27:ff:fe:44:9b:ab-01-0001"
  "uniqueid": "00:21:2e:ff:ff:0c:73:67-01-0001"

(2x other FYRTUR, 1x Phoscon Hive)

but there is none for the newly added:

  "type": "Window covering device",
  "uniqueid": "68:0a:e2:ff:fe:f6:e3:bc-01"

curl -vv -XGET http://.../api/.../devices/68:0a:e2:ff:fe:f6:e3:bc | jq
{
  "lastannounced": "2024-07-10T09:25:55Z",
  "lastseen": "2024-07-11T05:19Z",
  "manufacturername": "IKEA of Sweden",
  "modelid": "FYRTUR block-out roller blind",
  "name": "Rollo DG Mika",
  "productid": "FYRTUR block-out roller blind",
  "subdevices": [
    {
      "state": {
        "alert": {
          "lastupdated": "2024-07-10T19:36:00Z",
          "value": null
        },
        "bri": {
          "lastupdated": "2024-07-11T06:58:51Z",
          "value": 0
        },
        "lift": {
          "lastupdated": "2024-07-11T06:58:51Z",
          "value": 0
        },
        "on": {
          "lastupdated": "2024-07-11T06:58:51Z",
          "value": false
        },
        "open": {
          "lastupdated": "2024-07-11T06:58:34Z",
          "value": true
        },
        "reachable": {
          "lastupdated": "2024-07-10T19:36:00Z",
          "value": true
        }
      },
      "type": "Window covering device",
      "uniqueid": "68:0a:e2:ff:fe:f6:e3:bc-01"
    }
  ],
  "swversion": "24.4.13",
  "uniqueid": "68:0a:e2:ff:fe:f6:e3:bc"
}
5

Which version of deCONZ is this?

The output of /devices/<mac address> should have a few more fields in current version.

6

Latest stable version

ii deconz 2.26.3 armhf Zigbee monitoring and control.

7

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.

8

Mine hat 2.2.x initially and this did not work at all (also no light created)

9

I made some screenshots for before and after comparison, wouldn’t be the first time that the descriptors are changed via OTA updates.

image

This will take a while, update is reaaaaly slow :slight_smile:

10

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.

11

IDK if it’s linked but here Unable to pair Ikea PRAKTLYSING - #13 by drakkhen there is an user not able to pair a PRAKTLYSING.
On debug, deconz choose the good DDF, but nothing after.

12 
pi@raspberrypi:~ $ sudo rm /usr/share/deCONZ/devices/ikea/fyrtur_block-out_roller_blind.json 
pi@raspberrypi:~ $ sudo service deconz restart

opened the network and the sensor is there

{
  "config": {
    "alert": "none",
    "on": true,
    "reachable": true
  },
  "ep": 1,
  "etag": "40b6bb78aa850767e46a6434ea5f5b58",
  "lastannounced": null,
  "lastseen": "2024-07-12T04:51Z",
  "manufacturername": "IKEA of Sweden",
  "modelid": "FYRTUR block-out roller blind",
  "name": "Rollo DG Mika (Akku)",
  "productid": "E1757-140",
  "state": {
    "battery": 97,
    "lastupdated": "2024-07-12T04:08:22.685"
  },
  "swversion": "24.4.13",
  "type": "ZHABattery",
  "uniqueid": "68:0a:e2:ff:fe:f6:e3:bc-01-0001"
}
13

Good catch, also that the older files where intercepting loading of the blinds.json as they had Draft status.

I guess, we have a bug lurking that no two raw JSON files should exist using the same modelid/manufacturername, gonna need to check this.

Side note: For the new DDF bundles this isn’t a problem, loading here is based on embedded timestamps and stable/beta signature policies.

14

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?

15

I’ve reported this before. I believe made a PR, but not sure what happened to it.

16

The PR is merged and works but that was after v2.26.3.

17

That stills works then, the two user/system locations are searched and user one takes priority.

1 Like