This is the IAS Zone cluster when I restart deCONZ (without triggering the sensor):
and the REST-API reports: "open": true.
When I open and close it the IAS Zone cluster is
and the REST-API reports "open": false.
Hi,
I observed a similar behavior. It has worked fine when I did a first test. I did a reboot of deconz (hosted within a container on my synology NAS), and it does not work anymore…
The REST-API gives: "open": false.
For me it works fine after a deconz restart. But I have to trigger them once to get the correct state
Thanks for this. It has worked with my 2 sensors. They are now working fine. I hope the pairing process will be improved in the future.
Does anyone know if its possible to create a binding/reporting to get the sensor to report the current state at an interval? Lets say at least every 12 hours
Hi everyone,
I’m having trouble getting my Parasolls to work. I’m on Deconz 2.5.1-beta since this was the only version that allowed me to pair, I’m guessing it’s because it’s the only one that has the DDF. After pairing, however, the sensors are unresponsive. This is what I’m getting from the REST API:
{
"config": {
"battery": 0,
"on": true,
"pending": [],
"reachable": true
},
"ep": 2,
"etag": "ad36d019838ed28ecdf4db25f607b242",
"lastannounced": null,
"lastseen": "2024-01-22T10:56Z",
"manufacturername": "IKEA of Sweden",
"modelid": "PARASOLL Door/Window Sensor",
"name": "PARASOLL Door/Window Sensor",
"state": {
"lastupdated": "none",
"lowbattery": null,
"open": null
},
"swversion": "1.0.19",
"type": "ZHAOpenClose",
"uniqueid": "04:87:27:ff:fe:b8:32:38-02-0500"
}
I tried reading Power Configuration and IAS Zone as mentioned above, but it didn’t change anything. I have two Parasolls, both acting the same way. Can you guys recommend anything else?
EDIT: I went back to 2.4.3 with the DDF added manually, same behaviour
Did you trigger the sensor on reading? Was read successful?
Nothing changes in the Attributes list when I click “read”, so I guess that it isn’t successful. I tried clicking “read” while triggering the sensor as well, still nothing.
Ikea Parasoll Window/Door sensor - #8 by jan666 is it like on the first or on the second screenshot?
For me it looks like the issue I had. Did you click the read button (this one on the screenshot) and opened the sensor after that? This is how I fixed this on all of my 4 sensors
I did try that, with no success.
Interestingly I then tried pairing it using the old UI, and it looked like this:
Same REST API response, though, so not functional.
After Deconz restart, IAS Zone reverted to this: Ikea Parasoll Window/Door sensor - #18 by erratic
How did you pair it?
It just started working. I’m getting the right state on the API. But IAS Zone is still like in Ikea Parasoll Window/Door sensor - #18 by erratic
This is so weird.
I used Phoscon from deCONZ 2.24.2 with the DDF copied to /home/pi/.local/share/dresden-elektronik/deCONZ/devices/.
It worked with me also!
Looks like the initial pairing issue was fixed with an updated DDF in 2.25.3.
If you put the old DDF in your folder you have to delete it after the update or you’ll stuck with the old one.
But the issue that the state is wrong after a deCONZ restart is still there
I’ve recently purchased a couple of Parasolls from IKEA and am struggling to get them working. The pairing process went normally with clicking four times on the pair button. They paired pretty quickly; however, I’m only seeing basic information, and I’m not seeing any value being shared from the sensor. I see some people mentioned different versions; I’m currently running 2.26.3. I see a mention of a restart and a first trigger of the sensor to get them working, but these haven’t helped yet.
The Home app is also not reading anything from the sensor and only reading it as closed with 0% battery, as others have pointed out.
I’m not sure where to proceed from here. If anyone has any pointers, I’d greatly appreciate it.
@fl0 I never did. I actually moved to Zigbee2MQTT.
The only suggestion I have is through some forum somewhere, I forgot where exactly.
I had a separate issue connecting some new sensors I bought after my initial port to z2m (other Window/Door sensors were already connected and working as expected with other devices). Someone facing a similar issue posted about it and in that thread, the culprit ended up being Trådfri lights. Something about the proximity makes them pair to the lights or pairs through them. I believe they mentioned they planned on replacing their Trådfri lights, but I wasn’t about to do that. I thought that was interesting and tried pairing right next to the Conbee stick, and that actually resolved that separate issue.
Maybe this could be the issue I was facing initially with deCONZ? Can’t say.
Hope this helps in some way!
thanks for the reply.
i just got it working with my conbee 3 and deconz. I removed the sensor from deconz, cleared all old parasoll DDF files and rebooted deconz. After that, it just worked, even after no battery or reboots…I’ll check back tomorrow, but every test was successful now…
can’t tell exactly what happened today 