Ikea E1745 OTA disables motion detection

[RubenKelevra]

What happened?

I've got a message today regarding a OTA firmware update for my E1745 from Ikea (motion sensor). I've updated one of my devices.

After the update the device wasn't sending motion updates anymore, but it showed just 14% battery status (two CR2032). So I replaced them, but no luck, it still won't set any "occupation" status anymore. That's not just in HA but also in the Add-On UI not showing any updates.

The old batteries had still 2.9 V, so they should have still worked fine for a while.

No other device is affected, so it's not the 2.0 update, as far as I can tell.

I've also noticed that the E1745 is not on the changelog list and the firmware version number jumped from 2.x to 24.x.

Are we sure that's the right firmware?

@Koenkk sorry for the ping, but I think we may want to stop pushing this update until someone else confirms that it's working for them? 🤔

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

• Update from 20190308 / 2.0.022 to 20220928 / 24.4.5 via Z2M's OTA function

Zigbee2MQTT version

2.0

Adapter firmware version

20221226

Adapter

Slaesh's CC2652RB stick

Setup

Add-on on HA on a Raspberry 4B

Debug log

No response

[WoBBeLnl]

Had some same weird issueswith the E1745 after updating to 2.0.0. My sensor was up to date but I received an update for it which I installed. After updating this message showed up:

I had to repair my device and everything started working again EXCEPT for group binding. It only sends out to group 0 and not the previous 123 anymore.

z2m: Received Zigbee message from 'Trapkast TRADFRI motion sensor', type 'commandOnWithTimedOff', cluster 'genOnOff', data '{"ctrlbits":0,"offwaittime":0,"ontime":1800}' from endpoint 1 with groupID 0

[Koenkk]

Removed it!

[JornDL]

I have updated to 24.4.5 and have no issues

[RubenKelevra]

@Koenkk is there a way to force the older firmware onto that device somehow?

Or maybe force install the same firmware again onto it? Maybe the low battery status of my device was the culprit here and something went wrong flashing it? 🤔

[ashimokawa]

I also updated, and it still works well.

[ashimokawa]

I updated another one, also successful.

[stefangries]

Mine detect no motion anymore after the update.

[adizanni]

Also mine was not detecting motion after the firmware update. I'm trying to re-pair but it fails the interview

[adizanni]

Small update: after a few trials I managed to re-pair the device and now the occupancy works....

[stefangries]

Can confirm that deleting and repairing the device solves the problem.

[RubenKelevra]

I fixed the pairing instructions in the wiki, which were wrong. 10 seconds press on the pairing button is ZLL pairing. (Koenkk/zigbee2mqtt.io#3414)

I've tried to delete and readd the sensor, no idea why that would be necessary for a simple stability update thought...

Anyway, the interview failed on both attempts:

[stefangries]

@RubenKelevra Yes, that's a bit tricky. What worked for me was to remove both batteries from the device, then press the interview button, and then immediately reinsert (at least) one battery. Then the interview went through.

[Joska59]

@stefangries Wow, I laughed at first, but then it worked the same way with the first of 2 stubborn update refusers here. But that's more WooDoo than IT :-)

[stefangries]

@Joska59 Nice! I think the reason is, that the device is asleep most of the time and does not receive messages. After inserting the batteries the device is awake for a short time.

[kilkenny44]

After many tests evrything is working fine after reconfiguring binding
Latest firmware 24.4.5 is working except binding is not working to groups anymore but only to end device (I binded 5 end devices successfully to one sensor)
Precedent firmware binding was only working to groups -> behvior change
And the interview problem is solved by removing battery and insterting again as explain earlier (no need to press interview button for me)

[RubenKelevra]

I could successfully finish the interview by pressing the link button 4 times again and manually starting the interview in z2m. Took 2 tries.

Overall this firmware seems to be a lot more buggy than the previous one :/

@Koenkk how do we proceed now?