Tuya - overrule Tuya device category about core HOT 8 CLOSED

Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

tuya documentation
tuya source
_{^{(message by IssueLinks)}}

from core.

I also have this problem with my device. It should be a mmwave presence sensor but it is coded as a switch. I fixed the configuration manually in another addon but it would be nice to have it run natively.

localtuya-6a93607c50a3e9fcffe6f15792b17283-Basement High-precision breath sensor 24G-879246042808a98462ceb71bc864507d.json

from core.

Would love to have that option, but Local Tuya doesn't support Alarm yet...

from core.

This is also an issue for me, I have a multisensor (pid yrr3eiyiacm31ski) for air quality and it currently registers in Tuya cloud as co2bj which in HomeAssistant only exposes CO2.

However, after looking at the definitions in the official tuya integration, I believe this category: dgnbj would be a better fit, as it exposes all of the same sensors that this 8-in-1 device does

I would like to be able to override this, as I can see in the debug json that all of the values are being transmitted & available

from core.

How can the category be overruled so that it can be used?

It cannot. qt is used by Tuya for legacy devices. As far as I am aware, Tuya will never make them available via their cloud services.

This also shows in your provided diagnostic, as that contains the raw data we get from Tuya:

    "function": {},
    "status_range": {},
    "status": {},

I'm going to close this issue on this end, as there is nothing we can do. Please, reach out to Tuya for this case.

../Frenck

from core.

I also have this problem with my device. It should be a mmwave presence sensor but it is coded as a switch. I fixed the configuration manually in another addon but it would be nice to have it run natively.

What about my situation. My code is not qt. It shows up as a switch instead of a mmWave sensor. I've uploaded the file above.

from core.

What about my situation.

Sorry, I'm having troubles understanding how that is related to this issue? If you have a different issue, why is stacked in this issue?

../Frenck

from core.

Sorry, I'm having troubles understanding how that is related to this issue?

I thought it was related because the problem was that the codes are wrong. But now that I read it again, his code is actually correct and obsolete. In my case my code is wrong and not obsolete. I'll make another issue then.

from core.