[RELEASE] IKEA Drivers with Health Status and Zigbee2MQTT

Yeah that is what I have read. I paired one with the HE and it sort of responds... If I do configure it will respond to the HE. But it doesn't seem to work directly so it started to make me think it is a driver thing. That is what led me down the path to try to sniff the Zigbee traffic to see if it is sending something and then I could learn how it works and try to make a driver. I have a bunch of them sitting around as extra from when I installed blinds in our house.

Reporting in after 50 days since I've updated the firmware and put fresh batteries into my Tradfri buttons and they all report 100% battery, 3.0-3.1v. That might be odd as I'd expect the battery to decrease over time, but let's see where it brings us. I'm using Ikea 3032 battery cell if that matters.

The only thing I could think that make the battery last is my zigbee mesh network is quite strong as I have Zigbee thermostats in each rooms of my house.

I'll continue reporting until the battery wears out. Remind me if I forget @birdslikewires !

2 Likes

I'm going to give this one here another roll of the die starting today, but on my much weaker Xiaomi mesh. It shouldn't (ha!) upset the Xiaomi devices as it won't try to route anything and the only routers on that mesh are two IKEA E1746 ones anyway. So in theory they should play nicely.

Here we go, @bi0hazard! New battery starting at 3.35 V. Paired with the four-press-reset and nothing else (no press-and-hold like the Tradfri hub wants you to do). Using my driver v1.01 - there is an unreleased v1.02 which supports the new double-press in v2.3.080, but I'm not quite done with that yet.

For the sake of testing the Battery, maybe you should let the button next to the hub?

I just remembered that after pairing the button next to the hub, I repaired the button when it was sitting in it's room to make sure it wasn't trying to contact directly the hub, but using the nearest repeater.

I'm eager to try v1.0.2 with the double press!
Again, thanks for your hard work!

Can the buttons only be updated with a Tradfri hub?

If you're also playing in the Home Assistant sandbox, they can be updated via ZHA or zigbee2mqtt if you happen to have a USB coordinator.

I've updated my buttons from the Tradfri hub as well as via zigbee2mqtt.
Either way is painfully slow and a battery killer.

Ah okay. I unfortunately have not set up Home Assistant. I returned all my Tradfri buttons due to the extremely poor battery life but the recent posts have sparked my interest again. I’ll keep watching this thread for awhile to see the further results you guys share. If things seem promising enough maybe I’ll grab a bunch again and a hub since the hub isn’t that expensive anyways. I originally bought the buttons to give my toddler daughter the ability to turn the lights on in the rooms she’s commonly goes in. I liked the look of them for something that I was going to mount 10+ around the house. Fingers crossed they continue to perform as well as has been posted recently!

It's done and... I don't know what I was talking about, it's v1.09 now. It's been a few weeks, I've lost track. :slight_smile:

It should work with both pre-doubleTap and doubleTap (>=v2.3.080) firmware, but do let me know if any errors show up. I foolishly updated all of my shortcut buttons; should have left one on a lower revision.

Sadly the older firmware will show in other apps as doubleTap capable now as I've not figured a way to prevent this based on firmware version. Hopefully that's not a big deal.

Now 2.26 V. Dead. Lasted 48 hours.

The button didn't have a nice time on this mesh. Kept dropping and I'm now down to my last new CR2032! Perhaps the Xiaomi buttons were laughing at it.

Moved to my AlertMe mesh now, the final attempt. Some things really like it on here, though it's a busy place. There's one IKEA repeater, but all other repeaters are original AlertMe models. The Mijia light sensors really like it, let's see what this fussy thing thinks.

2 Likes

I updated to the latest driver and added a new shortcut button to Hubitat.

Button firmware is 2.3.015.

After pairing, it reported the battery was dead.
Popped it out and put it back in.

Battery has been reporting 100% for the last 24 hours.

I created a couple Button Controller rules for it as well.
So far it's all working well.

2 Likes

It hasn't dropped once. Still reporting 3.10 V. Weird.

I'm using Sinope thermostats and no Ikea Repeater in the mesh. Batteries are all still going strong on all my buttons!

What battery make are you using? I'm using Ikea and they're good.

Day 4, battery has dropped to 89%.

These are Panasonic, not sure where I got them from.

Interestingly, on this AlertMe mesh my first one still reports 3.10 V. I moved that first one to the loft (where it's supposed to live) and set up a second one, which I'm using to trigger a device I'm testing.

Both are working well. Perhaps I should have thought about using the AlertMe mesh earlier, as the loft one would always die very quickly indeed, but there are two AlertMe SmartPlugs up there that may be helping matters. Though the routing table doesn't tell me who it's chatting to.

It's gone up! :joy:

image

Your mesh is so strong it charges batteries :rofl:

2 Likes

My hub restarted today following a brief power outage.

My battery is reporting 100% /3.00v again :joy:

Okay, nine days later and the one for the loft lights is reading 3.10 V. My test device one is at 2.90 V.

It's dead, 2.11 V. Weird.

Up in the loft we're still at 3.10 V and working just fine. Both batteries were from the same strip of Panasonics. My best guess is that there's way more potential for interference in here than upstairs.

I had a button on the latest firmware that was doing well but was discharging fairly quick.
It fell off the network on the 21st.

The button I have that is on firmware 2.3.015 stopped reporting voltages on the 23rd.
It still had some life in it though, as I was able to pair it to my new Aeotec hub with Edge drivers.