Closed maxi1134 closed 4 years ago
I second this issue as well. I am experiencing the same issue.
I have the same problem as well. My tuya smart plugs are all regognized by homeassistant, so that a faulty configuration of the tuya integration on my side can be ruled out.
The bulbs in question: https://www.amazon.de/gp/product/B07H8B6B9H/ref=ppx_yo_dt_b_asin_image_o07_s00?ie=UTF8&psc=1 The bulbs all show up and work fine in the Smart Life app, I also tried the tuya app, changing the tuya part configuration in the yaml accordingly, plugs also did not show up.
I have the exact same problem with these. Other device using tuya (light bulb, outlet, switch,...) works fine but not these.
Can we get some support for this? Still not working.
Yes or is there anything we can do to help you to solve it?
Same problem with the Gosund bulbs for me; Also not showing these bulbs: https://www.amazon.de/gp/product/B07T59FWLD/ref=ppx_yo_dt_b_asin_title_o01_s01?ie=UTF8&psc=1
Brilliant Smart RGBW Bulbs (ALDI Australia) experiencing the same issue.
I've manually added the virtualID to .storage/core.entity_registry
but still cannot control the device
Can anyone shed light on how this integration works? Looking at the library used to connect to tuya: https://github.com/PaulAnnekov/tuyaha/blob/master/tuyaha/tuyaapi.py
It seems like tuya actually expose an endpoint specifically for home assistant to query?
https://px1.tuya(eu|ay|ax).com/homeassistant/skill
How did that happen? I've manually hit this endpoint (using another npm library) and it is not returning details on these bulbs. How can we raise an issue on it?
My current guess (massive assumption) is that these bulbs have a different type
or something on Tuya's side and the integration they provide has not been updated to reflect the changes. So these bulbs are getting filtered out somehow?
edit: In contact with Tuya re: this issue. Will report back.
Also posting this here:
I found a small work around.. You can make scenes that turns a device on and off. These scenes are found in HA and can be used to be intergrated in automations and scripts. The only thing one can´t control is the color of RGBW devices..
Thanks @MatthijsDJ! Nice find.
I would highly encourage everyone who sees this issue to open up a tech help request ticket with Tuya and help raise the priority to getting these devices up and running.
This is what I sent (vary it a bit):
I have some Tuya based RGBW bulbs that are showing up in the TuyaSmart application but do not appear in the Home Assistant discovery API endpoint. The endpoint used to discover and interface with Home Assistant is provided by Tuya and found here: https://px1.tuyacn.com/homeassistant/skill with "discovery" payload.
I have accessed it using this library (also by Tuya): https://pypi.org/project/tuyapy/
Open A Tech Request ticket here https://iot.tuya.com/council/chat/
You will potentially need to create a new Tuya account for this as non china accounts don't seem to work.
From Tuya on support ticket:
Hello, this will be scheduled as soon as possible, I will not close this ticket, the new version of the lighting support HA still takes a while.
There's hope!
Glad I found this here, I have been trying to get 2 bulbs working all day, all the sockets work fine.
Same problem here
Same issue also
Same issue here ... just the bulbs not showing up.
Same issue apparently with LSC smart connect RGBW LED strip and Ceiling lamp.
same issue with these bulbs by Gosund. Damn, I wished to use them as visual indicators. Guess I'll be waiting along with everyone else....
Everyone open tickets with tuya to help raise the priority!
On Sun, Oct 20, 2019, 4:00 PM ryaske notifications@github.com wrote:
same issue with these bulbs by gusound. Damn, I wished to use them as visual indicators. Guess I'll be waiting along with everyone else....
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/25163?email_source=notifications&email_token=AAETIJ7ZHACS3Q4LD26OQS3QPPQWFA5CNFSM4IDYSVBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBYCNPI#issuecomment-544220861, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAETIJ3BUVXU2IHUZFIUJGDQPPQWFANCNFSM4IDYSVBA .
Everyone open tickets with tuya to help raise the priority!
I opened a ticket and will reply back here with their response. I will be returning my 6 bulbs if they cant get this working... I see we've been waiting since July
Seeing the same issue with the Globe bulbs from Costco.
POST to https://px1.tuyaus.com/homeassistant/skill
Body:
{ "header": { "Content-Type": "application/json", "name": "Discovery", "namespace": "discovery", "payloadVersion": 1 }, "payload": { "accessToken": "TODO", } }
Response:
{ "payload": { "devices": [], "scenes": [] }, "header": { "code": "SUCCESS", "payloadVersion": 1 } }
I have the three bulbs working in the TuyaSmart app and integrated with Google Home.
I got a reply to my ticket. It does not appear like they will be adding HA support:
Tuya17 hours ago Hello, your product does not support HA, so it cannot be found on HA.
Last night I tuya-convert flashed one of my Gosund bulbs (WB4) to Tasmota, and was able to get it working in HA just fine after some fiddling. I guess I will just stop using the Smart Life app altogether and get Google Home / Alexa to talk to my HA directly (something I planned to do already).
DOWN WITH THE CLOUD!!!
Woah, ignore my last update ... now a bigger one! I sorta fabricated a story about wanting to buy hundreds of Gosund Bulbs for a project..................... but since they wont be supporting HA i will be returning my test bulbs and going with another vendor's products.
And so they replied with this HAHA
Tuya an hour ago Hello, we expect to support your product on HA this Thursday, and you will be able to use it normally.
So maybe I won't be converting my other bulbs to Tasmota just yet. Lets see if they come through!
Just submitted a ticket for the Costco Globe bulbs, will share any relevant responses.
Response from Tuya regarding the Costco Globe bulbs:
Hello, some of our new lighting does not support HA. What is your device ID? Let's take a look at it first. Some of us can schedule support later.
I sent along the device IDs for each bulb.
Hello, all three products are the same, we will evaluate and support HA in the later stage.
When asking for a more specific timeline, I got this back:
Hello, the specific time is not yet available to you. If you need more assistance, you need to evaluate, schedule, and then support.
Glad I found this it was driving me crazy I to have many Tuya switches and dimmers working with HA but 3 different ones don't Funny how some are from same company Moes. wall switches are found by HA but not the Moes dimmer switches. But work in Tuya app and Google home.
My question I want to buy more devices to complete my setup. How can I know which Tuya devices will work and which won't before purchasing ?
Woah, ignore my last update ... now a bigger one! I sorta fabricated a story about wanting to buy hundreds of Gosund Bulbs for a project..................... but since they wont be supporting HA i will be returning my test bulbs and going with another vendor's products.
And so they replied with this HAHA
Tuya an hour ago Hello, we expect to support your product on HA this Thursday, and you will be able to use it normally.
So maybe I won't be converting my other bulbs to Tasmota just yet. Lets see if they come through!
I bit the bullet and went the Tasmota route. TuyaConvert 2 worked flawlessly for 19 out of 20 bulbs.
They fixed it - I started seeing the Costco Canada Globe bulbs in Home Assistant today. A little laggy when switching them on/off; but, I suspect that is due to the dependence on their cloud API (versus local).
Hallelujah!!! .... I also can confirm that mine are showing up now and are functional in Home Assistant.
My bulbs also startet reporting for duty yesterday. But is it just for me that the function to change the bulbs color is missing? I can only switch on/off and adjust the brightness, while in smartlife the same bulbs can also change the color...
mackflix notifications@github.com schrieb am Fr., 1. Nov. 2019, 23:43:
Hallelujah!!! .... I also can confirm that mine are showing up now and are functional in Home Assistant.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/25163?email_source=notifications&email_token=AF4ENLUT5PL6VEEOWERZYPDQRSWIPA5CNFSM4IDYSVBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC4LAGY#issuecomment-548974619, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4ENLRCIXYVVPMW5RAK3TTQRSWIPANCNFSM4IDYSVBA .
My bulbs also startet reporting for duty yesterday. But is it just for me that the function to change the bulbs color is missing? I can only switch on/off and adjust the brightness, while in smartlife the same bulbs can also change the color...
Sorry, I cannot verify the colour bulb functionality as I only have the Warm White Bulbs with just a Brightness slider in addition to On / Off. I guess it's possible that they aren't quite finished with it but wanted to get "something" out there to quiet the complaints? Pure conjecture at this point, hopefully others in your situation will chime in.
is it just for me that the function to change the bulbs color is missing? I can only switch on/off and adjust the brightness, while in smartlife the same bulbs can also change the color...
I can confirm this is the case for me as well for my Tuya (Gosund) Bulbs. No color settings at all. Home assistant just controls brightness.
This is something I mentioned to the Tuya support case I have open with them, hopefully they can fix that too. If not........ looks like I will be converting to Tasmota anyway....... Will let you all know here if they decline to fix it.
The API now returns the bulbs like this:
{
"payload": {
"devices": [
{
"data": {
"brightness": "710",
"color_mode": "white",
"online": true,
"state": "false",
"color_temp": 18859
},
"name": "Basement 1",
"icon": "https://images.tuyaus.com/smart/icon/1548689576t5lgitdh01_0.png",
"id": "
Guessing the type = "light" would be different for RGB bulbs? I don't have any others to compare. I'm seeing both brightness and temperature options in HA when looking at a single light entity.
RGB color picker would be a nice-to-have; but, given how dark the non-white colors are, I never actually use them.
I would like to figure out a way to toggle the brightness and temperature for a group of bulbs in HA.
I would like to figure out a way to toggle the brightness and temperature for a group of bulbs in HA.
Have you tried setting up a light.group?
I got a very weird situation. Since you guys report the bulb start working. Then I check the unused entities and I saw my tuya bulb shows there. But after I change the entity ID and set a name for it. Then go to UI and trying to add it, I failed. After that I can not see my bulb shows there any more.
And I got this error in terminal
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 275, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 316, in _async_write_ha_state
attr.update(self.state_attributes or {})
File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 477, in state_attributes
data[ATTR_BRIGHTNESS] = self.brightness
File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 43, in brightness
if self.tuya.brightness() is None:
File "/usr/local/lib/python3.7/site-packages/tuyaha/devices/light.py", line 16, in brightness
brightness = int(self.data.get('color').get('brightness') * 255 / 100)
AttributeError: 'NoneType' object has no attribute 'get'
Is there anyone can help? I run my HA under docker.
Yes, I have the same issue with the log errors - I think either the tuya API or tuyaha component still need to be updated to get this working well.
Because I do not have the skills or knowledge to dig into it further I can only be patient and hope it will be fix soon at either end; In the meanwhile i use scenes to get everything working and those are still working fine.
at least it seems we are moving in the right direction - hopefully it is just a question of time untill they sort it out.
edit: make sure the bulbs are turned off when restarting Home assistant after adding the lights - if i restart with the bulbs turned on they show as unavailable but they come back to the UI when I turn them off; in any case, the errors are still present in the log, even when they all show up in the UI.
Hope someone can fix it too. But if tuya API got problem how come those are able to detect their bulbs? I just need HA can turn on/off. Brightness and color is not so important to me.
Woah, ignore my last update ... now a bigger one! I sorta fabricated a story about wanting to buy hundreds of Gosund Bulbs for a project..................... but since they wont be supporting HA i will be returning my test bulbs and going with another vendor's products. And so they replied with this HAHA
Tuya an hour ago Hello, we expect to support your product on HA this Thursday, and you will be able to use it normally.
So maybe I won't be converting my other bulbs to Tasmota just yet. Lets see if they come through!
I bit the bullet and went the Tasmota route. TuyaConvert 2 worked flawlessly for 19 out of 20 bulbs.
Is there a guide you followed to accomplish this? Can you change colors after the flash? I have the same issue as everyone else, my bulbs show up (if they are off during the reboot) but no color change option so thinking about doing the flash
Is there a guide you followed to accomplish this? Can you change colors after the flash? I have the same issue as everyone else, my bulbs show up (if they are off during the reboot) but no color change option so thinking about doing the flash
yes you can control color after converting. At least on my Gosund bulbs it was no problem. I did have to figure out which channels were which PWMs myself but it wasnt so hard, just a few minutes of trial and error.
After that I only went so-far as to confirm there is a nice place in Home Assistant to adjust the color. then I unscrewed my bulb and havent used it yet, was waiting on Tuya to come around but I am getting impatient now so I'm likely to convert my others too. You are just sending numerical color values for each brightness; W R G B so they can be automated via Tasmota/MQTT/HA like anything else.
I did an OTA upgrade so I didnt even need to take the bulb apart.
Here are some guides you can follow
There are newer/updated tutorials out there just give tuya-convert a google
You will need Raspbian Stretch Light and Raspi to follow most of the guides. Its nice because you will need both the ethernet and the Wifi. You will probably want to dedicate a microSD card to it so you can just shutdown your HA, swap the card in, convert, and boot HA back up.
Thanks for those guides! And good idea about swapping the sd card, didn’t think about that :)
In other news, I did find that if you put the tuya light using a light group feature in HA with a light that supports color change and then change the color of the group the tuya light will change the color as well once... then to change color again, you have to change the color temperature of the group and only then you can change the color again
I can confirm that the moes/Tuya dimmer switches now show up in HA. Great :)
Possibly the same issue here where the brightness/colour error comes up with the set of bulbs that only started working few days ago. Initially those 3 globes were not recognised by HA at all.
In my instance, the lights still come on via HA control slider but the sliders goes back to off position after which I can't control lights through HA.
Workaround I found is to set mode to white in the Tuya app, after which lights work as intended in HA but white only mode.
I think i am ready to flash my tuya bulbs using @ryaske's guide, since there have been no update on this. Do you need to do any hardware mods? Looks like it becomes a Sonoff module that I need to first buy and wire into my light? And then I control it using MQTT?
I'd recommend looking into esphome you can flash that after converting to sonos
On Sun, Dec 8, 2019, 9:11 AM skynet01 notifications@github.com wrote:
I think i am ready to flash my tuya bulbs using @ryaske https://github.com/ryaske's guide, since there have been no update on this. Do you need to do any hardware mods? Looks like it becomes a Sonoff module that I need to first buy and wire into my light? And then I control it using MQTT?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/25163?email_source=notifications&email_token=AAETIJ3OLC2E3NLARQ6T2W3QXQNRVA5CNFSM4IDYSVBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGGQTCI#issuecomment-562891145, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAETIJ4SDVYLWI2CO53KGA3QXQNRVANCNFSM4IDYSVBA .
Do you need to do any hardware mods?
If you are talking about a Tuya or related WRGB LED bulbs, no mods at all. Put it in pairing mode and you can use Tuya Convert to put Tasmota or anything else on it.
I got a very weird situation. Since you guys report the bulb start working. Then I check the unused entities and I saw my tuya bulb shows there. But after I change the entity ID and set a name for it. Then go to UI and trying to add it, I failed. After that I can not see my bulb shows there any more.
And I got this error in terminal
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 275, in async_update_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 316, in _async_write_ha_state attr.update(self.state_attributes or {}) File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 477, in state_attributes data[ATTR_BRIGHTNESS] = self.brightness File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 43, in brightness if self.tuya.brightness() is None: File "/usr/local/lib/python3.7/site-packages/tuyaha/devices/light.py", line 16, in brightness brightness = int(self.data.get('color').get('brightness') * 255 / 100) AttributeError: 'NoneType' object has no attribute 'get'
Is there anyone can help? I run my HA under docker.
I'm seeing the same types of issues here. I was able to see the device and could turn it on/off and change brightness however I never got state. Now since I renamed it and restarted HA the lights are gone, not showing anymore.
Same situation here. A few hours ago they worked correctly and now they don't work anymore. Some bulbs are showing up in home assistant but I can only turn them on and off and change the brightness. Other bulbs are not showing up at all. But I can still control them with the Smart Life app. I think they changed something in their cloud.
Samething happening to me. Was working perfectly till I restarted HA today...
I was able to regain partial control of the light by setting the light to white mode on the Smartlife app. After that, HA was able to show it on lovelace, but I can only control its brightness.
If for some reason I put it back in color mode, the same error starts poping up:
2019-12-18 00:00:01 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 286, in async_update_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 327, in _async_write_ha_state
attr.update(self.state_attributes or {})
File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 418, in state_attributes
data[ATTR_BRIGHTNESS] = self.brightness
File "/usr/src/homeassistant/homeassistant/components/tuya/light.py", line 43, in brightness
if self.tuya.brightness() is None:
File "/usr/local/lib/python3.7/site-packages/tuyaha/devices/light.py", line 16, in brightness
brightness = int(self.data.get('color').get('brightness') * 255 / 100)
AttributeError: 'NoneType' object has no attribute 'get'
I'm having the same problem and error as calexandre above using merkury innovations color bulbs setup with the tuya app instead of the merkury app also in developer tools states its showing supported_features: 1
This error started after upgrading to HA ver 103
@G33kDude posted a fix in a duplicate thread of this issue. It works for me, but you will have to edit your light.py file https://github.com/home-assistant/home-assistant/issues/28602#issuecomment-5673129766
Fixed by #30213
Operating environment (Hass.io/Docker/Windows/etc.): Hass.io running on a docker on Ubuntu
Component/platform: https://www.home-assistant.io/components/tuya/
Description of problem: I've just purchased 3 tuya bulbs that do not show up with the tuya component. All of my other tuyas things work properly.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Additional information: The bulbs in question: https://www.costco.ca/Globe-Electric-LED-A19-RGB-Smart-Wi-Fi-Bulb.product.100483522.html