Inkbird IBBQ-4T not being paired/recognized correctly

[rammstone83]

The problem

Hi guys, i try to pair my Inkbird IBBQ-4T with the Tuya integration but it is only shown as a heater:

in the old local tuya intergration it was possible to use this Device with following yaml code:

https://github.com/make-all/tuya-local/blob/e3cfb5dfe2479e17bca25d5f3b97c96819d7288d/custom_components/tuya_local/devices/inkbird_bbq4t_thermometer.yaml

Is it possible to add the Device with help of this yaml file ?

thanks in advance for your help

What version of Home Assistant Core has the issue?

2024.4.3

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

tuya-cda00996889d2f4be2f68c7aa40f0e64-IBBQ-4T-f80e8038e9366f9db9b591de7f720bd9.json

Example YAML snippet

name: BBQ thermometer
products:
  - id: x6oarivkdgru1upf
    name: Inkbird iBBQ-4T
primary_entity:
  entity: sensor
  name: Temperature probe 1
  class: temperature
  dps:
    - id: 107
      type: integer
      name: sensor
      class: measurement
      mapping:
        - scale: 100
      unit: F
    - id: 13
      type: bitfield
      name: fault_code
      optional: true
    - id: 111
      type: integer
      name: unknown_111
secondary_entities:
  - entity: sensor
    name: Temperature probe 2
    class: temperature
    dps:
      - id: 108
        type: integer
        name: sensor
        class: measurement
        optional: true
        mapping:
          - scale: 100
        unit: F
  - entity: sensor
    name: Temperature probe 3
    class: temperature
    dps:
      - id: 109
        type: integer
        name: sensor
        class: measurement
        optional: true
        mapping:
          - scale: 100
        unit: F
  - entity: sensor
    name: Temperature probe 4
    class: temperature
    dps:
      - id: 110
        type: integer
        name: sensor
        class: measurement
        optional: true
        mapping:
          - scale: 100
        unit: F
  - entity: binary_sensor
    class: power
    category: diagnostic
    dps:
      - id: 1
        type: boolean
        name: sensor
  - entity: binary_sensor
    class: problem
    category: diagnostic
    dps:
      - id: 13
        type: bitfield
        name: sensor
        optional: true
        mapping:
          - dps_val: 0
            value: false
          - dps_val: null
            value: false
          - value: true
  - entity: select
    translation_key: temperature_unit
    category: config
    dps:
      - id: 19
        type: string
        name: option
        mapping:
          - dps_val: f
            value: fahrenheit
          - dps_val: c
            value: celsius
  - entity: sensor
    class: battery
    category: diagnostic
    dps:
      - id: 101
        type: integer
        name: sensor
        unit: "%"
  - entity: number
    name: Screen timeout
    category: config
    icon: "mdi:camera-timer"
    dps:
      - id: 102
        type: integer
        name: value
        unit: s
        range:
          min: 0
          max: 3600
  - entity: switch
    name: Alarm
    category: config
    dps:
      - id: 104
        type: boolean
        name: switch

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[rammstone83]

hey everybody, any news on this topic? shall i provide more logs?

[issue-triage-workflows[bot]]

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.