Hello! I have two Ikea PRAKTLYSING cellular blinds and cannot get them to pair to Phoscon. I’m using a ConBee II running gateway v2.26.3 and firmware v26720700.
I go to Blinds → “+”; short-press both buttons on the device to enter pairing mode; after a minute or so the UI says “Failed to connect”.
Any ideas of what I can try or what might yield more helpful troubleshooting information? Thank you!
Hello what mean the “+” ? On my side it’s called “add new blind”.
On my side I m reading press both button for 5 s.
Hi Smanar –
Ah you’re correct about the UI button: when the Phoscon web app is in a narrow window, the “Add New Blind” button is hidden and replaced by a “+” button. I’ve tried adding the blinds from both my phone (with the “+” button) and laptop (with the “Add New Blind” button) with the same result.
As for the duration to hold the buttons on the blinds, Ikea’s instructions say to “short press” both of them to enter pairing mode (this works with the included remote button), and to hold for 5 seconds to reset the blind (unpairing any paired remotes and, I assume, resetting the extension limit if set).
This is the “pairing mode” to pair the blind with a remote no ?
Try with the reset procedure.
With a gateway, never pair a device with a remote with this “direct link procedure”, else it will leave the network to create a new one just for them.
The correct procedure is the reset procedure, to include all devices in the same zigbee network and after “link” them using zigbee request (making group)
Correct, the pairing mode is used to add a remote, and this works with the physical remote that was included with the blinds.
To clarify, you’re saying that the blinds cannot be paired both with the physical remote a Zigbee controller at the same time?
I did just try:
This resulted in the same “Failed to connect” in the UI. 
To clarify, you’re saying that the blinds cannot be paired both with the physical remote a Zigbee controller at the same time?
No, I m just saying this procedure is a “direct link”, if your device (light or covering) is already in a zigbee network, it will leave it to create a new one with the remote, so you will be able to control it with the remote but no more with deconz.
For exemple with the simple ikea remote the correct procedure is the 4 short press, never the long press.
It’s possible having all blinds and all remote in the same network, but not with the “direct link” procedure, this need to be done using deconz.
Try:
Thank you @Smanar – this is starting to make more sense, I think. So the “short press” is to pair the remote, but the 5 second press is to re-pair the blind with another controller/Zigbee network like Phoscon?
I tried several times pressing “Add New Blind” and holding both buttons on the blind for 5 seconds, even taking the blind down and holding it within a meter of the ConBee II, but unfortunately every time it times out with “Failed to connect”. 
It’s weird I’ve been able to connect many other devices to Phoscon (Aquara sensors and plugs, BTF-Lighting controllers, and a TRÅDFRI Signal Repeater) and I’ve never had a problem like this. Is it possible that IKEA changed something in the device’s firmware recently?
I haven’t the device but seem logic for me according the documentation. One procedure is a “direct pairing” the other a reset to re-include a network.
For you problem on the v2.26.3 it need to work. Do you have access to the GUI ? (the full application)
No, this installation is headless without the GUI. Is there any way to turn up logging or sniff the Zigbee network with a ConBee II or would that require different hardware?
It’s possible having log only deCONZ command line parameters · dresden-elektronik/deconz-rest-plugin Wiki · GitHub
I collected the following log entries with --dbg-info=2. (Note that I cleaned it up a little, removing unrelated entries from other devices that are working.)
From line 31, it seems that deCONZ is (or thinks it is) identifying the device – but it still ends with “Failed to connect” in the UI:
1 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:32:41:466 Websocket 192.168.0.86:63331 send message: {"e":"changed","id":"77","r":"sensors","state":{"current":0,"lastupdated":"2024-07-10T01:32:41.46 2","power":-1,"voltage":0},"t":"event","uniqueid":"00:15:8d:00:02:ab:2e:aa-01-0b04"} (ret = 1893629972)
2 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:32:41:625 Websocket 192.168.0.86:63331 send message: {"e":"changed","id":"78","r":"sensors","state":{"current":0,"lastupdated":"2024-07-10T01:32:41.62 4","power":0,"voltage":0},"t":"event","uniqueid":"00:15:8d:00:02:ab:2e:aa-02-000c"} (ret = 1893629972)
3 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:32:43:392 DB save zll database items 0x00000081
4 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:32:43:392 DB saved in 0 ms
5 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:32:45:892 send permit join, duration: 65
6 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:32:46:892 send permit join, duration: 65
7 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:09:986 APS-DATA.indication from unknown node 0xC7BB
8 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:09:986 0x70AC08FFFE8F9A0A 0x4F0F nwk changed to 0xC7BB
9 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:009 device announce 0x70AC08FFFE8F9A0A (0xC7BB) mac capabilities 0x80
10 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:009 set fast probe address to 0x70AC08FFFE8F9A0A (0xC7BB)
11 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:010 FP indication 0x0000 / 0x0013 (0x0000000000000000 / 0xC7BB)
12 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:010 ... (0x70AC08FFFE8F9A0A / 0xC7BB)
13 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:010 device announce 0x70AC08FFFE8F9A0A (0xC7BB) mac capabilities 0x80
14 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:010 DEV Tick.Join: event/device.anounce
15 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:010 DEV Tick: fast poll 0x70AC08FFFE8F9A0A, mac capabilities: 0x80
16 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:893 [1] get node descriptor for 0x70ac08fffe8f9a0a
17 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:10:893 ZDP get node descriptor for 0xC7BB
18 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:113 FP indication 0x0104 / 0x0000 (0x70AC08FFFE8F9A0A / 0xC7BB)
19 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:113 ... (0x70AC08FFFE8F9A0A / 0xC7BB)
20 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:119 wait response fastEnddeviceProbe() 0x70AC08FFFE8F9A0A, elapsed 226 ms
21 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:160 DB pushZdpDescriptorDb()
22 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:161 FP indication 0x0000 / 0x8002 (0x70AC08FFFE8F9A0A / 0xC7BB)
23 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:161 ... (0x70AC08FFFE8F9A0A / 0xC7BB)
24 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:161 ZDP indication search sensors 0x70AC08FFFE8F9A0A (0xC7BB) cluster 0x8002
25 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:161 ZDP indication search sensors 0x70AC08FFFE8F9A0A (0xC7BB) clear timeout on cluster 0x8002
26 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:166 [2] get active endpoints for 0x70ac08fffe8f9a0a
27 Jul 10 01:33:12 pi-phoscon deCONZ[7625]: 01:33:11:167 ZDP get active endpoints for 0xC7BB
28 [...]
29 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:223 FP indication 0x0104 / 0x0000 (0x70AC08FFFE8F9A0A / 0xC7BB)
30 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:223 ... (0x70AC08FFFE8F9A0A / 0xC7BB)
31 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:223 DEV found DDF for 0x70AC08FFFE8F9A0A, path: /usr/share/deCONZ/devices/ikea/tredansen_block-out_cellul_blind.json
32 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:229 FP indication 0x0000 / 0x8005 (0x70AC08FFFE8F9A0A / 0xC7BB)
33 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:229 ... (0x70AC08FFFE8F9A0A / 0xC7BB)
34 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:229 ZDP indication search sensors 0x70AC08FFFE8F9A0A (0xC7BB) cluster 0x8005
35 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:229 ZDP indication search sensors 0x70AC08FFFE8F9A0A (0xC7BB) clear timeout on cluster 0x8005
36 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:244 FP indication 0x0000 / 0x8005 (0x70AC08FFFE8F9A0A / 0xC7BB)
37 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:244 ... (0x70AC08FFFE8F9A0A / 0xC7BB)
38 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:244 ZDP indication search sensors 0x70AC08FFFE8F9A0A (0xC7BB) cluster 0x8005
39 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:47:892 send permit join, duration: 65
40 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:59:435 ZCL attribute report 0x00158D00077551BB for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
41 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:59:435 payload: 01ff42220121ef0b03281e0421a8430521a30206240100000000082106020a21d251641000
42 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:34:07:892 sql exec SELECT conf FROM zbconf ORDER BY rowid desc limit 1
43 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:34:28:545 ZCL attribute report 0x00158D0002AB2EAA for cluster: 0x0000, ep: 0x01, frame control: 0x1C, mfcode: 0x115F
44 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:34:28:545 payload: 01ff422b64100003282698390000000095399e418841052112009a200008210b120727000000000000000009210206
Let me know if you’d like me to try again to collect more logs, or if there are any additional debugging parameters that might yield helpful log entries.
Thanks again for your help!
31 Jul 10 01:34:28 pi-phoscon deCONZ[7625]: 01:33:12:223 DEV found DDF for 0x70AC08FFFE8F9A0A, path: /usr/share/deCONZ/devices/ikea/tredansen_block-out_cellul_blind.json
So deconz have reconised the device, and use the good DDF.
Have you check in deconz or at least the API if the device is not here ? In phoscon/Help/API Information/light
Confirmed — I don’t see it in the UI under Lights, Blinds, or in Help / API Information.
Under Lights I have two BTK-LIGHTING controllers and a TRADFRI Signal Repeater, and there are no devices under Blinds.
@Smanar : I’m curious – are these types of blinds identified as a “Blind” or “Light” accessory? Should I be trying to add it as a Light?
AFAIK it does not matter because it just opens the network to let a new device join.
I had a problem pairing my new FYRTUR in 2.26.3 and solved it by deleting the device-specific DDF (which was also removed in the latest beta) and so used the blind.json. Maybe that works for you, too? See FYRTUR - /battery device is not created - #12 by jan666. For you it’s /usr/share/deCONZ/devices/ikea/tredansen_block-out_cellul_blind.json (you can always restore it from here: deconz-rest-plugin/devices/ikea/tredansen_block-out_cellul_blind.json at v2.26.3 · dresden-elektronik/deconz-rest-plugin · GitHub)
Indeed I think it’s the same root issue here too and in v2.26.3 can be worked around by deleting /usr/share/deCONZ/devices/ikea/tredansen_block-out_cellul_blind.json.
Huzzah! This solved the issue. The blinds were able to be added using the “two buttons for 5-seconds” method. Thank you everyone!