Thanks I will doublecheck the firmware again in a little bit. I actually was able to get the motion sensors “seen” by simply pressing the buttons on the inside right before pressing the “update firmware” button. However it would come back that there wasn’t any firmware available.
I might try to figure out how to update them via Zigbee on HA just for this one instance. I tried before but it was like pulling teeth. Your method is soooo much easier.
That's much easier than fiddling with the batteries. Nice find!
Can you please post the full message that says that there is no update available? I want to see your current version.
I worked on the motion sensors before seeing your message request and posted to the IKEA firmware update thread on here. Firmware updates were discovered when I finally got this working through HE.
In brief, I had to uninstall the on/off button drivers and THEN I was able to pair the E1745 Motion Sensors via Zigbee (doesn’t show up anything specific at first.) Switch to the Motion Sensor driver then it’s very finicky to update them (but not impossible.) It seems like hitting the center button then the update firmware button, NOT switching to logs just yet, followed by slow intermittent pressing of the center button (and not triggering a reset) keeps the device alive enough for firmware information to be sent and received. Only after fussing with this, then I would check the logs to see if it was updating. But it requires a lot of patience as the reporting for these Motion Sensors is a LOT slower than other IKEA wireless device firmware updates so you don’t know if it’s even working.
On a related noted, I noticed in the logs these Motion Sensors with your E1745 drivers are pulling up the following errors:
WARN: java.lang.numberformatexception: null on line 296 (method parse)
That error was fixed in release 3.4.0.
Do you have the most recent version installed?
I had 3.4.1 installed.
I need more information in order to figure out what is happening. It would help me if you:
msg=[[raw:catchall: ... ]] or description=[catchall: ... ]Thank you for your help!
Looks like the device is configured to periodically report the value for attribute "0x0020" of cluster "0x0001" (battery voltage). Probably a config from another driver as we use attribute "0x0021" (battery percentage) instead.
Thanks for the report, I'll add something in the next version to cope with this situation.
No way,I should be thanking you!
dev:17302023-11-25 05:57:57.068 AMinfoIKEA Motion Sensor Living Room is active [physical]
dev:17302023-11-25 05:57:57.039 AMdebugIKEA Motion Sensor Living Room illumination is dim [physical]
dev:17302023-11-25 05:57:57.033 AMdebugIKEA Motion Sensor Living Room msg=[[raw:catchall: 0104 0006 01 01 0040 00 DE03 01 00 0000 42 00 0008070000, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:DE03, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:42, direction:00, data:[00, 08, 07, 00, 00], endpointInt:1, commandInt:66]]
dev:17302023-11-25 05:57:57.027 AMdebugIKEA Motion Sensor Living Room description=[catchall: 0104 0006 01 01 0040 00 DE03 01 00 0000 42 00 0008070000]
I tried to update an old E1524 . Is it possible to to update with the E1810 fimrware? I added successfully to hubitat, configured and startet the update. Battery is full , but even waiting for 20 minutest didn't bring up any update information. Battery level went down and up again like crazy.
After a while no new status in the log file regarding battery.
What am I doing wrong? Thanks for any input
Released version 3.4.2 with the following changes:
updated() - reported by @leo_charlesIt should be possible to update the firmware on E1524 devices. You just need to make sure that the device is not "sleeping" when you start the update process: press any button on the remote or remove/reinsert battery just before/after clicking the "Update Firmware" button. Repeat, retry different things, keep calm.
I suggest to ask for help on the other thread, since that topic was created to help folks with firmware update issues. Be sure to include details with what you tried and what went wrong; don't just say "it does not work", be specific and don't worry, you're amongst friends here; we'll make it work 
G'day from down under, I tried your drivers, excelent work !
Tradfri Motion Sensor (E1745), here the part number is different 903.704.69, it comes up as
Data * endpointId: 01
I have mine working although it was spitting out warnings which I think Dan fixed.
If you’re having problems pairing, read our posts above. Most importantly what I found was that those sensors were importing as open/close Ikea switches. So I had to delete that ikea switch driver then try to add the motion sensors again. THEN, the motion sensors were detected.
The next issue was that you HAVE to update the firmware on the motion sensors to the most recent version and quite honestly it was a pain: its not always responsive when it actually is, sometimes you end up accidentally canceling the firmware install if pressed at the wrong time, etc. Then the firmware probably takes about an hour on full batteries to update. I put new batteries in and it showed a low and plummeting charge, but after the firmware was updated, the next morning it had shown 100% again. I managed to get two paired and updated, but it took a long time and a lot of quiet swearing 
.
I installed a Styrbar today and noticed it was sending double events for each button press, just re-paired it and now it's just one so that worked great. Still running the older as-shipped firmware: 117C-11CB-00010024. Dan, do you know if hold for buttons 3 and 4 (next and prev) will work with the latest firmware?
I have one on the latest firmware.
I'll pair it to Hubitat and see.
Buttons 1 & 2 work as expected.
Buttons 3 & 4 don't seem to register correctly.
Also got this in the log:
[dev:809] 2023-11-26 11:27:55.048 PM [warn] Styrbar sent unexpected Zigbee message: description=catchall: 0104 0005 01 01 0040 00 F115 01 00 0000 05 00 0000000000, msg=[raw:catchall: 0104 0005 01 01 0040 00 F115 01 00 0000 05 00 0000000000, profileId:0104, clusterId:0005, clusterInt:5, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F115, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:05, direction:00, data:[00, 00, 00, 00, 00], endpointInt:1, commandInt:5]
Thank you for trying it Brad. Unfortunately, the Styrbar is a bit weird and has these 2 issues:
According to my tests, it takes about 2 seconds from the moment button 3 or 4 is pressed (and held) and the moment the driver has enough information (message #4) to determine which of the two buttons was held. Add the Zigbee mesh delays, and this makes the hold & release usage very weird. So I thought that is does not worth the effort to implement a hack around it.
I hope IKEA will release a new firmware to fix both these issues.
G'day again !
Thanks for your advise, I paired the sensor to an Ikea hub and 5-6 hours later it had updated the firmware. Paired with Hubitat first time around, it works a treat !!!!
thanks gain
Any early indications if the new set of sensors will be easily supported?
See: Ikea debuts a trio of affordable smart home sensors - The Verge
Download the Hubitat app
