Tapo Smart Temperature & Humidity Sensors

[Sugar]

Virtual ID of Moes Hub is: bfdd385cadc34fdb76jlx7

Tapo T310 Temperature Sensor:

Virtual ID for T310 (Temperature) is bfb5cf5519cd2571f3h5yc

You can't add those child devices to the main screen or change the name.

It is dp_temperature instead of just Temperature.

Tapo T315 Temperature Sensor:

Virtual ID for T315 (Temperature) is: bf649b287424409932xcbr

It is dp_temperature instead of just Temperature.

You can't add those child devices to the main screen or change the name.

That sensor is wrongly named; it should be Tapo T315 Temperature instead of T310. T310 is a different version of their temperature and humidity sensor (version without a screen).

Tapo 315 Humidity Sensor:

Virtual ID for T315 (Humidity) is: bf735ce333eac34bc64pqz

You can't add those child devices to the main screen or change the name.

That sensor is wrongly named; it should be Tapo T315 Humidity instead of Matter product 2.

Tapo T310 Humidity Sensor:

Virtual ID for T310 (Humidity) is: bffebcbc4ed71e3dc82jw6

You can't add those child devices to the main screen or change the name.

That sensor is wrongly named; it should be Tapo T310 Humidity instead of Matter product 3.

Thank you if possible to fix it

[fangping.guo]

Regarding the issue of the device name displayed after it is added to the doodle, as well as the problem of not being able to display it on the main interface, you can provide feedback through the app.

This section of this forum is used to provide feedback on Matter and Matter-Bridging issues.

For example, if your device displays and functions normally within the Tuya Smart app but cannot be bridged, or if it displays or operates abnormally on other Matter platforms after bridging, you can report the issue here.

[Sugar]

Regarding the issue of the device name displayed after it is added to the doodle, as well as the problem of not being able to display it on the main interface, you can provide feedback through the app.

This section of this forum is used to provide feedback on Matter and Matter-Bridging issues.

For example, if your device displays and functions normally within the Tuya Smart app but cannot be bridged, or if it displays or operates abnormally on other Matter platforms after bridging, you can report the issue here.

So, what I have done currently. Firstly, I bought the Zemismart hub and the Moes hub, then I realised that both hubs are exactly the same, same hardware and firmware. If I checked correctly, the hardware and firmware are made by Tuya.
I contacted support through tuya/smartlife app. They told me because it's matter devices, I have to contact the hubs makers. I sent an email to both hub makers. Zemismart didn't help, just a basic automated answer.
Moes support said to send them videos, plus screenshots and a video with log numbers, and they will contact Tuya. No answer for days.

So basically, who is responsible for the firmware for all these hubs? No one is trying to fix these visual Tuya app bugs for the Matter Controller, plus missing translations for some things. Is there any section somewhere for the matter controller, then?
All these Zemismart, Moes and Avatto Matter hubs are advertised as matter controllers for the Tuya app/platform.

Thank you.