[RELEASE] IKEA Drivers with Health Status and Zigbee2MQTT

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! :slight_smile:

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.

1 Like

It's odd that the old IKEA gateway takes forever to update the firmware on devices, yet their new Dirigera hub does it almost instantly.

Wanted to check in and see if the battery issue is still affecting the E1766s.

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%. :man_shrugging:

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.

I wonder if they dropped from your mesh in that case. Who knows what the cause could be there.

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