Fix Tuya unsupported cameras

[maghiel]

Proposed change

Fixes #132844 by adding the "dghsxj" category to cameras. Some, mostly LSC Smart Connect, devices suddenly moved from sp to dghsxj, rendering them as "unsupported". (As discovered by @Neirop)

Most Tuya cameras are in the device category "sp". About two months ago Tuya suddenly changed the category on some camera's, mostly of the LSC Smart Connect brand sold by Action stores in Europe, to "dghsxj".

It turns out "dghsxj" is a new, but still undocumented, category for "lower power consumption" cameras that Tuya moved some cameras too without any announcement whatsover. (Discoverd by @MPParsley)

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes TUYA: Tuya integration droped camera support for TY-CG6E-300W（T31+SC3336+AIW4211L by Tuya after 2412.1 (missed 0) #132844
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hi @maghiel

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[home-assistant]

Hey there @tuya, @zlinoliver, mind taking a look at this pull request 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 pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign tuya Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

Stale

[maghiel]

Sorry guys, my first pull request here. Accidently clicked Ready for review. Following the checklist as we speak!

[maghiel]

@abmantis did I make a mistake by merging updates from dev again, seeing all the checks have to pass again?
Sorry for the inconvenience, I'm learning ;)

[abmantis]

@maghiel Its ok to merge from dev from time to time or when there are conflicts to resolve.
Since this is your first contribution here, the CI does not run automatically so someone needs to trigger it. But that is fine :)

[maghiel]

@maghiel Its ok to merge from dev from time to time or when there are conflicts to resolve. Since this is your first contribution here, the CI does not run automatically so someone needs to trigger it. But that is fine :)

Awesome, thanks for the explanation and help! And thanks for triggering it again ;)
My thoughtpath was something like: I should keep my pr as up-to-date as possible, but I might have been overdoing that.

[stevesinchak]

Looks good, ty

[maghiel]

@abmantis could you? ..... :)

[frenck]

Hey there, @maghiel, let's make a fully up PR to remove all this duplication.

/CC @abmantis