Ikea Fyrtur Blinds

I have 3 Fyrtur Blinds from Ikea. All of them on the latest available FW 2.3.088
I’ve had a power outage in my house, once this was resolved 2 of the blinds returned to operate normally, one didn’t. Tried reseting it a bunch of time, but the Phoscon App (tried also the 2016 Version) won’t no longer detect the blind.

Just to make sure it does work I reconnected it to the Ikea Gateway and there it was right away found and working as it should - removed it from this Gateway again, another reset and tried to pair it again with Phoscon, but no luck, no matter how close the blind was to the RaspBee II.

Has anyone experienced something similar and was able to resolve the problem?

Hello, what is your deconz version ?
Have you access to the GUI ? To check how look the device or take a look on logs ?

take out battery from the blind wait few minutes and put battery back again.

Tried that multiple times with no luck.

deCONz Ver. 2.14.01 / 6.2.2022
Firmware: 26690700

I’m running it on a headless raspberryPi with no graphical UI. So therefore I never ever even looked into the GUI version of deCONZ. I will have to install X11 first on my iMac before i can forward the session via SSH.

There is someone else with the same issue on the discord, but he use HA, so not able to install a DDF.
IDK what you are using on your iMac but Swoop have made a DDF to test for this device

{
  "schema": "devcap1.schema.json",
  "manufacturername": "$MF_IKEA",
  "modelid": "FYRTUR block-out roller blind",
  "vendor": "IKEA of Sweden",
  "product": "FYRTUR block-out roller blind",
  "sleeper": false,
  "status": "Gold",
  "subdevices": [
    {
      "type": "$TYPE_WINDOW_COVERING_DEVICE",
      "restapi": "/lights",
      "uuid": [
        "$address.ext",
        "0x01"
      ],
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "state/bri",
          "parse": {
            "at": "0x0008",
            "cl": "0x0102",
            "ep": 1,
            "eval": "Item.val = (254 * Attr.val) / 100;",
            "fn": "zcl"
          },
          "read": {
            "fn": "none"
          },
          "deprecated": "2020-04-08"
        },
        {
          "name": "state/lift"
        },
        {
          "name": "state/on",
          "parse": {
            "at": "0x0008",
            "cl": "0x0102",
            "ep": 1,
            "eval": "if (Attr.val == 100) { Item.val = true; } else { Item.val = false; }",
            "fn": "zcl"
          },
          "read": {
            "fn": "none"
          },
          "deprecated": "2020-04-08"
        },
        {
          "name": "state/open",
          "parse": {
            "at": "0x0008",
            "cl": "0x0102",
            "ep": 1,
            "eval": "if (Attr.val == 100) { Item.val = false; } else { Item.val = true; }",
            "fn": "zcl"
          },
          "read": {
            "fn": "none"
          }
        },
        {
          "name": "state/reachable"
        }
      ]
    },
    {
      "type": "$TYPE_BATTERY_SENSOR",
      "restapi": "/sensors",
      "uuid": [
        "$address.ext",
        "0x01",
        "0x0001"
      ],
      "fingerprint": {
        "profile": "0x0104",
        "device": "0x0202",
        "endpoint": "0x01",
        "in": [
          "0x0000",
          "0x0001"
        ]
      },
      "items": [
        {
          "name": "attr/id"
        },
        {
          "name": "attr/lastannounced"
        },
        {
          "name": "attr/lastseen"
        },
        {
          "name": "attr/manufacturername"
        },
        {
          "name": "attr/modelid"
        },
        {
          "name": "attr/name"
        },
        {
          "name": "attr/swversion"
        },
        {
          "name": "attr/type"
        },
        {
          "name": "attr/uniqueid"
        },
        {
          "name": "config/on"
        },
        {
          "name": "config/reachable"
        },
        {
          "name": "state/battery"
        },
        {
          "name": "state/lastupdated"
        }
      ]
    }
  ],
  "bindings": [
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0001",
      "report": [
        {
          "at": "0x0021",
          "dt": "0x20",
          "min": 1,
          "max": 3600,
          "change": "0x00000001"
        }
      ]
    },
    {
      "bind": "unicast",
      "src.ep": 1,
      "dst.ep": 1,
      "cl": "0x0102",
      "report": [
        {
          "at": "0x0008",
          "dt": "0x20",
          "min": 1,
          "max": 300,
          "change": "0x00000001"
        }
      ]
    }
  ]
}

