Custom Component not showing as match when add Integration

[gearhead765]

I'm trying to create a custom component for an Inkbird C236T Thermostat. I previously had some YAML syntax errors in the file and would get a System Log message in HA when trying to add a new integration. I'm now to the point where the log errors no longer show up so I believe my YAML is syntactically correct. However, when I try to create a new integration, HA does not show my device in the list of matches to select from.

How does tuya-local go from a device query to selecting matching components. I guess I have something wrong in my device description, but I cannot figure out where that is. Here is my "simple" device YAML (I also have a complete YAML component where all of the DPs are implemented although there are a few related to the timers that are just string dumps until I figure ou thow they actually work).

name: Smart Plug-in Thermostat Timer
products:
  - id: ae6rmrnkqz7rjh66
    model_id: g1echw
    name: Inkbird C236T
    manufacturer: INKBIRD
    model: C236T
entities:
  - entity: climate
    name: Thermostat
    dps:
      - id: 129
        type: integer
        name: current_temperature
        scale: 100
      - id: 106
        type: boolean
        name: temperature_unit
        mapping:
          - dps_val: true
            value: "F"
          - dps_val: false
            value: "C"
      - id: 118
        type: boolean
        name: hvac_mode
        mapping:
          - dps_val: false
            value: "off"
          - dps_val: true
            value: "auto"
      - id: 130
        type: string
        name: hvac_action
        mapping:
          - dps_val: "HEAT_ON"
            value: heating
          - dps_val: "COOL_ON"
            value: cooling
          - dps_val: "HEAT_OFF"
            value: idle
          - dps_val: "COOL_OFF"
            value: idle

  - entity: number
    name: Start temperature
    icon: mdi:thermometer-chevron-up
    dps:
      - id: 107
        type: integer
        name: value
        range:
          min: -4000
          max: 21200
        scale: 100
      - id: 106
        type: boolean
        name: unit
        mapping:
          - dps_val: true
            value: "F"
          - dps_val: false
            value: "C"

  - entity: number
    name: Stop temperature
    icon: mdi:thermometer-chevron-down
    dps:
      - id: 108
        type: integer
        name: value
        range:
          min: -4000
          max: 21200
        scale: 100
      - id: 106
        type: boolean
        name: unit
        mapping:
          - dps_val: true
            value: "F"
          - dps_val: false
            value: "C"

  - entity: number
    name: High temperature alarm
    category: config
    icon: mdi:thermometer-alert
    dps:
      - id: 109
        type: integer
        name: value
        range:
          min: -4000
          max: 21200
        scale: 100
      - id: 106
        type: boolean
        name: unit
        mapping:
          - dps_val: true
            value: "F"
          - dps_val: false
            value: "C"

  - entity: number
    name: Low temperature alarm
    category: config
    icon: mdi:thermometer-alert
    dps:
      - id: 110
        type: integer
        name: value
        range:
          min: -4000
          max: 21200
        scale: 100
      - id: 106
        type: boolean
        name: unit
        mapping:
          - dps_val: true
            value: "F"
          - dps_val: false
            value: "C"

  - entity: number
    name: Cooling delay
    category: config
    icon: mdi:snowflake-clock
    dps:
      - id: 111
        type: integer
        name: value
        range:
          min: 0
          max: 10
        unit: min

  - entity: number
    name: Calibration
    category: config
    icon: mdi:thermometer-check
    dps:
      - id: 112
        type: integer
        name: value
        range:
          min: -990
          max: 990
        scale: 100
      - id: 106
        type: boolean
        name: unit
        mapping:
          - dps_val: true
            value: "F"
          - dps_val: false
            value: "C"

  - entity: switch
    name: High temperature alarm
    category: config
    icon: mdi:alarm-light
    dps:
      - id: 113
        type: boolean
        name: switch

  - entity: switch
    name: Low temperature alarm
    category: config
    icon: mdi:alarm-light-outline
    dps:
      - id: 114
        type: boolean
        name: switch

  - entity: switch
    name: Backlight
    category: config
    icon: mdi:backlight-high
    dps:
      - id: 115
        type: boolean
        name: switch

  - entity: switch
    name: Child lock
    category: config
    icon: mdi:lock
    dps:
      - id: 116
        type: boolean
        name: switch

  - entity: switch
    name: Buzzer
    category: config
    icon: mdi:volume-high
    dps:
      - id: 120
        type: boolean
        name: switch

  - entity: sensor
    name: Output state
    category: diagnostic
    icon: mdi:power-plug
    dps:
      - id: 130
        type: string
        name: sensor

  - entity: sensor
    name: Alarm state
    category: diagnostic
    icon: mdi:alert
    dps:
      - id: 131
        type: string
        name: sensor

  - entity: sensor
    name: Firmware version
    category: diagnostic
    icon: mdi:information-outline
    dps:
      - id: 149
        type: string
        name: sensor

Does anyone see what might be keeping this from matching my device when I try to add the integration?

Thanks,

Tom

[gearhead765]

Found my problem with adding the component. DPs 101, 121, 132, 133, 145, 148, and 149 are not included in the device broadcast so I needed to mark them as optional.

[gearhead765]

I wanted to add a little clarification on the above for others looking to create their own device configuration files. If you have an unknown device, the System logs in Home Assistant will have a line with the DPs your device publishes. Something like this:

{"updated_at": 1774740824.012109, "102": 0, "103": 1, "104": 3, "105": 0, "106": true, "107": 3800, "108": 4200, "109": 21200, "110": -4000, "111": 0, "112": 0, "113": true, "114": true, "115": false, "116": false, "117": false, "118": true, "119": false, "120": true, "129": 7175, "130": "HEAT_OFF", "131": "no", "134": 7880, "135": 7700, "136": 7700, "137": 7880, "138": 7880, "139": 7700, "146": false, "147": false}

When adding a new device using the tuya-local integration the percentage match depends on the number of DPs in your device file matching the published list. You should implement at least all of the DPs in the HA log message in your custom YAML. This is mentioned in https://github.com/make-all/tuya-local/blob/main/custom_components/tuya_local/devices/README.md -

There should be one list entry for each supported DPs reported by the device.

What is not specifically mentioned (at least not where I could find) is that if your device has additional DPs mentioned in the devices.json file from the Tuya developer portal, and you choose to add those to your device configuration file, you must mark those DPs as optional: true. If you do not, When tuya-local is trying to match your device, it will see additional DPs in the configuration file that are not in the published list and conclude that your device is not a match. There will be no error message, and you device will not show up in the list of possible matches.