Plug it in a different outlet, closer to the hub; maybe the Zigbee signal is bad where you tried.
Any errors or warnings in the Live Logs when you pair the device, or after the first on/off?
Does the state change in Hubitat if you click the on/off button on the device?
I see that you have firmware 2.4.4 but latest is 2.4.25. Maybe try a firmware update immediately after pairing it.
Maybe you got a dud, if everything else fails, try to take it back to IKEA and get a replacement (if you still have the receipt, or scanned your IKEA Family card when you purchased it)
From the logs, looks like HPM first downloads the drivers code, but it fails to install them. It fails at the very first driver it tries to install (E1836).
actually update firmware right after detection did the trick. not sure if its really updated the firmware or not, but its working since . knocking on wood. Thanks!
Thanks for your work on the Ikea Vindstyrka (E2112)
Just dropping this to convey what I'm seeing in the Device Status field on the Device page
span style="color:green">good</span
EDIT: OOPS, taking out the lt/gt symbols leading/trailing the above line....cause I placed it above exactly as it showed up in that field and obviously got interpreted by this Forum tool as HTML....whereas it did not seem to be getting interpreted in the Device List. Sorry.
A picture is worth a 1000 words. Shoulda remembered.
The device is sending some attribute reports, although the driver did not asked for these periodic reports. Nothing to worry about, will be fixed in the next release.
I have been getting these errors every 24hrs across most but not all of my IKEA devices. I have the same model outlets where one throws this error but the other doesn’t. This is occurring across both battery and powered IKEA devices. Same issue and fix?
I was able to pair the Parasoll contact sensor but it is not reporting open/close. I did get the Tretakt Smart Plug paired and working properly. What am I doing wrong on the contact sensor?
Here are the logs. I tried re-pairing it this morning. I also tried clicking the pair button and opening closing the contact followed by configure like it says in the logs but that didn't work either.
What does the "Ias" attribute reads for this device?
If you're pairing against a C-8, you can try the double-luck voodoo trick:
If that fails (or does not apply), try to power off the hub (Setting -> Shutdown), wait for the red LED on the hub (shutdown complete), remove the USB power cable, wait 30 seconds, re-insert the USB cable and wait until the hub starts up (green LED). This will reset the Zigbee circuit/board inside the hub, maybe it got stuck in a weird state.
If that fails, try to use the "Advanced Zigbee pairing" function from the Zigbee Map app, to make really, really sure that the device is pairing against the Hubitat hub, and not one of the close by repeaters.
It's also possible you got a bad unit, and can replace it in an IKEA store (if you still have the receipt).
Got it! Reboot did not fix it. I went to Zigbee Map app and realized, because I had never paid any attention prior, that there was a pair strictly to the Hubitat. Only reason I'd ever been in there was to pair my Aqaras to a specific repeater (the Tradifir outlets). OF COURSE the 2 that were being pains paired and are holding since I bought the Parasolls. They saw the proverbial writing on the wall...... But I do like the visual confirmation of whether or not something is closed with the Parasoll sensors. Going to put some on a greenhouse we'll be erecting in the spring so I can get alerts about temp vs vents and doors opening. Thank you and @Ranchitat for helping troubleshoot!
Early on myself and others were seeing false motion events with the vallhorn motion sensor. Especially with alkaline batteries.
I just picked up another sensor and noticed it has a different firmware version. On a whim I put alkaline batterys in it. A week in and no false triggers...
My original units show version:
117C-1938-01000057
The new one shows:
117C-1938-01000064
Can't find much on the changes but perhaps it's a hardware change too *64 shows added support for new revisions
Edit. I'm an idiot and didn't look in the firmware thread lol