If you can test it on your side ? DDF cheat sheet · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

You just need to put this file on the “devices” folder (where you can find the others DDF)

1 Like

Thanks for the reply @Smanar

As i’m unable to start the deCONZ GUI via SSH and X11-Server (following these instructions: Access deCONZ GUI in headless setups - dresden-elektronik/deconz-rest-plugin Wiki), i’m also unable to see what the DDF file does. I added it to my Ikea Devices Folder as fyrtur_blind.json → didn’t help with detecting, when scanning for new ‘lights’ in the Phosocon App

Can you confirm the model id “FYRTUR block-out roller blind”, visible on the working one.
There is already some other DDF in the folder you have put the file ?

Have you tried to remove the battery before making an inclusion ?

Yes the model id is as you write.
No, there are no other DDF in the Folder, only JSON files, named after the devices that have been detected.

Yes, i tried multiple times to remove the battery, to reset the device, even connected it to the Ikea Gateway and removed it and tried again on the Phoscon App.

When i connect it to the Ikea Gateway the blind can be 2-3m away and it is within seconds detected.
When using the RaspBee II with Phoscon, it can be 2 cm away from it and it will not detect it no matter how long I set the detection time in the App.

Its the “devices” folder ? Wich ones have you used ?

All DDF provided directly with deCONZ typically reside in /usr/share/deCONZ/devices/generic/ on a Linux system and are loaded first. However, files residing in the home directory of the user running deCONZ (e.g. /home/deconzuser/.local/share/dresden-elektronik/deCONZ/devices) will override the pre-packaged files to allow users to amend and keep their own files if desired.

One folder contain all DDFs

And I don’t understand “named after the devices that have been detected.”. The file name have changed after the detection ?

Under /usr/share/deCONZ/devices/generic/ i don’t have any DDF Files. There are 4 Folders and 1 JSON in it.

Under /home/ there is no Folder ‘deconzuser’ - obviously the rest is missing therefor too.

Under /usr/share/deCONZ/devices i have a folder ‘ikea’ and in it are the following JSON Files:

  • e14_ws_opal_400lm_light.json
  • gu10_ws_400lm_light.json
  • e27_cws_opal_600lm_light.json
  • ikea_known_issues_radio_silence.md
  • fyrtur_blind.json
  • kadrilj_blind.json

Ok so seem fine for me.
Without the GUI hard to see what happen, can you ty with enabling logging ? deCONZ debug flags · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

With --dbg-info=2 and --dbg-ddf=1 (not sure the second exist)

On the pi, you can just enable VNC (if not already enabled).
On your Mac, install VNC viewer.
On the pi, just stop deconz: sudo systemctl stop deconz.
Start the GUI version with: /usr/bin/deCONZ&

I also have had Fyrturs dropping out.
Re-included by starting search for new light and long pressing both buttons on Fyrtur.

well, i got the GUI running. But it doesn’t let me select my RASPBEE II and therefor I can’t check it…

did you stop the deconz process?

Deconz and deconz-gui are 2 different programs. They use the same set.

If you stop the deconz process, you can start this one.

Thx, for that @Mimiix

Now i have access to the GUI and the debug pane. But as none of my FYRTUR’s are listed, what can I do with it?

Can you show all devices on the map?

What do you mean by map? All the devices that are visible to me are in the screenshot attached in my prior reply.

And the Fyrturs are still working?

Either way, please enable the logs (see #deconz for what log levels we need) and then try to add the fyrtur. AFterwards, please share the logs.

Nope, in the meantime all of my 3 Fyrturs and 2 of my Kadrilj stopped working - only one remained in deCONZ.

I’ll try to add one of the Fyrturs back with the corresponding settings for the LOG activated.

1 Like