Tuya (Brilliant Led Spotlight) shows as unsupported in Tuya Integration

c775361 commented 10 months ago

The problem

When adding the Tuya managed light branded as "Brilliant Frontier LED WiFi Twin Security Light", the device is seen when adding the integration but is shown as 'unknown'

What version of Home Assistant Core has the issue?

core-2023.8.4

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 10 months ago

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!

Code owner commands

Code owners of `tuya` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tuya` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

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

c775361 commented 9 months ago

Hi there. I have looked at the Tuya IoT device debugging page. It appears that unlike my other Tuya managed devices, there are no standard controls configured. I assume the issue may be here.

jfp949 commented 9 months ago

Hi there. I have looked at the Tuya IoT device debugging page. It appears that unlike my other Tuya managed devices, there are no standard controls configured. I assume the issue may be here.

Same problem for me

issue-triage-workflows[bot] commented 6 months ago

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.

c775361 commented 6 months ago

Now running 2023.12.3. issue is unchanged. A still showing as unsupported with no device entities

DanielNagy commented 4 months ago

I've got the same issue, bought one of these lights from Bunnings, and it is showing as unsupported.

    "product_name": "Brilliant Smart Sensor Light",
    "online": true,

c775361 commented 4 months ago

As a messy work around I created a switch and use the google sdk to turn it off and on (Tuya integration with google assistant) from HA. Then with a helper expose it as a light I can then use in automations, lovelace, etc. It also appears that I may be able to use the unofficial google sdk version to set an automation to poll google to sync status back into HA for times when I operate it outside of HA

jfp949 commented 4 months ago

I've got the same issue, bought one of these lights from Bunnings, and it is showing as unsupported.
    "product_name": "Brilliant Smart Sensor Light",
    "online": true,

Same - now using LocalTuya for this device and working fine. Just a bit more work to set it up.

DanielNagy commented 4 months ago

Same - now using LocalTuya for this device and working fine. Just a bit more work to set it up.

Can you provide details on how i set this up with localtuya? I've got no other tuya devices, other than this, so i'm not bound by this tuya cloud version.

jfp949 commented 4 months ago

Install LocalTuya via HACS. https://github.com/rospogrigio/localtuya: Motion is 108 Light is 101 Timer is 103 Mode is 104 Lux is 102 Sensitivity is 106 On/off is 107

DanielNagy commented 4 months ago

Thanks! Will give it a go.

issue-triage-workflows[bot] commented 1 month ago

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.

home-assistant / core