Support for Osram Smart+ Motion Sensor

[SwoopX]

Hi,

It would be great if those could be supported as well.

Let me know if anything else might be required.

Thanks!

[manup]

I have this sensor running in my home for two weeks now.
Currently it needs some manual fiddling to get it working, the plan is to add automated implementation in the next versions.

[SwoopX]

Sounds great, thanks. I'll put them aside for the time being.

[fabsfuchs]

Hey could you please describe the "manual fiddling" a little bit further? I added the sensor and its reporting changes in the presence. I can see this through the deCONZ GUI. When I am trying to get the sensor data through REST with a request. The answer is always the following:

{ "config": { "battery": 100, "duration": 60, "on": true, "reachable": true }, "ep": 1, "etag": "ae3fc0e6c983647d214c2489b8b97e11", "manufacturername": "CentraLite", "modelid": "Motion Sensor-A", "name": "Bewegungsmelder", "state": { "lastupdated": "none", "lowbattery": null, "presence": null, "tampered": null }, "swversion": "\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd", "type": "ZHAPresence", "uniqueid": "00:0d:6f:00:0e:05:89:73-01-0500" }

So the interesting values are always set with null.

[manup]

The most important step is configuring the ConBee as CIE in the motion sensor

• Open IAZ Zone cluster in Cluster Info Panel
• Double click on the IAS_CIE_Address attribute to open the attribute editor
• Write the mac address of your ConBee/RaspBee in attribute

This should be enough to make the motion sensor work.

I have also created bindings of the following clusters to the gateway via the Binding Dropbox:

• IAS Zone cluster (might not be necessary)
• Temperature cluster
• Power configuration cluster

[fabsfuchs]

Thank you very much for the fast response. After the CIE configuration it works.

I am a little bit confused about the reporting of the presence value (unoccupied). I think there are two values to influence this behaviour. The first is the "PIR Occupied to Unoccupied Delay" and the second the "config.duration" value of the sensor.

For testing purposes I set the "PIR Occupied to Unoccupied Delay" to value 2 and the "config.duration" via REST API to the value 60 (default I think).
The lower outputs are received from the websocket:

Unoccupied to Occupied:
{ e: 'changed', id: '3', r: 'sensors', state: { lastupdated: '2018-10-21T19:17:49', lowbattery: false, presence: true, tampered: true }, t: 'event' }
Occupied to Unoccupied:
{ e: 'changed', id: '3', r: 'sensors', state: { lastupdated: '2018-10-21T19:18:21', lowbattery: false, presence: false, tampered: true }, t: 'event' } presence = false

The difference is 32s. When I observe this in the deCONZ GUI I can see the the Occupancy value being 0x01 for just 2s. Exactly how I set it up. Why takes it 32s to report it via the websocket?

[derBroBro]

Are there any options to connect the sensor just by the rest module?

[manup]

Currently the GUI is needed to do the missing steps as described above.

Looking forward to add these steps to the automatic join process, as well as the temperature cluster setup, in the next two releases.

[manup]

The sensor is supported in 2.05.57 and added in the wiki supported devices section.