The change to the existing illuminance sensor in the Tuya rain sensor (RB-SRAIN01) is not correct.

[wesleyRaposo]

What happened?

Until version 2.7.0-1, the existing illuminance sensor in the Tuya rain sensor (RB-SRAIN01) worked correctly with Zigbee2Mqtt.

From version 2.7.1 onwards, the sensor started having problems with Home Assistant because they changed the illuminance unit from "lux" to "mV" (millivolt), which would be its correct unit.

Since Home Assistant does not recognize this unit (mV - millivolt), they removed the original illuminance sensor with the "lux" unit and created a new sensor called "Raw Illuminance," which was released in update 2.7.2-1.

The problem is that this "new sensor" does not report any unit. Because of this, Home Assistant does not recognize it as a sensor that records history. Therefore, it cannot be associated with any card that generates a graph with the measurement history, as it is only a numerical sensor.

Although we know that this device does not record illuminance in "lux" but rather in "mV" (millivolts), I would like the original "lux" sensor to function again, as what interests us is being able to record the measurement history. This is essential for fine-tuning our automations and being able to compare what is recorded at different times of day with different sensors spread out.

To avoid displeasing anyone, the current sensor called "Raw Illuminance" and the original illuminance sensor associated with the "lux" unit can coexist peacefully in the same device, and each user can adopt what is most convenient for them.

Thank you.

Device:
https://www.zigbee2mqtt.io/devices/RB-SRAIN01.html#tuya-rb-srain01

What did you expect to happen?

That the illuminance unit be properly recognized by Home Assistant (as it was before) so that I can continue to have access to the measurement history through graphs.

How to reproduce it (minimal and precise)

Install the Tuya TS0207 rain sensor and update Z2M to version 2.7.2-1.

Zigbee2MQTT version

2.7.2-1

Adapter firmware version

EmberZNet 7.4.5 [GA]

Adapter

Zigbee2MQTT Bridge (Dongle M)

Setup

Hardware: Raspberry Pi 4b.
Método de instalação: Home Assistant OS
Core: 2025.12.4
Supervisor: 2025.12.3
Operating System: 16.3
Front-end: 20251203.3

Device database.db entry

No response

Debug log

It's not necessary.
It's not a device error, but a change they made to its illuminance sensor.

Notes

[Sergey7up]

Setting "state_class": "measurement" in sensor definition fixes problem:

Success unitless graph:

[wesleyRaposo]

@Sergey7up
This is an edit I've never made before.
I searched the configuration files, but I couldn't find any formal device definition that I could edit.
Where can I find this information?

[keidischoi]

@Sergey7up This is an edit I've never made before. I searched the configuration files, but I couldn't find any formal device definition that I could edit. Where can I find this information?

Create and use a template sensor.

• sensor:
  • name: "Rain Sensor"
    unique_id: rain_senseo_illuminance
    device_class: illuminance
    state_class: measurement
    unit_of_measurement: "lx"
    state: >
    {{ states('sensor.rain_senseo_illuminance_raw') | int }}

[wesleyRaposo]

@keidischoi
Thank you for your contribution.
I already know this solution, but I wanted to avoid yet another helper entity (because I already have dozens) that would only serve to cover a deficiency in the sensor.
From what I understood of the previous proposal, it seems there's a way to directly interfere with the sensor and include the information I need. I want to learn how to do that.

[keidischoi]

@keidischoi Thank you for your contribution. I already know this solution, but I wanted to avoid yet another helper entity (because I already have dozens) that would only serve to cover a deficiency in the sensor. From what I understood of the previous proposal, it seems there's a way to directly interfere with the sensor and include the information I need. I want to learn how to do that.

Using an external converter causes the sensor values ​​to freeze. I'd say this is the best solution.

[wesleyRaposo]

@keidischoi
I didn't know that detail. Thank you.