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 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.