[Problem Report] Smartthings Multipurpose Sensor IM6001-MPP02 Wrong Naming & Sensors Not Reporting

[K-BIB]

What happened?

First thing noticed, device is physically labelled as IM6001-MPP02 but IM6001-MPP01 in Zigbee2MQTT device list. https://www.zigbee2mqtt.io/devices/IM6001-MPP01.html

Main issue is echoing mostly; #25277

Pairing using instructions; "When pairing, make sure to keep the sensor awake for 20 seconds by opening and closing the contact every second. Reset Procedure - https://www.youtube.com/watch?v=yT3iVHuO7Qk" Several resets completed

These are not reporting anything:

battery (Null %)
moving (Null)
X axis (Null)
Y axis (Null)
Z axis (Null)

These are working:

temperature
contact
battery low
tamper
linkquality

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.2.1

Adapter firmware version

TBC

Adapter

SLZB-06M

Setup

Mini PC plain

Debug log

No response

[toxic0berliner]

I just realized #25277 is closed so I can report I have the exact same behavior.
If someone with skills is able to find a solution that would be awesome 👍
For what it's worth someone seems to get them working after pairing with zha. Maybe something in the pairing/interview process isn't done right here.

[thepiecesofme]

I am also having the exact same issues with this sensor. I posted on this at the previous issue link here: #25277 but as others have reported, it’s since been closed so no further help. I need to purchase some additional multi-sensors like this but am concerned since these don’t seem to fully work at this point. Oddly, the older versions of this same sensor (different shape but were sold under the same SmartThings Multi Sensor name) all work perfectly.

Any help would be hugely appreciated. Thanks in advance!

[toxic0berliner]

Today I found this in my logs trying to pair this device again...

error 2025-06-02 17:16:36z2m: Failed to configure '0x286d970001001c45', attempt 5 (
Error: ZCL command 0x286d970001001c45/1 genPollCtrl.write(
  {"longPollInterval":3600},   
  {
    "timeout":10000,
    "disableResponse":false,
    "disableRecovery":false,
    "disableDefaultResponse":true,
    "direction":0,
    "reservedBits":0,
    "writeUndiv":false
  }) 
failed (Status 'READ_ONLY') 
  at Endpoint.checkStatus (/app/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:363:28) 
  at Endpoint.zclCommand (/app/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:987:26) 
  at processTicksAndRejections (node:internal/process/task_queues:105:5) 
  at runNextTicks (node:internal/process/task_queues:69:3) 
  at processImmediate (node:internal/timers:453:9) 
  at Endpoint.write (/app/node_modules/.pnpm/zigbee-herdsman@4.1.0/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:406:9) 
  at Object.configure (/app/node_modules/.pnpm/zigbee-herdsman-converters@23.53.0/node_modules/zigbee-herdsman-converters/src/devices/smartthings.ts:308:13) 
  at Configure.configure (/app/lib/extension/configure.ts:124:13) 
  at Configure.onMQTTMessage (/app/lib/extension/configure.ts:49:25) 
  at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:204:17))

I can confirm the device is sending some movement events when paired using ZHA so it's not a defective device, just Z2M not able to "configure" it to report those settings.

Maybe the above log is blocking the configuration from moving forward and maybe not, maybe it makes sense to someone who can find a solution...

[Koenkk]

@toxic0berliner pushed a possible fix, can you check if it works?

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.

[toxic0berliner]

Will try to switch to the z2m-edge plugin and get down in the basement restart a pairing process, might take me a while to achieve, newly a dad and time for such things is getting thin, but thanks a lot for the attempt Koenkk !

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[toxic0berliner]

Oups, forgot about this, I guess this is in the release now, will try that.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days