IKEA Trådfri motion sensor detection

[kabal00]

Hi all,

I have a strange behavior of my IKEA Trådfri motion sensor which has been perfectly synchronized with the deConz software (installed on raspberry pi 3B+). But after a motion has been detected all of my bulbs within deconz will be shown as triggered (ON), but they are definitely OFF. The bulbs are from OSRAM and IKEA and I am using Homebridge which works great, except this issue.

Does anybody know what I need to do?

Thanks in advance

[Cybersmurfen]

I got the same behaviour. All lights shows on when a motion is detected.

It is the new waterproof detector - FW: 2.0.022 - the old detectors runs FW: 1.2.214

[Cybersmurfen]

Well. I deleted the Trådfri sensor from deconz. If I don't reset the sensor it will keep triggering all lights.

[avakarev]

I have issues with new model of motion control too.
The old model E1525 (2017) is fine
The new model E1745 (2019, IP44) cause deconz to report bulbs are on while they are off. Also deconz doesn't report motion events following the first "presense: true" till "presense: false".

[ebaauw]

Maybe the new model sends different ZigBee commands/command parameters? It’s definitely different hardware, no dials, no duration setting, but a 30% vs 100% brightness setting. Do you have the sensor on Day or on Night setting?

[avakarev]

@ebaauw Hard to say if it's on Day or on Night, there is no indicator anymore on the back. Now there is just a toggliing button, and I think it's supposed to be indicated by gateway/app what's the current settings (and it doesn't indicate it for a moment). In my case, it's set by default, I didn't modify it. The older E1525 has default mode is set to "on Day". Here is how back side looks of E1745 now:

[avakarev]

@ebaauw This is how response of GET /sensors/<id> looks like:

{ config:
      { alert: 'none',
        battery: 87,
        delay: 180,
        duration: 60,
        on: true,
        reachable: true },
     ep: 1,
     etag: '32101bc3e3b2992cb8f7efd5e68cb04d',
     manufacturername: 'IKEA of Sweden',
     modelid: 'TRADFRI motion sensor',
     name: 'Bathroom Motion Sensor R',
     state:
      { dark: true,
        lastupdated: '2019-07-14T21:08:45',
        presence: false },
     swversion: '2.0.022',
     type: 'ZHAPresence',
     uniqueid: '14:b4:57:ff:fe:52:3c:3a-01-0006' }

[Cybersmurfen]

@avakarev - if you push the toggle button once, the sensor shows if it is day or night with a small red indicator just next to the button. If you push it again it changes mode.

[ebaauw]

Hard to say if it's on Day or on Night, there is no indicator anymore on the back. Now there is just a toggliing button

The IKEA "manual" seems to suggest there's a LED that lights up. Maybe I'm too optimistic reading it.

This is how response of GET /sensors/ looks like:

Thanks. Some observations:

• Unsurprisingly, it has the same manufacturer name and model (or the REST API plugin wouldn't have exposed it already).
• config.delay is consistent with the fixed duration of 3 minutes from the manual.
• What really worries me is the lack of a config.group, suggesting the sensor hasn't been bound to one. The old model would select a random group on reset and send groupcast commands by default, but apparently this model sends a broadcast by default (which causes deCONZ to mark all lights as on). But somehow the lights themselves don't turn on...
• state.dark is true which means that either:
  • The sensor is on Day mode;
  • The sensor is on Night mode, and it's actually dark enough to turn on the lights.

Can you try the following:

• In the GUI, bind the client OnOff cluster of the motion sensor to a group. Trigger the motion sensor and check that config.group is created.
• Run deCONZ with --dbg-aps=2 and observe the logfile for something like:

  Jul 15 12:09:00 pi1 deCONZ[1121]: 12:09:00:346 APS-DATA.indication srcAddr: 0xe9b9, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -55
  Jul 15 12:09:00 pi1 deCONZ[1121]: 12:09:00:346 	asdu: 0162420058020000
  Jul 15 12:09:00 pi1 deCONZ[1121]: 12:09:00:347 button 1002 On with timed off
  

  The asdu means the following:

  0162420058020000
      | | |   + 0x0000: _Off Wait Time_: 0.0s
      | | + 0x0258: _Timed Off_: 60.0s (i.e. `state.delay` ==> 60)
      | + 00: _Accept only when on_ is not set (i.e. `state.dark` ==> `true`)
      + command: 0x42: _On With Timed Off_
  

• Add a light to the group, and see if the motion sensor will control it. Even if the light won't turn on, the REST API plugin should only mark the light(s) in the group as on, instead of all lights.

[tubalainen]

Hard to say if it's on Day or on Night, there is no indicator anymore on the back. Now there is just a toggliing button

The IKEA "manual" seems to suggest there's a LED that lights up. Maybe I'm too optimistic reading it.

This is how response of GET /sensors/ looks like:

Thanks. Some observations:

• Unsurprisingly, it has the same manufacturer name and model (or the REST API plugin wouldn't have exposed it already).

• config.delay is consistent with the fixed duration of 3 minutes from the manual.

• What really worries me is the lack of a config.group, suggesting the sensor hasn't been bound to one. The old model would select a random group on reset and send groupcast commands by default, but apparently this model sends a broadcast by default (which causes deCONZ to mark all lights as on). But somehow the lights themselves don't turn on...

• state.dark is true which means that either:

  • The sensor is on Day mode;
  • The sensor is on Night mode, and it's actually dark enough to turn on the lights.

Can you try the following:

• In the GUI, bind the client OnOff cluster of the motion sensor to a group. Trigger the motion sensor and check that config.group is created.

• Run deCONZ with --dbg-aps=2 and observe the logfile for something like:

  Jul 15 12:09:00 pi1 deCONZ[1121]: 12:09:00:346 APS-DATA.indication srcAddr: 0xe9b9, srcEp: 0x01 dstAddrMode: 1, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -55
  Jul 15 12:09:00 pi1 deCONZ[1121]: 12:09:00:346 	asdu: 0162420058020000
  Jul 15 12:09:00 pi1 deCONZ[1121]: 12:09:00:347 button 1002 On with timed off
  

  The asdu means the following:

  0162420058020000
      | | |   + 0x0000: _Off Wait Time_: 0.0s
      | | + 0x0258: _Timed Off_: 60.0s (i.e. `state.delay` ==> 60)
      | + 00: _Accept only when on_ is not set (i.e. `state.dark` ==> `true`)
      + command: 0x42: _On With Timed Off_
  

• Add a light to the group, and see if the motion sensor will control it. Even if the light won't turn on, the REST API plugin should only mark the light(s) in the group as on, instead of all lights.

Hi! Can confirm that the new IKEA sensor is behaving oddly. It does not create the config.group and "ghosts" all lights in deconz to "ON" on motion detected. Ive tried the @ebaauw way described above with no success.

How ever, can confirm that the sensor is VASTLY more sensitive than the old one. Hoping for a solution. <3

[avakarev]

@ebaauw

The IKEA "manual" seems to suggest there's a LED that lights up. Maybe I'm too optimistic reading it.

I can confirm the back side shows the state and it was on Day mode.

Unfortunately I don't have the access to conbee stick / deconz at the moment so can't provide the logfile / debug output. Hopefully some users of E1745 sensor can help with that.

@ebaauw Thank you for your involvement and attempt to help!

[Ergerbolt]

Hi there,

same problem for me. Exactly same behavior.

[JustAnotherUserName87]

Hi,

I have the same problem. Unfortunately I only have the newer sensor.

[LJSven]

Same here!