Third Reality Multi Function Night Light (3RSNL02043Z) – motion sensor not exposed in deCONZ

[Fabrizioso]

Is there already an existing issue for this?

• I have searched the existing issues and there is none for my device

Product name

Third Reality Multi-Function Night Light

Manufacturer

Third Reality, Inc.

Model identifier

3RSNL02043Z

Device type to add

Light

Node info

I’m using two Third Reality Smart Night Light devices (model 3RSNL02043Z) with deCONZ 2.32.0 (RaspBee firmware 26780700).
Pairing works fine and the devices are exposed as lights in Phoscon, but the motion / presence sensor is not exposed at all (no sensor created, nothing under /api/sensors).

In the deCONZ GUI (network map → device → expand node), the following clusters are visible:

0000 Basic
0003 Identify
0004 Groups
0005 Scenes
0006 On/Off
0008 Level Control
0013 Multistate Input (Basic)
0300 Color Control
0400 Illuminance Measurement
1000 Touchlink Commissioning
FC00 (manufacturer-specific)
0019 OTAU

There is no IAS Zone (0x0500) or Occupancy (0x0406) cluster exposed in deCONZ, and no motion events reach the REST API.

However, Zigbee2MQTT seems to support this exact model and exposes occupancy/presence. There is also a specific Z2M converter fix for the 3RSNL02043Z occupancy reporting.

This suggests the motion sensor is reported either via a secondary endpoint or manufacturer-specific handling that deCONZ currently does not enumerate or decode.

Happy to provide additional information, let me know how I can help!

Endpoints and clusters

Basic

Further relevant clusters

[mattreim]

@Fabrizioso Please add all screenshots (0006, 0008, 0013 and 0300) with the correct values. To do this, press the "Read" button in deCONZ and press any button on the sensor until the attributes are either recognized or grayed out.

[Fabrizioso]

Hi @mattreim , thanks for the reply, here are the screenshots:

Let me know when you need anything else!