Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blitzwolf bw lt31 secondary entities wrong type #1505

Closed
MackoMici opened this issue Jan 10, 2024 · 0 comments
Closed

Blitzwolf bw lt31 secondary entities wrong type #1505

MackoMici opened this issue Jan 10, 2024 · 0 comments

Comments

@MackoMici
Copy link
Contributor

Describe the bug
WARNING (SyncWorker_6) [custom_components.tuya_local.helpers.device_config] Karácsonyi fények extra sent invalid hex 'Classic 25%' for option

It seems that the wrong type has been entered because the system keeps throwing an error, although it still works.

secondary_entities:

  • entity: select
    name: Music
    icon: "mdi:palette"
    category: config
    dps:
    • id: 102
      type: hex --> string
      name: option
      optional: true

If I change the type value to string, it no longer throws an error and the settings work.

@MackoMici MackoMici added the bug Something isn't working label Jan 10, 2024
@make-all make-all added device improvement Improvement to an existing device config and removed bug Something isn't working labels Jan 10, 2024
make-all added a commit that referenced this issue Jan 10, 2024
Hex is only intended for encoded values. Due to other device requirements
the hex decoding is done after mapping, so using hex type for mapped values
that are mapped to non-hex produces errors. In this case, using the string
without hex decoding is what we want.

Issue #1505
@make-all make-all added awaiting confirmation Wating for confirmation the issue is solved unreleased Will be in next release labels Jan 10, 2024
@make-all make-all removed awaiting confirmation Wating for confirmation the issue is solved unreleased Will be in next release device improvement Improvement to an existing device config labels Jan 28, 2024
timlaing pushed a commit to timlaing/tuya-local that referenced this issue Aug 8, 2024
Hex is only intended for encoded values. Due to other device requirements
the hex decoding is done after mapping, so using hex type for mapped values
that are mapped to non-hex produces errors. In this case, using the string
without hex decoding is what we want.

Issue make-all#1505
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants