Hi, I have a couple of Styrbar buttons which both suffer with the same issue. It takes several pairing attempts for the devices to only display one instance of a button press in the logs. I.e. one press can manifest as 2-4 presses in some instances. Some pairing attempts don't even work whatsoever.
However, after several failed pairing attempts and then having success. After a few days, the device seems to revert back to a single button press becoming several button presses as shown in the logs.
Sorry about this, it's a bug I introduced in v4.0.0. Will be fixed in the next release. Thanks for reporting!
I have a spare Styrbar that I can play with to see if I can reproduce this. Do you use the latest firmware version (2.4.5 - 117C-11CB-02040005) ?
I want to know if all the functions work well with no errors in the logs, and if there is some functionality missing. I also need the "Device Details" section (that you just posted) and the fingerprints to add to the drivers.
Thanks for recommendation! The fact that they don't sell them anymore probably tells you how long back I got these devices
Edit: Not sure if it's an issue with the devices I have but these are chewing through my batteries. At this rate I'll have to get a new battery every other day, if not sooner.
Hi, cheers for this. My firmware version is 117C-11CB-00010024 which seems to be an earlier version. I've hit the update firmware button but with no joy. How do I update to you're version above. Appreciated in advance
Firmware upgrades, that usually take about 100 minutes for battery-powered devices, chew a lot of batteries, not sure this is the case. What devices are you talking about?
Oh, no, all the devices I'm running through your drivers are running perfectly, even though I'm using the crap two-and-a-half year old Ikea batteries they came with. I was referring to the Symfonisk Gen 1 remote during normal operation. It managed to take kill the included Ikea battery in about ten minutes and took a brand new Panasonic CR2032 from 100 to 47 in about 15 minutes of moderate usage.
Anyhow, I think it's a documented issue with the other driver made by @birdslikewires - from what I gather from the thread, he recommends running it through Z2M now. Guess I shall set that up after procrastinating for a couple of more years
It's a firmware incompatibility, the problem exists with multiple non-IKEA controllers. The devices do appear to like Sonoff controllers, so some Zigbee2MQTT solutions work perfectly without firmware updates. I suspect they don't deep-sleep properly with the Zigbee hardware used in Hubitat hubs and the E1812 buttons exhibited the same problem.
Firmware update 24.4.5 improved battery life, though my E1744 is still on 2.3.080 and works perfectly via Z2M and the Sonoff ZBDongle-P. If you can get one to update it may work fine directly connected to your Hubitat hub, but I believe you'll need an IKEA hub or Z2M set up already to prompt the update... so it's one of those chicken-and-egg problems.
Nice one. On point three in the instructions you mention this:
If you don't see an "Update Firmware" command in the device details page, change the driver to "Device".
Anything snazzy need to be done in a driver to add that "Update Firmware" command? Just to avoid the need for users to switch driver, I could add it in next time I'm tinkering.
This version fixes a problem introduced in v4.0.0 that manifests when pairing the Vallhorn Motion Sensor (E2134) and the Symfonisk Sound Remote Gen2 (E2123). After upgrading to v4.1.1, you need to re-pair the affected devices.
There is no need to upgrade to v4.1.1 if your devices are already paired and work fine.
Good evening @dandanache. Thank you for all these drivers allowing you to use Ikea products. I really appreciate. I have a quick question about the IKEA Starkvind Air Purifier (E2006). There is a “Dark mode” function. However, it is not possible to create a rule to activate this mode during the night to keep the room in the dark. Is it possible that this feature can be turned on or off with a rule? Thanks in advance for the response!
Thanks very much for the update. I'll swap over to the new versions soon.
I'm wondering on the known issue for the Styrbar Remote Control where the hold and release events don't work properly. Is it possible to get that fixed? Is it an issue with the driver or something odd that the device does?
Getting the hold and release working would effectively add 2 more actions that could be triggered with the remote and make it more useful being able to effectively have an 8 button remote
When you press and hold one of the Left/Right buttons on the Styrbar, I takes about 2 seconds for the driver to figure out that you want to "hold", no way around this. If you assign the startLevelChange command to the hold event, you must keep it pressed even longer until the desired brightness is achieved.
The 2 seconds lag makes it unusable in my opinion (read as: the wife might start throwing things in my general direction ). That's why I didn't bother to implement the hack for it.
The Symfonisk Sound Remote Gen2 has about the same form factor as the Styrbar but 3 more buttons. Plus, the shortcut buttons support push, double-tap and held/release. Note that the up/down buttons only produce "held" events (every 300ms), but does not support "release".
In our bedroom we each use one of the Symfonisk Sound Remote Gen2 (E2123) to control music (same Sonos radio stream with country music that somehow calms us and makes us sleepy ), the ceiling light, and the 2 reading lights above the bed:
). That's why I didn't bother to implement the hack for it.
), the ceiling light, and the 2 reading lights above the bed:
