This same problem occurs with zigbee2mqtt, there’s an issue for it open:
There has been a converter and implementing IasZone/ZonesStatus to Min Rep Interval of 0 , which should fix the problem. I guess someone could do a ZHA Quirk that enables this fix for ZHA as well?
Instead of saying “latest firmware”, could you say what the actual version is? Latest version is not particularly helpful months or years later.
Hopefully this comes as constructive, rather than a gripe - it’s not, but it’s hard to phrase it in a way that does not sound negative. Believe me, I’ve tried 4 different variations before I gave up and just hit the reply button 
The batteries don’t make a difference. NiMH like the Ladda has a range of 1.48 volts to 0.8, while Alkaline cells have a range of 1.5 to 0.8 volts.
The difference is in way the voltage changes over time. Alkaline cells will drop gradually over time, while NiMH will fall from 1.48 to 1.2, remain around 1.2 for a relatively long period, then suddenly fall off a cliff.
To look after your NiMH’s charge only to around 1.4 if your charger gives you that option, and swap from one set to another by time rather than waiting until the device stops working.
OK, I’ve perhaps seem to be getting somewhere. I’ll update the situation next morning because usually the Parasoll’s drop out of the network nightly. What I did was I removed the pairing which I’d done previously through the Sonoff coordinator. After this I selected the nearest router device and “add devices via this device”. After pairing through my light strips, the firmware version is finally visible, previously it was always “Unknown” despite multiple pairings with my coordinator. Also strangely one of the devices opening sensor changed from “Opening” to IaS Zone. The other one still reports its status normally. At least this updated the visibility of the firmware version. I’ll let you know if this fixed the problem.
I can report that after pairing the device not directly via the coordinator, but rather through the nearest physical router (though i have my coordinator and router in the same table) the Parasoll sensors haven’t disconnected themself in 2 days. So pairing the device through the nearest router rather than directly via the coordinator seems to fixed the problem for me.
Same here for Vallhorn motion sensor device (firmware 0x01000064)
Pairing directly with Sonoff coordinator (P version) would not find any entities on the sensor.
Pairing the sensor through another Ikea smart plug (inspelning) as router worked flawlessy and all entities were immediately recognized
The sensor keeps working after removing the smart plug from the network
Core 2024.6.4
I’ve still got this issue, using a conbee II. Parasoll will start pairing and the two I have (tried various AAA types) and they both just stay stuck at configuring and never fully pair.
Tried holding it super close to the dongle and didn’t have anything for me.
I’ve used loads of IKEA devices and never had these issues so seems a bit odd.
It isn’t an issue with the batteries. It’s some kind of problem between the coordinator and the Ikea products. They seem to work flawlessly if you pair them via another device. Go to the any mains-powered device which acts as a zigbee repeater, and open its information page. Where is says Reconfigure, under the three vertical dots, you will find “Add devices via this device”
I have 20 parasoll devices.
15 are working perfect but 5 are unstable.
Sometimes they come back on the network en sometimes they are disconnected for a couple of days.
I have tried connecting them via an Ikea GU10 bulb but that doesn’t solve the problem.
I have also vallhorn devices and they work perfectly.
I think its a firmware problem on the parasoll devices, but I think there isn’t a firmware update posted yet?currently running on 0x01000019
I have a SLZB-06p7 coördinator.
I was also stuck in the “Configing” step. When it had hung for a while, I tried rebooting Home Assistant and when everything came back online it had successfully paired (this was with ZHA)
Thanks man, this helped me. I’m using the Sonoff stick and was unable to pair via the coordinator directly, then I used an already connected Ikea lamp as router, pressed 4 times the connect button, and it worked.
This worked like a charm
Here’s what I got to work using ZHA. I tried every method mentioned on every site and post I could find save from buying another IKEA device to pair with. This is the only thing that worked for me.
If you’re now bald because of these things, give this a try. Hopefully it works for you. I’ve now paired 4 of these doing it this way. The IAS Zone one I need to figure out how to wipe that from ZHA because it keeps coming back like that no matter how many times I pair it. It seems the configuration is still in ZHA despite me removing it each time. Good luck, you’re going to need it.
EDIT:After letting the sensors sit connected over night, 3 of the 4 report battery and firmware status. The one that said IAS Zone I repaired and eventually got it to work and show as an Opening, but that one still shows firmware status as Unknown. Opening and closing them repeatedly reflects accurately in the device logs so they seem to be maintaining the pairing and working.
Bro is genius.
Worked like a “charm”, considering the insane workaround.
One of two of mine also showed “IAS Zone”, but I simply went into the config of the sensor, and selected a different “show as” (“Öffnung” is German for “open”):
So, I recently bought a new Parasoll unit. When pairing for the first couple of times, the LED was behaving differently. It actually paired succesfully using ZHA. The led on the unit blinked once when closed, en twice when opened (but without fading). However, it showed up as IAS Zone in the config. The firmware version showed as 0x00024001. After pairing and unpairing a couple of times, I long pressed the pairing button, and the LED reacted by a fading blink. Now when opening and closing, the LED would blink with the usual fading behavior which I am familliar with because of a differenr one I am using. Now I reset again, and as described above paired it to ZHA. (Without actually succesfully connecting). Now it shows as a contact sensor, with firmware version 0x1000019. Below are some screenshots.
This all seems very weird to me, how can there be different behavior of the LED, and how can there be two different firmware versions on the same device?
I’m going through similar troubles with PARASOLL. I initially got one to pair, it showed as an IAS Zone but was working, but 4 or so hours later it went unavailable. When I next triggered it, curiously it suddenly reported its status. I’ve since tried to remove it and repair it, and I now can’t get it to show up when searching for devices.
I got one of these as a test as they’re cheap and easy to get locally, but unfortunately they seem too good to be true as they don’t appear to work very well.
I have the IKEA air quality sensor which acts as a zigbee router, I had success adding the VALLHORN motion sensors via that, but it hasn’t work for the PARASOLL.
EDIT: OK update, I’ve got it to pair by putting it right next to the co-ordinator during the pairing process. It gets stuck at the configuring step, and only reloading ZHA gets it to show as a device.
EDIT: OK nope, back to IAS device and unknown firmware. I suspect it will just disconnect again if I keep it in this state.
EDIT: OK last edit. The ONLY way I can get this to reliable pair is via my co-ordinator (ZBDongle-P) and by putting it right next to the co-ordinator. It won’t clear the configuring state, but does appear after a ZHA reload. After doing that, it shows as an IAS zone with firmware and battery unknown. Reconfiguring it is unsuccessful. I think I’m going to give up now and look for a different contact sensor as these are way too unreliable for my use case (security).
I was also trying to connect my PARASOLL to ZHA and somehow managed to get it to work with a slzb-06. Got them into HA by following the steps mentioned above:
Additionally I did try different Channels and the first time I switched it from smart to 25 (and later 11, 20 and now on 15) the sensor started showing as IAS Zone. The headache started here as it was showing as on Opening sensor before so I thought I might have broken it.
Then I looked around and used the reconfigure feature and looked into the details. Previously it didn’t show much but this time there were some more checkmarks and I noticed the OnOff checked as well as IasZone (and some other green checkmarks).
So I click on Sensors → IAS Zone and then the cog on the top right and changed the Entity ID to binary_sensor.ikea_of_sweden_parasoll_door_window_sensor_onoff (previously it ended in something IAS related - I didn’t write it down). From changing the Entity ID to the new value the flipping thing started working going from On to Off when using it (Open/Closed respectively when set as a Door or Opening).
A few hours later it also shows the battery % and Firmware (Up-to-date Installed version 0x01000019).
So as an additional step I suggest checking if the Entity ID is set to binary_sensor.ikea_of_sweden_parasoll_door_window_sensor_onoff
I was so happy I had to create an account and share this info. Still not sure if it’s stable but at least it started reporting the correct state to HA.
I got my PARASOLL to pair and show as an opening, with the firmware version showing as up to date and the battery level showing. However, exactly 6 hours later and it’s showing as unavailable again. What’s interesting, is it took exactly 6 hours last time to show as unavailable, so it appears to be going in to some kind of sleep state.
EDIT: So that 6 hours appears to be the 21600 seconds I have set for “consider battery powered devices unavailable after” setting in ZHA. The question is, what value should I be using for the PARASOLL?
Funny, one shows battery, one does not…
I have a track record with 18 Parasoll sensors (and 4 wallhorns). They worked perfectly for about 2 years now with my Skyconnect stick (old FW). I have >70 zigbee devices in ZHA (besides Parasoll und Wallhorns a few lamps and plugs, lot of tuya thermostats, tuya and aqara thermometers)
For about one month two Parasolls started becoming unavailable und I fail to repair them. They show exactly this same behaviors (stuck on configuring). I bought few new ones, same problem.
Sometimes I get the new ones connected. I leave the pairing window open for a while with “interview complete - configuring” and than reload ZHA and they appear correctly.
this is no WiFi interference, no Zigbee dongle HW/FW problem, not even Parasoll HW problem I guess. Maybe incompatibility between some new devices?
