Someone on the home assistant forum noted that they made a change to the ZHA configuration so that the ikea buttons cannot connect directly to the coordinator.
This supposedly resolved the battery drain issue.
Not something we'd have access to on Hubitat though.
I haven't had a chance to try this myself on my HA install.
Apologies, if this is a wrong discussion group. I have E1810 5-button button and trying to find Hubitat C7 driver for it. Any help ? or I am simply out of luck.
I’d heard they were incompatible with the way in which Hubitat passes on messages to custom drivers, so I’ve never bothered picking one up.
Now, from our recent work with the previously-incompatible blind control button it would seem this may not be the case with IKEA’s newer firmware. However, nobody has yet overcome the bizarre battery drain issues, so I give hope with one hand and take it away again with the other.
Hey there, no, I’ve not got one I’m afraid. Given the blind controller gives me the same battery issues as the rest of the Tradfri kit I’m not hugely enthused about spending more time on them at the moment.
I’ll keep an eye on other projects though, and will definitely take another look if a battery solution appears. Thanks for the offer of sending one - it’s likely to cost you more than the thing’s worth to get it to the UK!
I don't mind at all, it's the least I can do for the community and especially people who are actively working to make things better for the rest of us. I got the buttons free with the blinds but ironically am using Sonoff buttons to control them (single tap to open - double tap to close).
I also have the dimmer but I am afraid it suffers the same fate as the button with the battery drain though I have not yet tried updating the firmware on it.
With the Tradfri repeater, would it be possible to keep the "Get link quality", "Get route table" functions back with your presence driver?
That's typically how I test if the repeaters are actually responding on the network and other troubleshooting.
I updated my two repeaters to this driver, both show present even though I know one is misbehaving. How long without a check in before it changes to not present?
The link quality should be doable. Never done the route table so I'd need to research how to get that data.
Should be 30 minutes or so. From the code it's set to expect messages every 10 minutes. It accepts that one message may be lost and then the check only runs every few minutes, so ballpark half an hour for these.
There were some big updates to the firmware on these devices at the end of May 2023, with the E1744 sound remote being updated to v24.4.5 plus the E1716 and E1812 being updated to v24.4.6. Battery optimisation and stability improvements are the touted features.
Now here's the rub. To update you either need to unpair the devices from Hubitat and pair with an IKEA gateway, then wait patiently for days, or unpair the devices from Hubitat and pair with a Zigbee2MQTT system and push the update using the OTA feature. Or you could implement OTA firmware updates for IKEA devices in Hubitat... no, I didn't fancy doing that either.
But if you go the Z2M route these very drivers can be used with my MQTT routing driver without bothering to update the firmware at all. They work perfectly.
The choice is yours!
BTW, all of these drivers have now been updated to support the healthStatus custom attribute, so will no longer misuse presence as a means of reporting device connectivity. Use @kkossev's Device Health Status to give yourself a nice system overview.
I never got to the bottom of it on HE, I'm afraid.
There's new firmware out for IKEA devices which mentions something about battery life in the changelog, but I've been using mine connected via Zigbee2MQTT for nearly a year. Since I paired them with that rather than direct to HE, all my battery woes vanished.
My most problematic button was for the loft (attic) lights. That's had the same battery since March and is currently reporting 73%.
I'd love to hear if the new firmware helps, though.
I'll give it a shot and see how it goes! Real question is if I do the firmware update from my Digera hub, or from Hubitat.
One interesting surprise. I just paired them all with Digera again, I had thought they had been paired with Hubitat with drained batteries. Apparently all the batteries are actually fine, which makes me wonder what's up as none of them were dead.
Further little update, looking at them in Hubitat it all shows activity on each today, now if that's Hubitat trying to readopt them when I went into pairing mode on the remote, or if it's a button press as I unscrewed the back I'm not sure. Firmware in Hubitat shows as: 117C-11C5-24040005