A quick question, I have several Z2M devices in the same room, namely:
Aqara door & window contact sensor (Xiaomi MCCGQ11LM)
Temperature & humidity sensor with display (TuYa TS0201)
Aqara human body movement and illuminance sensor (Xiaomi RTCGQ11LM)
The problem is that three of these elements have a temperature in their features, but only one is a real temperature from a temperature/humidity sensor (TuYa TS0201).
But on the Room Temperature Widget, it’s the temperature of one of the other sensors that is used. Is there a way to specify the device to use in this box or to remove features from the other devices?
So, if I understand correctly, the temperature value of Xiaomi sensors other than the temperature sensors is the temperature of the printed circuit board.
The temperature reporting feature is actually the internal temperature of the device, not the ambient air temperature, and is only reported once an hour. So it is not useful.
This is mainly used as an indication because the sensors are designed to operate within a temperature range of -10 to 45°C (from memory).
Therefore, I think it would be necessary to have the possibility to select a list of devices in the box to average them, as not everything can be used currently.
The problem, in my opinion, is not from there, it’s more of a feature classification issue (these sensors are not really temperature sensors in the « ambient air temperature » sense, they are device operating temperature sensors)
Because this box is not the only place where we average temperatures.
Example: In the chat, you can tell Gladys: « Give me the temperature of the living room », and she will answer.
To do this, she averages the temperature sensors in the room, and since it’s not in the UI, she must have a way to know which sensors are ambient temperature sensors, and which sensors are « internal » temperature sensors.
So, to solve your problem, we need to create a new device_feature category (something like « internal temperature » / « internal_cpu_temperature »), and in the Zigbee2mqtt integration, we need to re-classify these features so that Gladys does not confuse them with ambient temperature sensors.
Yes, this issue has been resolved. However, it is possible that you have devices whose temperature is classified as « Temperature » when it should be classified as « Circuit Temperature. »
I have placed a room temperature box. And in the room I have 2 sensors, 1 Xiaomi Aqara temperature sensor and 1 Xiaomi Aqara opening sensor.
So the temperature of the opening sensor is wrong, well it does not represent the ambient temperature.
I think that this data is misclassified
In Zigbee2Mqtt it is just indicated as temperature.
By browsing the parameters in Zigbee2Mqtt I found how to set up a filter and not send this value to solve my problem.
That’s what I think too. Which is quite absurd because in the majority of cases the open/close sensor is placed on a door / a window… so the temperature doesn’t reflect the room’s temperature ^^
So we can recalibrate (thanks @AlexTrovato for the info) the temperature of this sensor or stop sending this value to MQTT. That’s actually what I did, so this temperature no longer affects the calculation of the room temperature.
It’s indeed the only proper way to avoid sending the information, since depending on the type of window/door frame the temperature can vary quite a bit — I’ve seen cases of a correction difference of -7 to -3°C within a few hours.
Isn’t it possible to ignore this temperature value for these devices on the Gladys side?
