Tuya Intgegration Showing Devices as "Unsupported"

[almighty059]

The problem

I have almost 30 devices connected to the Tuya Integration and approximately 20 out of the 30 are showing as being "unsupported" by the Tuya Integration. The devices work fine when operating over the Tuya Cloud or LocalTuya. The problem only seems to exist within the Tuya Integration. I tried deleting and reinstalling it but when the integration loaded and asked me to assign rooms to the devices I could see that they were still showing as being "unsupported".

What version of Home Assistant Core has the issue?

core-2022.5.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tuya

Diagnostics information

config_entry-tuya-08b0dc7dae9cfd25ba02ef056042b411.json.txt

Example YAML snippet

N/A

Anything in the logs that might be useful for us?

N/A

Additional information

N/A

[probot-home-assistant]

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

[probot-home-assistant]

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)}}

[almighty059]

After looking into this issue I found the following error. Only devices with the light domain have been affected and show as being unsupported.

2022-05-15 07:37:54 ERROR (MainThread) [homeassistant.components.light] Error while setting up tuya platform for light Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform await asyncio.shield(task) File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 382, in async_setup_entry async_discover_device([*hass_data.device_manager.device_map]) File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 375, in async_discover_device TuyaLightEntity( File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 450, in __init__ h_type=IntegerTypeData(dpcode, **function_data["h"]), KeyError: 'h'

[almighty059]

@tuya, @zlinoliver, or @frenck have any of you had a chance to look at this issue? Thanks.

[almighty059]

Do these bug reports even do anything.?

[frenck]

Sure they do, but they won't resolve themselves. This is an open-source project which relies on contributions. Feel free to contribute a fix for this issue (or any other issue) in this project if you are up to it.

../Frenck

[almighty059]

@frenck I would love to contribute a fix for this issue because then there would be no issue and I wouldn't be going crazy... 🤪
I also contribute when I am able to and would love to be able to contribute more but unfortunately, I don't have the knowledge and experience that you and others have so my contributions are limited. And forgive my sarcasm, it was just my frustration because I have tried almost everything myself and have yet to find a solution.

• searched all of the forums and found some related but nothing that has helped me.
  #684 (open issue)
  #60135 (you closed this one out with Fix Tuya data type information in lights #62993 (comment))
• switched from the Tuya App to the Smart Life App and back.
• deleted and reinstalled HA Tuya integration.
• created a new Tuya IoT cloud project.
• currently have an open Tuya ticket but so far they have not found a solution.
• flashed my HA Blue and started over from scratch with a fresh installation of HA.

Issue: All Tuya light devices suddenly show as being "unsupported" and their entities go dead after rebooting HA. The devices can still be controlled via the Tuya IoT platform, Tuya or Smart Life App, and LocalTuya if installed. Devices not using the light domain and lights from other integrations such as Govee are not affected and are functioning with no issues.

Temporarily Works: Transferring devices from the Tuya App to the Smart Life App temporarily fixes the issue. The process I use is I disconnect the Tuya integration and Tuya App from the Tuya IoT cloud project and delete Tuya integration from HA. I then connect the Smart Life App to a new cloud project and install the Tuya integration in HA and connect them. I then delete devices one by one from the Tuya App and install them in the Smart Life App. After several devices are connected I reboot HA and check the device and entity status. If everything looks okay I continue to transfer the devices. At first, everything usually works but for some reason when I have about 10-15 lights added and I reboot HA the issue will occur. Device are suddenly unsupported and their entities go dead.

I'm completely lost because the problem does not immediately happen which makes me think that it's either the number of devices or one specific device that triggers the problem. I've tried to narrow it down but I can't find any correlation yet between a specific device or the number of devices and the issue. I only know that it always seems to happen after I have installed at least 10 devices.

Below is the error log from Home Assistant and I have attached diagnostics from two devices that use the light domain and also the diagnostic from the Tuya integration. Everything is new and was pulled from HA after the fresh installation that I just did.

Logger: homeassistant.components.light
Source: components/tuya/light.py:450
Integration: Light ([documentation](https://www.home-assistant.io/integrations/light), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+light%22))
First occurred: September 12, 2022 at 4:14:56 PM (1 occurrences)
Last logged: September 12, 2022 at 4:14:56 PM

Error while setting up tuya platform for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 382, in async_setup_entry
    async_discover_device([*hass_data.device_manager.device_map])
  File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 375, in async_discover_device
    TuyaLightEntity(
  File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 450, in __init__
    h_type=IntegerTypeData(dpcode, **function_data["h"]),
KeyError: 'h'

config_entry-tuya-545e4cae768b8ecd417406f7473e9bb3.json.txt
tuya-545e4cae768b8ecd417406f7473e9bb3-LED Strip 001 (Kitchen)-0d2e2a86165287632739472b3f14d0c1.json.txt
tuya-545e4cae768b8ecd417406f7473e9bb3-Kitchen Ceiling Light 01-4f3b0caf61e05643b70a29e6998162fd.json.txt

[almighty059]

@frenck hopefully you get a chance to look at this because I think I at least found the issue, If I did then maybe you can help me find a fix for it.

Without going through all the steps that it took me to find this out I will get right to the issue. I had two Tuya devices that were causing the issue and when I removed them the issue went away. Both of the devices are switches. One is a socket switch that gets plugged into a wall outlet and the other is a hardwired switch that gets put inside of an electrical box. The product types for these switches are "cz" and "qjdcz". I'm assuming that the "cz" in both of them means that they are somehow similar which would explain why both of them are causing the issue,

Just to reinforce my findings, in the open issue tuya/tuya-home-assistant#684 (comment) the user describes the same problem and in the description, it says that the user's "power cords" are still working correctly.

I think the problem is that the Tuya power switches are somehow breaking the Tuya integration when it comes to any device that uses the light domain. I don't know how soon you will respond and I have never tried to do this but I'm gonna try to make a pull request of the light.py and try to remove or edit those product types. You encouraged this so keep your fingers crossed... lol...

[guiramos]

I am having the same issue. All entities are "Unsupported".
I have everything working fine with Smart Life and Google Home.

[almighty059]

@guiramos can you troubleshoot it to see if it's just "light" entities or are all your entities showing as "unsupported" covers, switches, lights, etc..?

Also, were they previously working or did something change that led up to them showing as "unsupported".?

[guiramos]

No, they were always unsupported. I just installed the tuya integration.

[almighty059]

What kind of devices and how many.? Have you checked the error log to see if the Tuya Integration is logging an error.?

[bone6000]

Hello

Same problem here. In my case I have 4 tuya switches (Product Category= cz) and since a few months ago the devices are detected by Homeassistant but no entities, so I can't manage them.
In Tuya IOT platform and also the Android App are working fine....

I think there is an issue with the switches somewhere...

With localtuya works but in my case I have 2 different locations in my homeassistant so can only manage the LAN devices but not remote ones.

Thanks.

[almighty059]

@bone6000 yes it seems to be something with the (Product Category= cz) switches being seen as "lights". I think the error was caused when Tuya was trying to associate them with the "light" domain.

Do you only have those four switches or do you also have lights?

Are the switches the exact same brand and model?

If you have more Tuya devices than just those switches or if the switches are different than try removing all four switches and restarting HA and then see if everything starts working. If it does then add one switch at a time to see which switch is causing the issue. If all four switches are the same then you obviously only have to try adding one and you'll know.

If you're only using those four switches with the Tuya integration then you're kind of screwed until the issue gets fixed. It's not getting a lot of attention because I don't think a lot of people of experiencing it. It seems to only be certain switches causing it. I converted all my Tuya devices to Tuya Local and everything works fine like that. I think it also works better so that's always an option if you want to get them working.

[bone6000]

I only have those 4 switches, tried configuring one by one but the problem persists even with only one unit. I think that switches are the root cause of the issue so I have to wait to somebody to fix the code...

With localtuya works but can only configure the switches in the house that homeassistant is local, the other house can't be configured because the switches are not in the same LAN network...

[almighty059]

@tuya, @zlinoliver, @frenck, I don't mean to bother any of you but if you have the time could you please help us out and look over this issue? I've already opened a ticket with Tuya but I haven't much progress with them. I kind of already know what's causing it I just don't know how to fix it. Thanks.

[bone6000]

@almighty059, how did you retrieve the debug logs with that error messages? I tried to download "diagnostics" from the tuya integration but there is not as much information as you have... do you have to enable some verbose debug in configuration.yaml?

[almighty059]

@bone6000 I would think that there is more information when downloading the diagnostics from the Tuya integration than from what I posted unless we're both refering to something different.

The way to get the diagnostics for the entire Tuya integration is to go to Settings -> Devices & Services -> Integrations then click the three dots on the Tuya integration like you see in the screenshot below and Download diagnostics.

The way to get the diagnostics for an individual Tuya device is to do the same thing but instead of clicking on the three dots you click on Devices and then click on the device you need the the diagnostics for and the under Device Info click on Download Diagnostics like you see in the screenshot below.

If neither of those are what you're talking about then the only other thing that I posted and that you could have meant was the actual errors that HA displays in it's Log section. That I got by going to Settings -> System -> Logs. Depending on how much data is logged you could either look for or you the search at the top to find an Error associated with the Tuya integration. When you find it you could click on it to see more information. You should find a Tuya error there and if your error is happening because of the same reason that mine is then the error log should look similar to mine below.

Logger: homeassistant.components.light
Source: components/tuya/light.py:450
Integration: Light ([documentation](https://www.home-assistant.io/integrations/light), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+light%22))
First occurred: September 12, 2022 at 4:14:56 PM (1 occurrences)
Last logged: September 12, 2022 at 4:14:56 PM

Error while setting up tuya platform for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 382, in async_setup_entry
    async_discover_device([*hass_data.device_manager.device_map])
  File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 375, in async_discover_device
    TuyaLightEntity(
  File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 450, in __init__
    h_type=IntegerTypeData(dpcode, **function_data["h"]),
KeyError: 'h'

Also, FYI the switches that caused me a problem were a plugin wall switch that is meant for a cord to plug into and a wall switch that is used to toggle a light on/off. I have a Tuya switch that gets hardwired in between a normal wall switch and a light/fan and that one does not cause any issues.

I was going to suggest that you connect all four switches to the Tuya App and then just add the two local switches to Tuya Local but then I started thinking about it. How do you have the switches connected in the Tuya App.? Since they use different networks at different locations did you make separate "homes" for them in the app?

[bone6000]

my switches are plugin wall switches that are meant for a cord to plug into. all of them same model.
i have no separation at all in tuya app for different homes, but tried only to add 1 local switch and removing all others and not working...

[almighty059]

If they look similar to the one in the picture below then they're just like mine and all of them will cause the Tuya integration to break. When you first connected the outlets to the Tuya app did they all work fine? I'm curious how you were able to connect them at different locations on different networks. The only way I know how to do that is by creating separate "homes" within the app because then you could entire a different network name for the other location.

To add a "home" you need to open the Home Management settings and "Create a home". You can find the Home Management settings by either clicking the name of your "home" on the top left of the screen or by clicking on your profile button on the bottom right of the screen. Both ways should bring up an option to choose Home Management and then "Create a home".

Then you should have control over all of the devices by using the Tuya App. You could then add the two devices that you want local HA control of by using Local Tuya. Then you don't need to use the official Tuya integration for anything so the "unsupported" issue shouldn't matter. Right.?

[bone6000]

In tuya application for Android I only have one home configured, but I have 4 switches there, 2 in one house and 2 in another one and I can manage all of them from the application.

From HA, in can only manage the local switches (2 of them) with local tuya integration, but actually i can "discover" the 4 devices with tuya integration but no entities for any of them (the integration says unsupported). My switches are different from the image because that ones are for UK i think, and mine are for Spain, so it's a different plug (and model). My model have the power button made of transparent rubber material and you can see the red light when it's on

[spathix]

I've purchased a smart plug here in Australia, an 'Arlec Grid Connect Smart Adaptor with Temp and Humidity sensor' (PCTH01HA) and I am also getting the same error via the Tuya Integration. The adaptor works fine via the Tuya Smart app, however via the tuya integration I see:

My diagnostic output -

config_entry-tuya-9ee88ab1c2f8ea390a772cf1246a1b17.json.txt

I couldn't see anything in the Settings -> System -> Logs

Picture of plug fwiw -

https://grid-connect.com.au/wp-content/uploads/2022/02/PCTH01HA.png

I may try local tuya and see how that goes.

[guiramos]

Wait, wait, wait. Sorry to change the subject for a moment, but this topic is also pertinent.

Couple days ago my Home Assistant integration stopped working, after recently installed. I went to check it and it seems the first one month expired. Now, there was an option to extend the period but after that we would have to pay for it.

Is that accurate? How to navigate this situation? I really don't want to pay for this.

[almighty059]

@guiramos you do not have to pay for it but you do need to extend it...

Here is the link for the same information as in the screenshot below.
Link -> Request to extend your Tuya API service.

[guiramos]

Thank you very much sir @almighty059

[bone6000]

do you think anybody is trying to see this issue? I'm upgrading HA everytime I see upgrades but the problem persist...

[almighty059]

do you think anybody is trying to see this issue? I'm upgrading HA everytime I see upgrades but the problem persist...

@bone6000 I know they get overwhelmed with all the different issues that they have to respond to and sone take priority over the others. From what I understand, @tuya is one of those integrations that does not provide the same level of help as other companies with integrations. I think this issue is fixable and it might just a matter of removing the switches product type from the code but I don't know how to do that. I don't know where the Tuya integration .js file is even stored. If this was an integration from HACS I could attempt to mess with it a little but not an actual HA integration. I'm hoping that maybe @zlinoliver or @frenck get some time to help us out and take a look at it.

[MickPBduece]

Some additional information - When the recommendation for addressing intermittent failure of the the Tuya integration failing to connect when adding devices if follow (error 2406: Invalid Skill Id) is followed to unlink devices from Tuya and re-link them the ability to add unsupported devices is eliminated. Previous to the unlink - relink devices could be added but it required mapping the entity to the device manually which was relatively easy. Maybe these are the devices that are failing

IF there is a way to contiue to manually map the device to entities please tell me. If not I'd suggest that having many hands to find the mappings and a place to share them would allow the Tuya app to work with closed walls for new devices else it seems like it is open enough for the many hand that are not developer to help and it would be better to allow devices to be added with mapping throug the gui

"Tuya Integration - reccomends going into the Tuya cloud and unlinking all devices from the Tuya

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[almighty059]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows another "closed" issue with no solution...

[shackra]

I'm experiencing this in Home Assistant 2023.3.5

[WWillig]

Hi, Newbie here...
I had my Tuya intergration working then the monthly API service expired. I was able to renew for 6 months and HA is able to control my FEIT light bulbs manually from the dashboard but automations dont appear to work and on my dashboard one light says "Entity not available: light.kitchen_table", I can manually turn on this light by going to Settings> Devices> selecting device> and "manually" turning it on and off.
When I maually go to "Run" in automations the lights work, when I move by the motion sensor no joy.

When I go to the Settings>Intergtations>Devices> the Device Info tab on all says "White or Color Light (unsupported). Do I have to re-register them on the Tuya IoT site?
Logbook says the lights are triggered on and off.

No other changes to the system.

Thanks in advance for suggestions.
Running HA Core 2023.3.1 OS 9.5
Bill

[BlueWater86]

This isn't the place for suggestions, feelings or piles of level 1 physical troubleshooting. The world needs to adopt a prerequesite before allowing lodging of issues against open source repositories or all open source repositories will fail. @frenck after trudging through so many open HA issues over the last 6 hours, I feel your pain and thank you for your service to the community.

[WWillig]

If the site is not a place for help, suggestions or troubleshooting what is the purpose? I was under the impression that this is the place to come to share experiences and learn from those who might be able to help.

[BlueWater86]

The "enthusiast" style circular discussions above are best left for an enthusiasts forum. The above discussion does nothing to get a code limitation/bug resolved.

To resolve code issues (github is all about code) discussions should centre on code.

[bone6000]

SmartPlugs still being showed as "unsupported" in latest version of HA... Can anybody check the debugs and try to find the issue?

config_entry-tuya-b1e3633cc6258900e511a08cc788207d.json.txt

[prbreezy]

I'm having the same issue as well under "2023.6.1".
I've followed all the steps in here. https://www.home-assistant.io/integrations/tuya
Thanks!

[bone6000]

@prbreezy, this problem is at least one year long, so don't expect to be fixed in short-mid term.

[Kawobei]

Mine did this only recently because of expired Tuya IoT Core, after i extended it they still said unavailable. I then went in and enabled them again and they are working even though they say unsupported

So they where disabled in this screen.

[Avalonnw]

I have come across this thread when I noticed my devices became "unsopported" but keep working. On the other hand, I am struggling to add a second Inkbird 308 wifi thermostat (the first one works fine) - this second one appears in HA (but with wrong ID for some reason) and does not offer any data. I tried making another project in Tuya cloud, no difference. Tuya local can see devices but also can't control them for some reason.

[prbreezy]

Ive personally unfortunately gave up and moved to other devices with matter support…

On Tue, 25 Jul 2023 at 8:27 AM, Anton ***@***.***> wrote: I have come across this thread when I noticed my devices became "unsopported" but keep working. On the other hand, I am struggling to add a second Inkbird 308 wifi thermostat (the first one works fine) - this second one appears in HA (but with wrong ID for some reason) and does not offer any data. I tried making another project in Tuya cloud, no difference. Tuya local can see devices but also can't control them for some reason. — Reply to this email directly, view it on GitHub <#71486 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMVDXIY3CQQ23ZCZMEABR3XR4HGBANCNFSM5VKS43IQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Pierre-Richard, **Précival*

[bucklevision]

I'm finding this odd. All my devices worked 4 weeks ago on a none-HAOS installation (supervised).
I had a hardware failure and moved to a HAOS installation on another machine, to remove all the usual unsupported OS warnings, and now all my TUYA devices show as unsupported. Baffled.

[StilgarBF]

I may have found a solution. - At least it solved the problem for me.
TLDR: Unlink temperature sensors you may have and reload your tuya "hub" in the integration

Detail:
I had the tuya integration running for some weeks in homeasistant and mainly used it to track power consumption from smart plugs and power meters.
Then I ran into the trial timeout of tuya platform without knowing, while at the same time adding more devices like an outdoor-plug and wireless temperature sensors.

While the switch action for my powerplugs worked in HA with tuya, none of my sensors worked. they had just gone. (that is power, current, voltage, temperature, humidity...)
this shows especially with a low number of entities for my devices in the tuya integration-overview.

I tried removing and re-configuring the integration.
Tried also removing and re-doing the cloud-dev project in tuya IoT Platform.
Then I thought about those last devices I added (temperature sensors and "Energy Meter Clamp...") and unlinked them in the platform devices list. - > changed nothing.

last and finally WORKING: I deleted the temperature sensors from the tuya android app and clicked "reload" in the HA tuya integration. -> BINGO the "unsupported" was gone and the integration showed many more entities (65 entities for 19 devices).

Those also deliver data.

so once again:

in tuya app:

• select suspicious devices
• click edit /pencil in top right
• in very end of the view pick the red delete option
• delete with or without data (seems to make no difference)

in homeassistant

• go to settings >devices & services
• click into tuya
• 3 dots ⋮ -> "reload"

should be fine now.

disclaimer:
this worked for me. I have yet to test adding a temperature sensor again to screw it up and prove its those.

I believe its a problem of the tuya integration and not the API, because the data for power with seemingly valid values was in the json when I checked it. so I assume something that comes with the temperature sensors makes the parser bug out. (unproven assumption)

edit: adding the clamp power meter again brings the problem back. - which is strange, because that power meter worked once. I still have a custom sensor with it configured which has old valid data.

[bucklevision]

Interesting, but I don't have any temp sensors so it's something more general.

[joachimwussow]

Hi,

this device, that meters the water level of a tank, comes up as unsupported. What can I - novice - do?

Thanks!
Joachim

{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2023.12.1",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.11.6",
"docker": true,
"arch": "aarch64",
"timezone": "Africa/Johannesburg",
"os_name": "Linux",
"os_version": "6.1.63-haos",
"supervisor": "2023.11.6",
"host_os": "Home Assistant OS 11.2",
"docker_version": "24.0.7",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"solarman": {
"version": "1.0.0",
"requirements": [
"pyyaml",
"pysolarmanv5"
]
},
"hacs": {
"version": "1.33.0",
"requirements": [
"aiogithubapi>=22.10.1"
]
}
},
"integration_manifest": {
"domain": "tuya",
"name": "Tuya",
"codeowners": [
"@tuya",
"@zlinoliver",
"@frenck"
],
"config_flow": true,
"dependencies": [
"ffmpeg"
],
"dhcp": [
{
"macaddress": "105A17*"
},
{
"macaddress": "10D561*"
},
{
"macaddress": "1869D8*"
},
{
"macaddress": "381F8D*"
},
{
"macaddress": "508A06*"
},
{
"macaddress": "68572D*"
},
{
"macaddress": "708976*"
},
{
"macaddress": "7CF666*"
},
{
"macaddress": "84E342*"
},
{
"macaddress": "D4A651*"
},
{
"macaddress": "D81F12*"
}
],
"documentation": "https://www.home-assistant.io/integrations/tuya",
"integration_type": "hub",
"iot_class": "cloud_push",
"loggers": [
"tuya_iot"
],
"requirements": [
"tuya-iot-py-sdk==0.6.6"
],
"is_built_in": true
},
"data": {
"endpoint": "https://openapi.tuyaeu.com",
"auth_type": 0,
"country_code": "27",
"app_type": "smartlife",
"mqtt_connected": true,
"disabled_by": null,
"disabled_polling": false,
"name": "Tank A Level",
"model": "EPT_Ultrasonic level sensor",
"category": "ywcgq",
"product_id": "wtzwyhkev3b4ubns",
"product_name": "Tank A Level",
"online": true,
"sub": false,
"time_zone": "+02:00",
"active_time": "2023-12-11T07:20:04+00:00",
"create_time": "2023-12-11T07:20:04+00:00",
"update_time": "2023-12-13T10:35:49+00:00",
"function": {
"max_set": {
"type": "Integer",
"value": {
"unit": "%",
"min": 0,
"max": 100,
"scale": 0,
"step": 1
}
},
"mini_set": {
"type": "Integer",
"value": {
"unit": "%",
"min": 0,
"max": 100,
"scale": 0,
"step": 1
}
},
"installation_height": {
"type": "Integer",
"value": {
"unit": "m",
"min": 200,
"max": 2500,
"scale": 3,
"step": 1
}
},
"liquid_depth_max": {
"type": "Integer",
"value": {
"unit": "m",
"min": 100,
"max": 2400,
"scale": 3,
"step": 1
}
}
},
"status_range": {
"liquid_state": {
"type": "Enum",
"value": {
"range": [
"normal",
"lower_alarm",
"upper_alarm"
]
}
},
"liquid_depth": {
"type": "Integer",
"value": {
"unit": "m",
"min": 0,
"max": 10000,
"scale": 2,
"step": 1
}
},
"max_set": {
"type": "Integer",
"value": {
"unit": "%",
"min": 0,
"max": 100,
"scale": 0,
"step": 1
}
},
"mini_set": {
"type": "Integer",
"value": {
"unit": "%",
"min": 0,
"max": 100,
"scale": 0,
"step": 1
}
},
"installation_height": {
"type": "Integer",
"value": {
"unit": "m",
"min": 200,
"max": 2500,
"scale": 3,
"step": 1
}
},
"liquid_depth_max": {
"type": "Integer",
"value": {
"unit": "m",
"min": 100,
"max": 2400,
"scale": 3,
"step": 1
}
},
"liquid_level_percent": {
"type": "Integer",
"value": {
"unit": "%",
"min": 0,
"max": 100,
"scale": 0,
"step": 1
}
}
},
"status": {
"liquid_state": "normal",
"liquid_depth": 178,
"max_set": 100,
"mini_set": 20,
"installation_height": 2001,
"liquid_depth_max": 145,
"liquid_level_percent": 99
},
"home_assistant": {
"name": "Tank A Level",
"name_by_user": null,
"disabled": false,
"disabled_by": null,
"entities": []
}
}
}

[elpeho]

Hi,
Same issue with a Tuya Smart Led Bulb (Bluetooth) connected to a Tuya (Zigbee+BT+wifi) Smart Gateway. Works fine with IOS Tuya app, but it has an "unsupported" flag in HA. So no control available. Same issue with the Gateway (unsupported).
I really don't understand why...
regards

[antwal]

Hi, I have the same problem; I have 63 devices connected on Tuya and Smart Life, they all work perfectly with the mobile app and in the developer console but on Home Assistant only 3 are supported, one of which has wrong values, but it is a known bug with the thermostat; I don't understand why they aren't supported; I also tried with tinytuya and even if the devices have port 6668 open they don't communicate correctly; they don't work with local-tuya or tuya-local either

[lasmaty07]

Same Issue with VersionCore 2024.3.0. Any update on this issue?

Edit:
I managed to get the functions in the diagnostics following this guide

This was my diagnostics before
tuya-6cd2c3e8e804a6f8b313f37c87a2808e-Smart IR-a6b602a6ea2fb37090b82abfc76a145f.json

and now looks like this
tuya-6cd2c3e8e804a6f8b313f37c87a2808e-Audio-49fbf13fd467fbb22a55d4989aa89dc6.json

But I'm not sure what that means. Devices still show "This device has no entities"

[antwal]

I haven't found a solution, at the moment I have given up on using home assistant to manage Tuya devices and continue to use the smart life app

[joluinfante]

Hello. I have smartlife/tuya and sonoff devices. And, of course, I cannot use the app of either of the two so that a "Smart Zigbee M1 Switch (tuya specific)" device is used to turn on the sonoff fan light. Obviously, this would be a last possibility, but the original idea is to use home assistant to integrate both. And I run into this "compatibility" problem. How can it be solved? I can cooperate (I have years of programming in various low-level architectures), but I do not have the expertise to handle the homeassistant code. What can be done? Because my idea, in the long term, is to have all the IoT managed locally (for a country like Argentina, it is difficult to think that turning on a light means touching a button here, that I travel to China or Europe, and from there, they "turn on the light" light").